Hi everyone.
I have a question about the behaviour or Adobe analytics on a site when the opt out cookie is set.
Should the b/ss page load requests be present in the dev network panel?
Views
Replies
Total Likes
Hi @Dmitriy1
which exact opt out cookie are you referring to? The one that gets set through your cookie banner or a global Adobe opt out cookie that is set through the Adobe website?
Thanks for quick response. I'm using the "omniture_optout" cookie with value "This-cookie-will-expire-in-2035". It block all page load requests but button clicks are still present
Views
Replies
Total Likes
Ah, then yes, that is supposed to block all tracking.
If I recall correctly, this cookie was also the "backup" method for excluding internal traffic (if you didn't have a dedicated office IP that you could add to your internal IP filters... you could get your teams to install the cookie...)
If you are still seeing calls from your button clicks, that sounds like a bug... you should raise it with Client Care...
I've noticed that if I add this cookie manually via the developer panel on a dedicated page, the page load requests are still visible on the front end, but this data doesn't appear in the reports. Is this expected behaviour?
Views
Replies
Total Likes
I am going to be honest, I've never used the cookie, so I am not sure the exact technical expectations... whether it should prevent calls going to Adobe, or if it stitches a value to the call to "exclude" it during processing... I am not having much luck finding documentation for this (yet... I will keep looking)
That's my main concern, I can't find the documentation for this cookie either ) Will be glad if someone can share the clear answer on this. Thanks
I've reached out to an Adobe contact, to see if he knows if there is any documentation kicking around...
Ok good news... we found the documentation:
https://experienceleague.adobe.com/en/docs/analytics/implementation/js/opt-out
It looks like the tracking calls should still be sent... but there is a flag that indicates the data should not be included... this is probably so that internal teams can view the tracking calls for testing, but don't corrupt the data collection itself.
So you should still see all the tracking calls, but not appear in workspace reports.
Thank you for your help
You're very welcome... now you have to figure out why your page load requests aren't sending... cause it doesn't seem like the opt-out cookie should be doing that...
Yes, there are different levels of opt out...
Opting out of tracking cookies could mean you still have tracking, but that each visit sets a temporary session cookie for the user, and the next visit a new cookie is generated (meaning the same user will be treated as a new user every visit, but you still have basic tracking).
If however, your opt-out is a full "opt out of tracking", then no, you wouldn't get any tracking at all if your are adhering to the user's request.
Views
Likes
Replies
Views
Likes
Replies