Hello AA Experts!
Has anyone implemented AA alongside One Trust for EU GDPR compliance?
We have had it in place for a while, but recently had to make some updates that the legal team wanted to improve compliance.
We put the Adobe optin code in the One Trust optanonwrapper function, setting the opt in properties based on which categories the customer opts in to (we set this function via a rule in Launch which runs on library loaded). I also update the s.cookieLifetime property (in the top of the Extension custom code) to be NONE if the customer opts out.
This then loads a totally cookieless AA tag on first page load, and then if they opt in and carry on we fire a "normal" tag.
When we did this, we saw Direct traffic jump up a lot.
We noticed that the OT wrapper function was taking a long time to load, could be up to 5-10 seconds in some cases. Which meant the AA tag wasn't necessarily firing on the landing page. So we changed it yesterday and moved all the code out of the OT wrapper and into the Extension custom code.
This meant the AA tag was firing immediately, rather than waiting for OT.
However we immediately saw Internal/Session Refresh traffic rocket (from ~5% to ~20%). Again, it looks like the AA tag isn't firing on the landing page, despite all our tests looking fine.
All our testing of the cookieless tag seems to be fine; Adobe is matching our test visitors fine across multiple visits and multiple channels, and we're not seeing a big jump in unique visitors, just a massive jump in Internal visits.
Anyone got any thoughts about why/how that might be?
Anyone else tried a cookieless AA tag using the s.cookieLifetime property?
Or any thoughts about why removing the delay on the landing page tag would cause an increase in pages where it doesn't fire?
It looks like the cookieless hit isn’t included in the same visit. So when the cookied hit brings back a new MCVID it is starting a new visit, rather than adding on to the anon session.
We tested multiple visits from the same cookieless user, and Adobe was able to stitch them together into the right visits / visitors, but it seems to fail when a user goes from cookieless to cookied.