Fire Facebookpixel before GDPR consent

  • Hi!

    Recently installed this plugin. What a great plugin and great explanatory videos! Really like the concept of fallback server tracking/facebook api.

    Im a little confused about the GDPR settings. We use “GDPR Cookie Consent” by Webtoffeee that is one of the featured GDRP plugins in your settings.
    I′ve set the pixel settings to “Enable the Facebook Pixel tracking before consent is captured” and also enabled the “Enable AJAX filter values update” however the tracking wont work until accepting the cookies. Im testing with the facebook pixel helper and it says “We detected event code but the pixel has not activated for this event, so no information was sent to Facebook”
    If i understand this right this is indicating that your event code is firing but the pixel is not active due to some absent cookies.

    As soon I accept the cookies, things works.
    The server side tracking wont work either until accepting, which makes sense if its dependent of “blocked cookies”.

    I′ve checked some of the biggest European webshops and they all track facebook events before accepting cookies so im also confused about the GDPR rules here. But maybe thats a question i should ask elsewhere.

    Thank you for a great plugin.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author PixelYourSite

    (@pixelyoursite)

    Hello,

    These options are no longer supported, we need to update that page completely.

    Thread Starter stevesand

    (@stevesand)

    Thank you, we ended up switching GDRP-plugin.

    We have had our first purchases with your plugin now. Our purchases are being counted as two in Ads Manager.
    While the events manager is showing 1 browser event and 1 “unduplicated” server event, Ads Manager will still count 2 purchase events on the AD. I understand that this is a bug with Facebook. Just wanted to check if you have some input?

    Thank you.

    • This reply was modified 3 years, 11 months ago by stevesand.
    Plugin Author PixelYourSite

    (@pixelyoursite)

    Hello,

    If the number of purchase events is correct in the Events Manager, this looks like a sort of Facebook bug indeed.

    One thing you can do is to check if automatic events are ON inside your Events Manager settings. Make sure this is turned OFF, since it can lead to double counting.

    Thread Starter stevesand

    (@stevesand)

    Thank you, i′ve checked now and it was off.

    I′ve contacted Facebook about this since everything is reported correctly in events manager with matching browser and api event id, and correct “unduplication”. It is 100% due to some bug in Ads Manager.

    Facebook were not helpful as usual but advised me to contact a web developer, which i′ve been for 10 years ?? Sent them print screens comparing the events in events manager and ads manager.

    Might turn off api tracking until they sorted it out.

    Thank you for all your help.

    Plugin Author PixelYourSite

    (@pixelyoursite)

    Let me know if turning off the api will fix the problem.

    But if browser/api events are reduplicated, I don’t see how this can create a problem.

    I would say that their major updates related to iOS14 and Aggregated Event Measurement have something to do with it, and it will get fixed soon. But of course, can’t be sure that’s the cause of the problem.

    Thread Starter stevesand

    (@stevesand)

    Hi!
    Just wanted to report back and say that it is now reporting correct. We did not disable the api tracking. The bug was at Facebook as expected.

    Thank you.

    • This reply was modified 3 years, 11 months ago by stevesand.
    Plugin Author PixelYourSite

    (@pixelyoursite)

    Thank you for your feedback, it’s really helpful.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Fire Facebookpixel before GDPR consent’ is closed to new replies.