01
Record
- Timestamp, in one timezone, at send — not at queue time.
- Event name and the event id you generated. This is the field that makes deduplication provable.
- Order or cart reference, so a row can be joined back to the store record.
- Value and currency, exactly as sent — the two fields most often wrong on a purchase.
- Identifier set present: hashed email, phone, external id, fbp, fbc, client IP, user agent.
- HTTP status and the platform's response body, truncated but kept. A 200 with an error body is a failure.
- Retry count and why it retried — 429 and 5xx only; retrying a 4xx adds noise and can look like abuse.
- Deduplicated outcome: did the platform merge this with the browser event, or count a second purchase.
