The default Hosted Login experience includes a single consent opt that an end user can set and update as part of their profile. It resides in the Privacy Settings screen, which can be made available to the end user after they have registered or signed in with Hosted Login. Privacy Settings screen in Hosted Login

Note the green toggle labeled Marketing Consent along with some placeholder description text.


When the user opts in to this consent and clicks the save button, the Identity Cloud writes data about the user’s consent into their record. This data is stored in the user’s record in an object called marketing, which resides in a parent object called consents. Consent data in user record

The consents.marketing object contains the following data attributes:

  • clientId - The Identity Cloud client associated with the website or application where the user opted in or out of the marketing consent. If you have multiple digital properties integrated with the Identity Cloud, this is used to identify which one the user opted in or out from.
  • context - Can be used to record the context from which the user opted in or out, for example from a profile update or from a registration (for example, value is “profileUpdate” by default).
  • granted - The current opt value: true (opted in) or false (opted out)
  • type - Can be used to indicate that the user gave explicit consent.
  • updated - The date and time (UTC) when the user opted in or out.

In addition, Hosted Login has the ability to prompt the user for a missing consent if it is required in order to authenticate. Required consents screen in Hosted Login

Based on an update to your settings in Console and the state of consent in the user’s profile, the above screen will display to the user when they log in.