Configuration models

On some of your websites or mobile apps, there might be an opportunity for a user to authenticate, log in or provide some sort of identifier. From there, deliver additional value and improved experience by:

• Synchronizing user preferences across your websites and mobile apps. Cross-domain-cross-device consent
• Maintaining a user record in Universal Consent & Preference Management to save and propagate user preferences via integration workflows and more. Unified Profile

Using these two features, there are configuration that can be made to manage known users:

Configuration A - Full authenticated experience

In this case, your audience has the opportunity to identify themselves on your app or website.

The business wants to synchronize preferences - websites and applications will always retrieve the person's latest preferences saved in OneTrust.

The business also wants to keep a UC&PM data subject profile for the person, so they can log into a UC&PM preference center, activate their preferences using integration workflows, and keep a "golden copy" of the data subject.

Configuration B - Synchronize cross-domain, cross-device without maintaining a profile record

In this case, your audience has the opportunity to identify themselves on your app or website.

The business wants to synchronize preferences - websites and applications will always retrieve the person's latest preferences saved in OneTrust.

However, you don’t need to have a UC&PM profile for the data subject, and don’t need to activate their preferences using integration workflows.

Configuration C - Maintain a user profile, but do not synchronize across domains and devices.

In this case, your audience has the opportunity to authenticate on your app or website.

Your business wants to save the preferences managed locally into the UC&PM profiles database and possibly propagate these preferences to other systems using integration workflows.

However, the business does not want to synchronize preferences across websites and mobile apps. Websites and applications will not retrieve the person's latest preferences from OneTrust. Preferences can only be changed locally, on each website and mobile application.

Configuration D - Unknown audience

In this case, your audience remains unknown throughout their session on your app or website. Preferences are only managed locally, on the user’s device.

This is how OneTrust CMP functions by default when the current user is unknown and has not authenticated.

FAQ

What OneTrust products are needed for these configurations ?

In order to synchronize preferences, a Consent Rate Optimization license is needed. To maintain a user profile, a Universal Consent & Preference Management license is needed. Contact your OneTrust representative for a trial or demonstration.