I’m using Stape with a server-side GTM configuration to track conversions.
Currently, I’m tracking web-side Page Views with the Facebook Pixel and using Stape’s DataTag to send server-side conversions.
On the server side, I use Stape’s CAPI tag to send conversions to META, and for maximum redundancy, I also use GA4 to send Page Views via Stape’s CAPI.
I generate a unique code for each page to ensure events (even when triggered at different times) have a unique ID for Page Views.
I checked the Google Chrome console and META’s Test Events tool, and the server events are correctly firing with the right unique ID.
Essentially, I’m sending 1 Pixel event and 2 server events.
For some reason, META keeps reporting that only 28% of Pixel events are also sent server-side. Given the volume of incoming events, this seems impossible.
The coverage metric is a new metric in Events manager and I haven’t seen any pixels where this works correctly yet.
But does it make any sense to you to send 2 server events for 1 event? Usually it doesn’t make any sense.
Also it looks like you do have a deduplication issue as only 27% of the time the event_id matches. This metric either hasn’t been updated yet (it is updated once every ~48 hours) or you are sending different event_id in many cases.
If your site uses SPA make sure you disable automatic history tracking in the Meta tag:
