We started using Stape’s CAPIG feature for about 70 advertisers and are seeing issues with event coverage across every pixel and event basically. We’re seeing event coverage for eventID in mid 50s-60s and FBP at 0% despite both browser and server being in the 90s. Is there anything that could explain the low event coverage from eventID, and non-existent coverage from FBP parameter? Is there anything that could help improve our event coverage so we’re not overreporting conversions? For what its worth - fbc isn’t being passed back in our gtm setup.
This is what the payload looks like for Meta Pixel fbp and eventID and for the server (ss below), which has data routing configured correctly.
fbp. fb.1.1746724538931.762286347729749308
eid. ob3_plugin-set_91e1b76737c394a8c8d8e49863662a66285e0dd5cff50666e3ecf3973cd89528
If you don’t provide us with screenshots so we can verify if it has been implemented correctly, it becomes difficult to understand the problem and help you.
Please make sure that you’ve Enabled Advanced Matching inside your Meta CAPI Gateway hub.
Other than that, the event match quality score depends on the data you send with your pixel events. Please make sure that you’ve set it up in such a way that it sends as many parameters as possible.
Thanks for the response. We have advanced matching and FB Login ID enabled in the CAPIG hub and have automatic matching enabled for the pixel in events manager, but we haven’t been manually set up any parameters to send back on the pixel.
In setting manual parameters on our custom events via GTM, what would be main ones we’d want to pass back? A lot of our clients are in restricted verticals but want to make sure we’re sending back at least the key parameters that would improve our deduplication and EMQ scores.
In the case of Gateway, fbp and event_id are fully automatic. We need to study your configuration to see if there is a real problem. Unfortunately you can’t trust Meta events manager interface because it often displays incorrect information, especially in the new Events coverage section, in my experience only 1 out of 10 pixels displays correct data, most of them are false positive errors or gaps that don’t actually exist.
