• Resolved bostrb

    (@boosterbast)


    For each page load there are multipel similar consent events. I have checked this using tag assistant.This seems unneeded and I suspect it will slow down my site. Any advice on how to resolve this?

    In addition when not selecting explicit consent mode, the initial consent that is loaded is everything grantend. I doubt that is correct. Later consent updates after the first one set the denied status correctly.

    • This topic was modified 10 months ago by bostrb.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author alekv

    (@alekv)

    Hi

    For each page load there are multipel similar consent events. I have checked this using tag assistant.

    The Pixel Manager only sends one consent event to Google upon page load. It sends another consent event in case the visitor approves or disapproves cookies (using one of the compatible cookie banners).

    If you see more than one consent event, it’s likely not coming from the Pixel Manager.

    Please post a way how to replicate what you’re seeing.

    I suspect it will slow down my site.

    No. It won’t.

    In addition when not selecting explicit consent mode, the initial consent that is loaded is everything grantend. I doubt that is correct. Later consent updates after the first one set the denied status correctly.

    That is exactly what implicit and explicit consent modes are for.

    If you want no tracking pixels to be loaded and the Google Consent Mode to be denied, simply turn on explicit consent mode.

    Thread Starter bostrb

    (@boosterbast)

    For example. When I have denied consent (without explicit consent option active) and i load a new page. Everytime when I load a page a sequence like the one below occurs

    1. I get a consent event with the following set:
    on-page Default: {ad_storage: Denied, analytics_storage: Denied, ad_user_data: Denied, ad_personalization: Denied, security_storage: Granted, functionality_storage: Granted, functionality_storage: Denied}
    On-page update: nothing is set

    2. I get a consent event with the following set:
    on-page Default: same as previous step
    On-page update: {ad_storage: Denied, analytics_storage: Denied, ad_user_data: Denied, ad_personalization: Denied, security_storage: Granted, functionality_storage: Denied, functionality_storage: Denied, source: Denied}

    3. I get a consent event with the following set:
    on-page Default: same as previous step
    On-page update: {ad_storage: Denied, analytics_storage: Denied, ad_user_data: Denied, ad_personalization: Denied, security_storage: Granted, functionality_storage: Granted, functionality_storage: Denied, source: Denied}

    4. I get a consent event with the following set:
    on-page Default: {ad_storage: Denied, analytics_storage: Denied, ad_user_data: Denied, ad_personalization: Denied, security_storage: Denied, functionality_storage: Granted, functionality_storage: Denied}
    On-page update: Same as pevious step

    URL: https://www.timelesstableau.nl

    • This reply was modified 10 months ago by bostrb.
    Plugin Author alekv

    (@alekv)

    While working on your other support thread I discovered that you also load the Google Consent Mode through Complianz: https://cln.sh/5pWJy2N3

    You shouldn’t do that and only use the Pixel Manager implementation of the Google Consent Mode.

    Thread Starter bostrb

    (@boosterbast)

    Thanks that indeed fixed the issue.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Lots of consent events upon loading of each page’ is closed to new replies.