Hoping somebody here has experienced this before because we're completely stumped.
We're using the same Launch script on all sites, they're all waiting for Onetrust consent to be given before OptIn happens, this is managed within a rule looking for C0002 then runs 'adobe.optIn.approveAll()'
This works for all our sites other than one (brightsideinsurance.co.uk). For some reason this site drops an AMCV cookie (without the experience ID included) even without Target or Analytics firing.
Adobe Support have identified 'adobe.optIn.permissions' are returning very different responses. Brightside (broken site) returns:
['a', 'a', 'm', 'a', 'd', 'c', 'l', 'o', 'u', 'd', 'a', 'a', 'c', 'a', 'm', 'p', 'a', 'i', 'g', 'n', 'e', 'c', 'i', 'd', 'l', 'i', 'v', 'e', 'f', 'y', 'r', 'e', 't', 'a', 'r', 'g', 'e', 't', 'm', 'e', 'd', 'i', 'a', 'a', 'a']
While a working site (https://www.geoffreyinsurance.com/,) returns:
{aam: false, adcloud: false, aa: false, campaign: false, ecid: false, …}
Any tips you can provide would be appreciated
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @SamMa10
can you add some screenshots of how you've configured the previous consent settings in the visitor id extension and how the logic and or data elements look like that read out the consent to enable adobe tools?
Views
Replies
Total Likes
Hi @SamMa10,
Could you provide the requested details to @bjoern__koth so they can assist you better? Or were you able to figure this out on your own? If you still need help, please let us know.
Thanks!
Views
Replies
Total Likes
Apologies for the delayed response!
In the Experience Cloud Id Service extension 'Enable Opt In' is set to true. We then manage the Opt-In by waiting for the customer to interact with OneTrust.
This rule fires when OneTrust has updated their groups or at page top, we check Performance Cookies have been allowed:
Then submit this custom code:
Views
Likes
Replies