Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @x18tomek,

    Google Tag Manager
    Could you confirm that you have configured your tags in GTM to fire on Complianz triggers, such as “cmplz_event_marketing”, and not on a trigger such as “All Pages”?

    When I leverage the “Network Request Blocking” feature in Chrome DevTools to block Tag Manager from loading on your site, that prevents Google Analytics and (one of the) Facebook Pixel events from being set prior to consent. Which does indicate to me that this is indeed related to the GTM container configuration.

    Please find our Tag Manager configuration article attached, which explains this in more detail: https://complianz.io/definitive-guide-to-tag-manager-and-complianz/

    HandL UTM Grabber
    It appears that this plugin sets cookies with PHP (not with JavaScript), meaning that these are already set by the time Complianz loads.

    To combat this, Complianz 6.1 will introduce the CookieShredder: a user-focused clean sweep of cookies without consent during website visits.

    When the cookies are set, they will then be checked against your cookie list (synced with CookieDatabase). If these cookies do not meet the consent level of the user, they will be removed or shredded almost instantly from the user’s browser. Please refer to https://complianz.io/introducing-the-cookieshredder/ for the full explanation.

    Facebook Pixel
    As noted earlier, there seem to be two Facebook Pixel implementations on this site. One of those is fired with Google Tag Manager, and can be addressed by triggering it on the “cmplz_event_marketing” event instead.

    As for the remaining FB Pixel, this one doesn’t seem to be fired with Tag Manager. Could you let me know how this has been implemented?

    Kind regards,
    Jarno

    • This reply was modified 3 years, 1 month ago by jarnovos.
    Thread Starter x18tomek

    (@x18tomek)

    Hi @jarnovos ,
    thanks for your answer. I have no access to my client’s GMT so I had to hardcode it by
    <script data-category=”statistics” type=”text/plain”>
    Now it looks ok. So the only remaining cookies are those from Handl. Should I just wait for updating your plugin?

    Thanks again.

    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    @x18tomek If you want you can use the current branch for the cookie schredder:

    https://github.com/Really-Simple-Plugins/complianz-gdpr/compare/extended-cookie-blocker?expand=1

    It will be merged in 6.1.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cookies are set before agreement’ is closed to new replies.