Purchase events don’t have a deduplication key

Hi, I’m having the same problem with my facebook pixel. It started today.

Hi @simonbbs and @valmy02

Thanks for reaching out for support with Facebook for WooCommerce.

>Some of your Purchase events don’t have a deduplication key, so we’re unable to cross-check whether they’re duplicate events. This means they’re potentially being incorrectly counted twice and leading to inaccurate ad attribution.

>From what I’m seeing it looks like other users are having a similar issue with this plugin.
Is this issue something you guys have a solution / workaround for at this time?

We can confirm that ideally by default, the plugin, intelligently deduplicates events that are sent both from the browser pixel events and server-to-server events (Conversions API) to ensure no double-counted events.

https://woocommerce.com/posts/adapt-for-the-future-with-facebook-conversions-api/

With the Facebook for WooCommerce plugin, the same data that flows through Conversions API and the Facebook Pixel is deduplicated based on a unique event ID, so there’s no concern about the same events being double-counted.

However, we have an open bug report regarding this Missing Some Deduplication Parameters and our devs are working to ensure this resolved.

If you have made sure no other plugin that does FB pixel and also no caching plugins that could affect it, for now, I’d suggest manually click “Resolve” or “Ignore” on the Facebook site as we keep monitoring this and working on the above mentioned open issue, and also working with Facebook to ensure the accuracy of the report.

Or as a work around you can temporarily disable the auto pixel injection using the following code snippet:

add_filter( ‘facebook_for_woocommerce_integration_pixel_enabled’, ‘__return_false’ );

You can use Code Snippet plugin to insert this code.

And then, you can keep Facebook for WooCommerce for the products syncing, while for Facebook pixel, you can use another plugin that does Facebook pixel for example, Facebook for WordPress by Facebook.

Let us know if you have any questions!

Good Afternoon @zhollenbeak,

Thanks a ton for the information!

I double checked with the NitroPack team and there was not an exclusion in place for the Facebook Pixel, so it’s *possible* that is affecting us here as well.

I’ve worked with their team to get an exclusion in place for the Pixel, and if that doesn’t help us here we’ll test that code snippet you sent over.

Thanks so much for the info here, I’ll follow up when we’ve determined if the NitroPack exclusion helped.

-Simon

Hello @simonbbs

Sounds great! Do let us know how it goes.

If you encounter any error after following the steps above, feel free to reply back; we’d be happy to help.

Good Morning @nathvi

I have some more information for you after putting that exclusion in place and running some tests.

After ignoring the error yesterday we are still seeing the following error in our diagnostics tab related to the “View Content” event: https://www.dropbox.com/s/61uaez7ps91a37m/ViewContent%20Still%20Has%20Issue.png?dl=0

I ran tests of both the browser View Content and the server View Content event using FB’s test tool, and investigated the site using the Chrome “FB Pixel Helper Extension” and everything looked good, except for these errors that came via the browser event: https://www.dropbox.com/s/mbjydvu5hia13az/ViewContent%20Parameters.png?dl=0

I don’t believe those parameter errors have anything to do with this, but I wanted to send over all the information just in case.

My first question here: The initial error we were given was:

`Some of your Purchase events don’t have a deduplication key, so we’re unable to cross-check whether they’re duplicate events. This means they’re potentially being incorrectly counted twice and leading to inaccurate ad attribution.

You’ll need to use the solution below to fix the issue.

Once you’ve fixed the issue in your website code you can mark it as resolved. This will move it to the Previously Detected section. If the issue is found again after 3 days it will move back to the Active section.

To prevent this, add deduplication keys to Purchase events received by both your pixel and the Conversions API.`

It doesn’t seem to me like the “View Content” event is a purchase event, so I’m not sure if we’re barking up the right tree here.

Does the plugin track that “View Content” event / could the issue with the “View Content” event be the same issue as other users are experiencing with “Purchase events” ?

If so, we’ll likely run the test you highlighted with the code snippet, however, I wanted to confirm that the “View Content” event is tracked by this plugin.

Thanks so much!

-Simon

Hi @simonbbs,

Does the plugin track that “View Content” event / could the issue with the “View Content” event be the same issue as other users are experiencing with “Purchase events” ?

From the code level, the plugin will send all events via both server (Conversions API) and browser (Browser pixel) with the same event name and event ID. Then Facebook will try to deduplicate identical events sent through the Facebook pixel and the Conversions API.

Reference: https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events

Your current problem:

ViewContent Event Missing Deduplication parameter

It looks like Facebook is getting duplicate data from the Facebook plugins API and the pixel, which it then cannot deduplicate.

The first thing to check here would be for a conflict between your plugins and/or theme.

1. If you are not using the latest version, could you please update the Facebook for WooCommerce plugin and see if that helps?
   https://github.com/woocommerce/facebook-for-woocommerce/releases
2. Do you perhaps have the pixel tracking code added to your site more than once? One thing you can check is your site’s header.php in case the code was added there manually.
3. If your host does not provide an easy way to set up a staging site, you might want to use something like the WP Staging plugin for this purpose: https://www.ads-software.com/plugins/wp-staging/

On your staging site, you can try the following conflict test: https://docs.woocommerce.com/document/woocommerce-self-service-guide/

Please let us know how this goes!

We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

Good Morning Guys,

I took a look at our events today and we’re once again seeing the deduplication error for one of our purchase events: https://www.dropbox.com/s/017ftybzl8tour5/Purchase%20Event%20Pixel%20Issue%20Back.png?dl=0

I just want to confirm that our next steps for testing this should be adding the following code:

add_filter( ‘facebook_for_woocommerce_integration_pixel_enabled’, ‘__return_false’ );

Then re-inserting the Facebook Pixel via one of the Typical FB Pixel plugins like: https://www.ads-software.com/plugins/official-facebook-pixel/

Please just let me know if I need to do / prep anything else to run that test!

Thanks so much,

-Simon

Hi Simon,

Yes, you can try this method – which will then disable the plugin’s auto pixel injection, using a plugin such as Code Snippets to insert this code.

You can then test using a generic plugin that does not use the WooCommerce filter you described, as needed.

I hope this information is helpful to you – please let us know how this goes!