YUNJI Agency
Registered Member
- Jul 10, 2026
- 55
- 12
Ran into this one a few weeks back, still not sure i fully nailed down every piece of it.
Had both pixel and capi running on an account, purchase numbers in ads manager started looking off, higher than what the store backend was actually showing. difference wasn't huge at first, maybe 15-20 purchases a week more than actual orders, but it kept showing up consistently.
Checked the obvious stuff first, no test purchases running, no bot traffic that i could find. went into the events manager and started comparing individual purchase events side by side, noticed some orders had two separate purchase events firing within a few seconds of each other, one from pixel, one from capi.
Turned out the event_id being passed wasn't matching between the two, pixel was generating its own id and capi was sending a different one for what should've been the same purchase event, so meta wasn't deduping them.
Fixed the event_id logic so both sides pass the exact same id for the same transaction, watched it for about a week after, numbers lined up with the store backend again, gap closed to basically nothing.
Still not 100% sure this was happening on every order or just a subset, didn't dig into how far back it went. anyone dealt with event_id mismatches like this before, how'd you end up spotting it?
Had both pixel and capi running on an account, purchase numbers in ads manager started looking off, higher than what the store backend was actually showing. difference wasn't huge at first, maybe 15-20 purchases a week more than actual orders, but it kept showing up consistently.
Checked the obvious stuff first, no test purchases running, no bot traffic that i could find. went into the events manager and started comparing individual purchase events side by side, noticed some orders had two separate purchase events firing within a few seconds of each other, one from pixel, one from capi.
Turned out the event_id being passed wasn't matching between the two, pixel was generating its own id and capi was sending a different one for what should've been the same purchase event, so meta wasn't deduping them.
Fixed the event_id logic so both sides pass the exact same id for the same transaction, watched it for about a week after, numbers lined up with the store backend again, gap closed to basically nothing.
Still not 100% sure this was happening on every order or just a subset, didn't dig into how far back it went. anyone dealt with event_id mismatches like this before, how'd you end up spotting it?