Opt-in Use Cases
- Topics:
- Identities
- Integrations
CREATED FOR:
- Developer
- User
- Admin
- Leader
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. |
Experience Cloud Services
- Identity Service Help
- Overview
- Implementation
- Implementation methods
- Implementation guides
- Implement with Experience Platform tags
- Implement for Analytics
- Implement for Target
- Implement for Analytics and Audience Manager
- Implement for Analytics, Audience Manager, and Target
- Using the ID Service with A4T and a Server-side Implementation of Target
- Direct Integration with the ID Service
- Direct Integration Use Cases
- Test and verify the ID Service
- Opt-in Service
- ID Service API
- ID Service API Overview
- Configuration
- Configurations overview
- audienceManagerServer and audienceManagerServerSecure
- cookieDomain
- cookieLifetime
- disableIdSyncs
- disableThirdPartyCalls
- disableThirdPartyCookies
- idSyncAttachIframeOnWindowLoad
- idSyncContainerID
- idSyncSSLUseAkamai
- loadTimeout
- overwriteCrossDomainMCIDAndAID
- resetBeforeVersion
- sdidParamExpiry
- Secure and SameSite configurations
- secureCookie
- useCORSOnly
- whitelistParentDomain and whitelistIframeDomains
- Methods
- Methods
- appendSupplementalDataIDTo
- appendVisitorIDsTo (Cross-Domain Tracking)
- callTimeOut Methods
- ID Synchronization by URL or Data Source
- getInstance
- getAnalyticsVisitorID
- getCustomerIDs
- setCustomerIDs
- getMarketingCloudVisitorID
- getLocationHint
- getVisitorValues
- isClientSideMarketingCloudVisitorID
- resetState
- Reference
- Reference Overview
- Analytics Reference
- Analytics Reference Overview
- CNAME Implementation Overview
- Setting Analytics and Experience Cloud IDs
- Order of Operations for Analytics IDs
- ID Service Migration Decision Points
- ID Service Migration Scenarios
- Analytics and Identity Requests
- Server-side Implementation Mixed with JavaScript
- The ID Service Grace Period
- Google Chrome SameSite labelling changes
- Content Security Policies and the ID Service
- COPPA Support in the ID Service
- CORS Support in the ID Service
- Customer IDs and Authentication States
- ECID library methods in a Safari ITP world
- Identifying Unique Visitors
- Get Region and User IDs From the AMCV Cookie or the ID Service
- Requirements for the ID Service
- Video Heartbeat and the ID Service
- Data Workbench and the ID Service
- SHA256 Hashing Support for setCustomerIDs
- FAQs
- Release notes for ID Service
Connect with Experience League at Summit!
Get front-row access to top sessions, hands-on activities, and networking—wherever you are!
Learn more