Meta CAPI Event Time Too Old: Fixing the 7-Day Window Error

Meta rejects a Conversions API request when the event happened more than 7 days before you send it, so a booking from Monday has to be uploaded by the next Monday, unless it is a physical-store sale, which Meta asks you to send within 62 days. The whole request fails. Meta does not keep the newer rows and drop the old one.

The Problem

A job booked on Monday, April 6, and uploaded on Wednesday, April 8, is inside the window. The same booking uploaded on Tuesday, April 14, is more than 7 days old, and Meta rejects the request. The ad click can be older than 7 days. What matters is how long you waited after the booking.

A 30-day sales cycle still fits if you upload the closed job within a week of closing. It does not fit if the closed job sits in a spreadsheet for two weeks.

Solutions

1. Upload the event that just happened

Send the event within 7 days of that event, not within 7 days of the click:

Event	When it happened	When you upload	Result
Contact	Monday	Wednesday	Accepted
Booked job	Monday	The next Monday	Accepted
Booked job	Monday	Nine days later	The request is rejected
In-store sale	Monday	40 days later	Meta asks you to send a physical-store sale within 62 days

2. Put the hash on the same event

A hashed email or phone does not stretch the 7 days. Meta still checks the event time. Send the booking within 7 days of the booking, and include the hash on that same event so Meta can match it.

3. Upload More Frequently

Daily uploads ensure events are sent within hours of occurring — well within the 7-day window for early-funnel events.

How TUOCA Handles Meta’s Window

1. Priority routing — Meta uploads are processed before other platforms
2. 7-day validation — Records approaching the window are flagged
3. Multi-stage events — Configure relays to send Contact/Lead events immediately
4. Daily scheduling — Ensures minimal delay between event and upload