GDPR : add cookie check condition to Experience Cloud ID service Extension | Community
Skip to main content
Level 4
March 26, 2018
Delivered

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

  • March 26, 2018
  • 16 replies
  • 29082 views

with GDPR coming in place, the call to the Experience Cloud ID service is coming into discussion. Several legal consultants in companies are claiming that the call only may be issued if there is a consent from the visitor to be tracked.

The current implementation of the standard extension, will always fire the call.

It would be very helpful if the extension would be able to do a cookie check, as such a consent cookie could be set, and the rule would only fire if the consent cookie is on an adequate level.

Stefan

16 replies

jantzen_b
Adobe Employee
Adobe Employee
August 24, 2018

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

Level 3
January 22, 2019

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

brandon_pack
Adobe Employee
Adobe Employee
January 24, 2019

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.

brandon_pack
Adobe Employee
Adobe Employee
February 12, 2019

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

Level 3
February 12, 2019

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!

brandon_pack
Adobe Employee
Adobe Employee
February 13, 2019

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.