Title: facebook pixel &#8211; hashed customer data
Last modified: April 7, 2018

---

# facebook pixel – hashed customer data

 *  [nataliii](https://wordpress.org/support/users/nataliii/)
 * (@nataliii)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/facebook-pixel-hashed-customer-data/)
 * Dear Pixel Caffeine Team,
 * first of all – I love this plugin, thank you for that 🙂
    That’s why I would 
   love to use it properly also with the GDPR and that’s why I need one information
   about the facebook pixel code your plugin implements on my site:
 * Does the pixel caffeine plugin change the facebook pixel code in order to capter
   the “hashed customer data”? Here ist the facebook link, which probably better
   explains what I mean: [https://www.facebook.com/business/help/611774685654668](https://www.facebook.com/business/help/611774685654668)
   🙂
 * I couldn’t figure it our on my own and it is extremely relevant to what I need
   to do on my website to meat all the gdpr requierments (if I need user consent
   for exampel, or not…)
 * I would be very greatful, if you could give me an answer to this question 🙂
 * Thank’s in advance and all the best,
    Natalia
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffacebook-pixel-hashed-customer-data%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  Plugin Author [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * (@antoscarface)
 * [8 years, 4 months ago](https://wordpress.org/support/topic/facebook-pixel-hashed-customer-data/#post-10169339)
 * Hi,
 * thank you for the appreciations about the plugin, we are glad of that! 🙂
 * About your request, the plugin already hashes the advanced matching data passed
   to the pixel, you can check it with [Pixel Helper Extension](https://developers.facebook.com/docs/facebook-pixel/pixel-helper):
   [https://snag.gy/NyZGLU.jpg](https://snag.gy/NyZGLU.jpg)
 * So, I guess that it’s already compliant to the GDPR rules, how you already said
   🙂
 * Let me know if I’m missing something.
    Thank you.
 *  Thread Starter [nataliii](https://wordpress.org/support/users/nataliii/)
 * (@nataliii)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/facebook-pixel-hashed-customer-data/#post-10177457)
 * 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](https://developers.facebook.com/docs/facebook-pixel/pixel-with-ads/conversion-tracking)(
   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
 *  Plugin Author [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * (@antoscarface)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/facebook-pixel-hashed-customer-data/#post-10185571)
 * Hi,
 * unfortunately, it’s not possible to remove the advanced matching at now, but 
   I’ll add an option in the next release, it will available before that GDPR will
   be active on May 25th for sure, most probably at the end of April or early May.
 * Anyway, Pixel Caffeine adds the advanced matching data already hashed and it 
   doesn’t store anything on the website. Only read them, hash them (as required
   from Facebook) and include them in the Facebook pixel directly without storing
   in the database or wherever. So far, I didn’t see any limitation according to
   GDPR from Facebook about the advanced matching in Facebook Pixel, but I’ll keep
   an eye on it and I’ll do all the necessary to be compliant with the new laws 
   🙂
 *  Thread Starter [nataliii](https://wordpress.org/support/users/nataliii/)
 * (@nataliii)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/facebook-pixel-hashed-customer-data/#post-10278898)
 * 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 🙂
 *  Plugin Author [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * (@antoscarface)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/facebook-pixel-hashed-customer-data/#post-10316832)
 * Hi,
 * sorry for the late response. Unfortunately, I wasn’t able to make an update of
   the plugin in time. I’m working on it to add some more features according to 
   the GDPR and add some compatibilities to some other cookie consent plugin, implementing
   the new API from Facebook: [https://developers.facebook.com/docs/facebook-pixel/events-advanced-use-cases/v3.0](https://developers.facebook.com/docs/facebook-pixel/events-advanced-use-cases/v3.0)
 * Here a topic of a user that is using a plugin of those and I added a suggestion
   to change the main script of Pixel Caffeine to make it working only if the cookie
   is consented: [https://wordpress.org/support/topic/prior-consent/](https://wordpress.org/support/topic/prior-consent/)
 * I hope it can help you in meanwhile I’ll push the new version with GDPR compliant
   version of PC.

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

The topic ‘facebook pixel – hashed customer data’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/pixel-caffeine_e2ce0c.svg)
 * [Pixel Caffeine](https://wordpress.org/plugins/pixel-caffeine/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/pixel-caffeine/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/pixel-caffeine/)
 * [Active Topics](https://wordpress.org/support/plugin/pixel-caffeine/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/pixel-caffeine/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/pixel-caffeine/reviews/)

## Tags

 * [custom audience](https://wordpress.org/support/topic-tag/custom-audience/)

 * 5 replies
 * 2 participants
 * Last reply from: [Antonino Scarfì](https://wordpress.org/support/users/antoscarface/)
 * Last activity: [8 years, 2 months ago](https://wordpress.org/support/topic/facebook-pixel-hashed-customer-data/#post-10316832)
 * Status: not resolved