GDPR : add cookie check condition to Experience Cloud ID service Extension

Thanks Dave - hopefully it's helpful.   To answer your question, in it's current state you cannot customize or choose the cookie name if you enable storage.  You can choose the domain but not select 'sat_track' at this time.

Thanks Brandon!  That is excellent news, I looked over the documentation.

New question, how would I leverage the EU compliance cookie sat_track? That is what we are currently using to control the analytics implementation, so it would easiest to keep using the same thing.  Thanks!

For those following this thread the new Opt-In Capabilites for the Experince Cloud JavaScript libraries were successfully released to the public yesterday.  The Experince Cloud ID Service and a number of the solution libraires like Analytics, Audience Manager, Target, etc. can now be configured to supress beacons and cookies until your definition of consent has been opted-in.  This can be done with raw implmentations but also has a nice UI in Launch:

https://docs.adobelaunch.com/extension-reference/web/experience-cloud-id-service-extension

The current plan is to release this to the general public on Feb 11th, 2019.  New versions of AppMeasurement.js and VisitorAPI.js an their coordesponding Launch Extensions that support this feature will be released at the same time.

Did this ever make it out of beta?  I could really use it!

Update: This feature is entering beta stage this fall. Assuming all goes well, it should hit general availability shortly after that.

Hi Dave,

I made a custom JavaScript in which I copied the VisitorAPI.js code, and added a global scope function "getVisitorID" with some conditional code on retrieving a consent cookie, checking the cookie and if consent OK, making the call to the VisitorID service.

I load this script directly in the HTML code before Launch. In launch, in the Adobe Analytics tool configuration, in the Custom code for tracker, I call this "getVisitorID" function and assign the value to the s.Visitor. This seems to work quite well.

The issue is that the VisitorID service must be called before Analytics is called, so that the s.Visitor assignment is taking place at the right moment.

However, as stated in my earlier comment, since we already track the first call to Analytics before the enabling of the Visitor ID service (hence setting the cookie), the visits before and after consent are seen as from 2 different visitors. Until now still no response from Adobe Support on this issue yet.

Any updates on this?  My idea above didn't work.

I created a rule which loads at the top, and the custom code is the visitorAPI.js file and added a condition.  Any reason why this won't work?  Then the code is still controlled by Launch but you can add the consent condition.

We have a test implementation running where the Experience Cloud ID ( via VisitorAPI.js) is hardcoded after the consent. But we ran into another issue: we track the pagehit before the consent popup as well (no mcid yet), and a pagehit after consent is set (mcid set), but both visits are seen as from different visitors, even with grace period enabled.

This issue is in the meanwhile under investigation at the Adobe Analytics team... still waiting...