Deduplication event_id 0%

[onword333]

Hello.
I'm sorry, but I don't know what to do.
We use ConversionsAPI-Tag-for-GoogleTagManager to send events through the server.
All accounts are getting a deduplication error. It repeats again and again after marking it as "resolved" in the pixel.

There were no problems before 2021-10-22.
I don't understand why this is happening. We pass evenID and event_id to the deduplication parameters.
When we run debugging through pixel to we see that events are deduplicated.

But Facebook keeps showing this error and in the cluster the deduplication shows 0% for the server.

Maybe the problem is with facebook, but I'm not sure.
Can you tell me what the problem is ?
Do you also have this problem?

[koconnor3]

keep in mind that:

• the deduplication modal doesn't respect the date range you have selected; it shows data from a completely different (and seemingly arbitrary) window of time seen just below the charts ("Data from: ..."). So if you fixed it outside that window it might not show yet
• Facebook has been making a lot of changes to the events manager UI lately and it is very buggy. I have had similar situations...
• it says Overlap of event_ids is 66.67%, so that clearly indicates that at least some event_ids must be received from the server events, otherwise how could they overlap? Since the numbers in that chart can't all be true, I'm willing to wager this is Facebook's bug, not yours.

[onword333]

keep in mind that:

• the deduplication modal doesn't respect the date range you have selected; it shows data from a completely different (and seemingly arbitrary) window of time seen just below the charts ("Data from: ..."). So if you fixed it outside that window it might not show yet
• Facebook has been making a lot of changes to the events manager UI lately and it is very buggy. I have had similar situations...
• it says Overlap of event_ids is 66.67%, so that clearly indicates that at least some event_ids must be received from the server events, otherwise how could they overlap? Since the numbers in that chart can't all be true, I'm willing to wager this is Facebook's bug, not yours.

Hello @koconnor3

• I don't understand what I have to fix (in the event manager I just clicked the “Mark as Resolved” button), the event_id parameters from the server are passed for all events.
• Yes, I noticed that :)
• Before the error, the overlap was 95- 100%. Now the percentage is 66% I suspect it is related to this problem and now there is a drop in the overlap percentage.

@koconnor3 , thank you for your help and your time, it looks like you are right and it is a problem with facebook.

[shockalotti]

I suspect it's something on Facebook's side.

I noticed around 5 or 6 days ago, ALL client accounts using CAPI were showing this error.

We've done MANY of these GTM / GTM server setups (using our own code base), and are now suddenly seeing this.

I notice Trackify clients on Shopify aren't seeing this issue. Trackify has a direct partnership with Facebook so their app auth will work slightly differently. I wonder if it's the CAPI auth system that's suddenly become buggy because an intern inadvertently introduced an errant typo.

It happens...

[amit3649]

I am facing the same issue. Is there any other alternative at the moment?

[onword333]

I suspect it's something on Facebook's side.

I noticed around 5 or 6 days ago, ALL client accounts using CAPI were showing this error.

We've done MANY of these GTM / GTM server setups (using our own code base), and are now suddenly seeing this.

I notice Trackify clients on Shopify aren't seeing this issue. Trackify has a direct partnership with Facebook so their app auth will work slightly differently. I wonder if it's the CAPI auth system that's suddenly become buggy because an intern inadvertently introduced an errant typo.

It happens...

@shockalotti hi. Thank you for your time and information. Didn't know about this.
We wrote to facebook support, but no response yet

[onword333]

I am facing the same issue. Is there any other alternative at the moment?

Hi @amit3649
I don't know.
We have CAPI integrations through the tag manager, as well as on the back end of the site.
Both of these integrations always send event_id. But both pixels show event_id from the server = 0%.

[Bukashk0zzz]

@amit3649 You can try new FB CAPI GW https://stape.io/facebook-conversions-api-gateway-the-easiest-way-to-implement-fb-capi/

[onword333]

@amit3649 You can try new FB CAPI GW https://stape.io/facebook-conversions-api-gateway-the-easiest-way-to-implement-fb-capi/

@Bukashk0zzz hi.
Interesting, thanks for the option, I'll be able to try it out later.

[koconnor3]

I don't think it's related to the 'auth' at all as the events are coming through just fine. They show up in the test tab, you can see the server totals in the line graphs, and of course, there is a non-zero event_id overlap. The issue is that the events manager UI is buggy and isn't presenting the correct value here. It's probably a state-management issue with the React component and 0 is just the initial value.

[onword333]

Hello all.
I finally managed to figure it out.
In short, you need to remove test_event_code or pass "null" or "undefined" as a value.
You can read more about it here

[shockalotti]

Nice work @onword333 - thanks!

[Tiggerito]

I can confirm that removing test_event_code from the events does fix this issue.

[onword333]

Nice work @onword333 - thanks!

you're welcome

[simeyla]

I have been sending test_event_code: null (from a .NET client) which I always assumed would be fine, but now I'm suspicious.

I just completely removed it because over a year later I'm seeing the following odd statistics:

The Test Events Tool help says:

Note: The test_event_code field should be used only for testing. You need to remove it when sending your production payload.
Events sent with test_event_code are not dropped. They flow into Events Manager and are used for targeting and ads measurement purposes.

I don't even know here what 100% means when it's also saying 0%. My server events are definitely getting through since they're shown in other graphs just fine.

Hopefully this means targeting and measurement wasn't affected and it's just a glitch in this page.

--

UPDATE: Confirmed that sending null for test_event_code does break this reporting. I removed it yesterday from my .NET client code and everything shows 100% now under that second column. Wow!

If using JavaScript you can set it undefined which gets ignored when serialized. This is really bad tbh.