How many users clicked on opt out on cookie consent banner? | Community
Skip to main content
M
MahimitraCh
Level 3
September 4, 2024
Solved

How many users clicked on opt out on cookie consent banner?

  • September 4, 2024
  • 2 replies
  • 1673 views

Hello,

 

 

I am implementing one trust banner on website and I am aborting server calls if user clicks on Opt out. let's say I want count of users opting out. How would i get that in adobe launch/analytics.

 

thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by bjoern__koth

Well, if you don't have consent, you cannot track that, correct?

So, you  could / should for sure not track analytics opt outs 😂


OneTrust has its own dashboard you can look at. Unfortunately no API to pull the data out.

 

Another option I have set up for a client: set up a proxy that you can send custom analytics calls through, that strips all outgoing and incoming cookies. At the same time, the IP is obfuscated, so you end up having a fully anonymized, cookieless AA consent tracking.

Problem: you cannot load an analytics library and will have to forge your own tracking requests...

2 replies

RiteshY18
Community Advisor
RiteshY18Community Advisor
Community Advisor
September 5, 2024

Hi, consider below 

- create a data element in Adobe Launch to capture/identify the opt-out button click

-  Define rule event in Adobe Launch to track opt-out button click and perform event capture /

-  Define an action to send an event to analytics [should have Adobe Analytic extension for Launch ] and the corresponding action type [set variable]to set the value to Analytics custom variable 

 

M
MahimitraChAuthor
Level 3
September 5, 2024

Ya but when user clicks on opt out we won't send any server call right? So how we gonna capture this click.?

RiteshY18
Community Advisor
RiteshY18Community Advisor
Community Advisor
September 5, 2024

on click assign value to data element example - in and pass on this to your evar/custom variable on the analytics 

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
September 5, 2024

Well, if you don't have consent, you cannot track that, correct?

So, you  could / should for sure not track analytics opt outs 😂


OneTrust has its own dashboard you can look at. Unfortunately no API to pull the data out.

 

Another option I have set up for a client: set up a proxy that you can send custom analytics calls through, that strips all outgoing and incoming cookies. At the same time, the IP is obfuscated, so you end up having a fully anonymized, cookieless AA consent tracking.

Problem: you cannot load an analytics library and will have to forge your own tracking requests...

Cheers from Switzerland!
    M
    MahimitraChAuthor
    Level 3
    September 5, 2024

    Can you explain bit more on setting up proxy or any resurces would help, on how to strip the cookies in image request.

     

    Thanks.

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    September 5, 2024

    Hi @mahimitrach 

    DISCLAIMER: talk to your legal department if they are ok with this approach!

     

    you will have to talk to your sys admins to set up

    • a CNAME that is sending data to Adobe Analytics (you cannot use an existing CNAME which you may have set up for 1st party cookie)
    • under this CNAME, your infrastructure / proxy has to be set up to forward tracking calls to the default Adobe servers (sc.omtrdc.net or 2o7.net domains)
      • this proxy has to 1:1 forward your requests, but at the same time
        • strip existing cookies you would send to Adobe
        • strip incoming server-side cookies that may be returned with the tracking call
    • create custom code on your tag manager that generates an image request similar to what your AppMeasurement call creates (best is to copy an existing tracking request from your website)
    • separate report suite
      • it makes complete sense to create a standalone report suite that is solely capturing consent data, since you anyway cannot reidentify the users due to missing cookies
      • set up events for e.g.
        • banner shown
        • banner accepted (accept all)
        • banner rejected (reject all)
        • custom consent
      • set up props or eVars to capture your different consent categories upon user interaction with the banner, and make sure to always fill them with "yes"/"no" if set e.g., all "yes" if the user clicks "accept all"

    Here's a schematic view on how it works. We kept it tracking solution agnostic. Adobe Analytics showed the most precise captured data.

     

    A sample call may look like this (consent shown)

    https://experienceleague.adobe.com/en/docs/analytics/implementation/validate/query-parameters

    https://consent.yourdomain.com/b/ss/yourdomainconsentprod/1/s2752396664298?AQB=1&server=www.yourdomain.com&pageName=%2F&pe=lnk_o&pev2=&c5=%2F&c6=CH&c7=www.yourdomain.com&v3=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_15_7)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F128.0.0.0%20Safari%2F537.36&v5=%2F&v6=&v7=&v8=&v9=&v10=&events=event1&r=&p.=&debug=true&.p=&AQE=1

     

    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...