Opt-in Use Cases

Sample use cases and solutions to manage the Opt-in service.

Tips and Troubleshooting

  • Visitor JS initialize is synchronous and executes during page load. If you are interfacing with a CMP or permissions persistence that has a high latency, it might be preferable to use the asynchronous functions described in Opt-in Setup.
  • Opt-in is a per-domain implementation. It will not handle cross-domain implementations.
  • In order to disable third-party calls for a specific library, you will need to configure that preference in each library separately.

Opt-in Scenarios

These use cases are example ideas for using Opt-in service.

Requirement Solutions Impact

Analytics is okay to collect in pre-consent state but all other libraries can’t be loaded until consent is received

Use Opt-in to enable Analytics category in pre-consent state

Analytics uses the Analytics identifier rather than ECID in pre-consent collection. Once ECID is approved, a new identifier will be used and the visitor will receive an ECID that can be used for activation and integrations.

Visitor fragmenting in pre-/post- consent state is expected.

First-party measurement is okay to collect in pre-consent state. All other types of data usage prevented until consent is received.

Use Opt-in to enable Analytics + ECID libraries in pre-consent state.

Add the ‘disablethirdpartycookies’ config to ECID library to block 3rd party cookie + ID syncs in pre-consent state

Adobe Demdex call will trigger for ECID retrieval but no Demdex cookie, other third-party cookie or ID syncs will be present.

Keeps consistent visitor in pre-/post- consent state for Analytics. Collection in pre-consent state will be tied to post-consent data collection.

First-party measurement plus targeting is acceptable in a pre-consent state. All other types of data usage prevented until consent is received.

Use Opt-in to enable Analytics + ECID + Target libraries in pre-consent state.

Add the isablethirdpartycookies config to ECID library to block third-party cookie + ID syncs in pre-consent state. Remove flag in post-consent state.

Adobe Demdex call will trigger for ECID retrieval but no Demdex cookie, other 3rd party cookie or ID syncs will be present.

Keeps consistent visitor in pre-/post- consent state for first-party solutions. Collection in pre-consent state will be tied to post-consent data collection.

No cookies are allowed to be set in a pre-consent state

Use Opt-in to block all libraries from loading until consent is received

Implementation is as expected and all libraries, including ECID, will load in correct sequence in post-consent state.

Data loss for customers who never give consent to be tracked.

On this page

Adobe Summit Banner

A virtual event April 27-28.

Expand your skills and get inspired.

Register for free
Adobe Summit Banner

A virtual event April 27-28.

Expand your skills and get inspired.

Register for free
Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now
Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now