Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter nataliii

    (@nataliii)

    Hi,

    first of all – thank you! I`m really looking forward for the update 🙂

    Regarding the advanced matching in Facebook Pixel – the European law doesn’t see the hasing as sufficient. The problem is in the way of the data is being hashed. Tough it is impossible for anyone form outside to match this data with the affected website visitor, it is still easy for Facebook to identify this person. And that’s against the GDPR…

    It means, that if want to use the advanced matching function in UE we need to ask our website visitors for a definite consent. Since not everyone (as for example me) needs this feature, it will be great to just have the possibility to remove it 🙂

    Thread Starter nataliii

    (@nataliii)

    Hi,

    thank you for your reply!

    Well… yes and no 😉

    According to the GDPR:

    1) if you use the facebook pixel in a “normal” way (the pixel fires only when people, who already are logged in into facebook in their browser, visit your website) – than everything is fine
    2) but if the facebook pixel code is modified to use the advanced matching data (regardless if they are hashed or not – according to the GDPR it is not enough privacy for the website visitors) – than I need to specifically ask my website visitors, if they agree that I collect this data…
    It is the ADVANCED MATCHING WITH THE PIXEL, which is not allowed without an explicit permission from the website visitors. Look at this article (scroll to the paragraph “advanced matching pixel”)

    I the situation 2, I need to now if the pixel caffeine plugin is collecting this “advaced matching data” and if so – can I change that to use the facebook pixel just in its “normal” basic way?

    Looking forward for your answer,
    Natalia

    Thread Starter nataliii

    (@nataliii)

    Thank you!
    Now it works 🙂

Viewing 3 replies - 1 through 3 (of 3 total)