To deduplicate identical events received by both your pixel and the Conversions API, we need to identify them by cross-checking a matching deduplication key in both sources.
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.
When you run debugging, you can see that the deduplication is working
Looks like your local Facebook bug.
I had the opposite situation a couple of days ago. In debug mode the events didn’t deduplicate, but in fact they did, it eventually went away on its own within 24 hours.
Try marking all issues as resolved and see if the problem resumes.
@Alex Hi,
The thing is that not only I see it, but all clients observe these errors.
Thanks, I’ll try marking them as resolved and see if they appear again.
Yes, I’m sure the unique identifier is correctly generated. We use your template and supplement it with fbp. When tested through a pixel, the deduplication works.
Everything was working until 22.10.2021
@Denis, hello.
That’s not exactly true
I’m sorry, maybe I didn’t express myself correctly.
I meant that in the event manager I just clicked the “Mark as Resolved” button.
From your screens look like everything is configured correctly.
I don’t have this issue that’s why I can’t test approaches to find a workaround on it. However, I saw a few similar issues to this one across the internet. And the only suggestion I have that’s trying to do the same on the new business manager with a new API key and new pixel.
Hi, congratulate me .
I finally figured it out.
The problem was that the test_event_code value was passed with all events. I set test_event_code to undefined.