When setting up a new webhooks endpoint to retrieve the profile object on receipt of the "Account logged in" notification, the recommended method is:
* accounts.getAccountInfo with UID from notification:
* Use the UID provided in the notification payload to callaccounts.getAccountInfo.
* This API call will retrieve the complete profile object associated with the given UID.
This method ensures that you get the most up-to-date profile information for the user who has logged in.
References
* SAP Customer Data Cloud API Documentation

To ensure that all subscriptions for your marketing campaign are genuine and that users confirm their intent to subscribe via email, you should activate the Double Opt-In process in the subscription. This process sends a confirmation email to users, requiring them to verify their email address and confirm their subscription by clicking on a link.
* Double Opt-In Activation:
* Navigate to the subscription settings within your SAP Customer Data Cloud account.
* Enable the Double Opt-In option for the specific subscription.
* Configure the email template that will be sent to users for confirmation.
This ensures that only users who confirm their email address and subscription will be added to your list, maintaining the authenticity of your subscriptions.
References
* SAP Customer Data Cloud Documentation on Double Opt-In

An update to the consent vault in SAP Customer Data Cloud is triggered by actions that involve changes to a user's consent preferences. Specifically, when:
* User Opts Out of a Newsletter: This action directly impacts the user's consent records, as it reflects a change in their subscription and communication preferences.
* Consent Vault Update: Opting out of a newsletter requires updating the consent vault to record the user's new preference, ensuring compliance with consent management and data privacy regulations.
Other actions, such as updating contact details, failed login attempts, or connecting to social media, do not directly involve changes to consent preferences and therefore do not trigger updates to the consent vault.
References
* SAP Customer Data Cloud Consent Management Documentation