Skip to content

Purchase events arrive late

Purchases are recorded hours or days after the order was placed.

Why it matters

Late events land on the wrong day in reports, and platforms may discard server events older than their window.

How to fix it

  1. Check whether a server-side integration batches events; send them as soon as the order is created or paid.
  2. For Meta, the Conversions API accepts events up to 7 days old; older events are dropped.
  3. If late events come from payment methods that settle later, decide whether to send purchases on order creation or on payment, and keep it consistent.

After a fix, TagGap confirms it on the next comparison run. Questions: support@taggap.com.