GDPR : add cookie check condition to Experience Cloud ID service Extension | Community
Skip to main content
S
stefanm38281801
New Participant
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

    Show previous replies
    D
    Dave_Hamel_2024
    New Participant
    June 15, 2018

    I have implemented a test with TrustArc, and I can stop everything but the Experience Cloud ID.  The only solution I can find is to put the code outside of Launch and wrap the entire launch include in a conditional statement.  If anyone has a better suggestion I would love to hear it.

    thebenrobb
    thebenrobb
    Employee
    June 7, 2018

    Sorry, not at the moment.  I'm only parroting what I've heard, I don't have any inside knowledge of the roadmap.

    P
    PieterVdo-oa3E4
    New Participant
    June 6, 2018

    Any idea/news on when this update will be available?

    thebenrobb
    thebenrobb
    Employee
    May 15, 2018

    This is in the works.  The ECID itself is being updated to have an ability to wait for opt-in before firing.  Then the Launch extension will need to be updated.  We'll be able to provide more technical details when it's a little farther along.

    S
    stefanm38281801Author
    New Participant
    March 26, 2018

    Not really the same. The sat_track option in Analytics is an all or nothing on website tracking. Sat_track not set is "no tracking at all".

    We're used to different consent levels for different kinds of tracking. Below is a typical settings screen, indicating to which kind of tracking a visitor gives consent.


    So normal basic web tracking is allowed. However, the Visitor ID Service (Experience or Marketing Cloud ID) is seen by the legal advisors as a mean to identify and profile the visitor (i.e. collect personal information), and they advise to allow it only if the consent level is at least "relevant" (mainly, because the service makes a call to another domain - i.e. demdex.net). So we may only invoke the Experience Cloud ID service (and link it to Analytics) if the consent level is adequately set.

    jkunz
    jkunz
    New Participant
    March 26, 2018

    This sounds very similar to the already-existing "Enable EU compliance for Adobe Analytics" option in the Analytics tool/extension?

    Terms & ConditionsAccessibility statement

    Loading footer...