Meta Pixel and Conversions API Count the Same Conversion Twice
The viewer and server can report the same event. Without a common identifier Meta can treat them as two different results. Do not immediately disable the entire server measurement.
Step by step
1. In Event Manager, open event testing and perform one controlled action. Save its name and identifiers on the browser and server side.
2 . For the same event, both channels should transmit a compatible event name and event id. ID create once for a specific action, not separately in each channel.
3 . Check that the purchase is not sent simultaneously by the store plugin, GTM and its own code. Make a list of all the places that trigger the event.
4 . Refresh the confirmation page and return to it from history. The display itself should not generate a new transaction. On the system side, use a permanent order identifier and repeat service.
5 . Verify value and currency and your consent to the appropriate processing. Do not send unnecessary personal data for testing.
How to check whether the amendment works
One controlled action should be identified as one event after a deduction. The mere disappearance of the warning does not prove that the sales value is correct; compare the result with the order in the system.