Will Meta and Google take it?

Meta rejects the whole request when any event time falls a week or more before the upload. The server-side spec says that if any event_time occurred more than seven days ago, Meta returns an error and processes no events.

A sale approved two weeks later still clears that check when the timestamp is the payable day, because the upload and the timestamp share a day. Stamping the click fails once that click is already a week old. The checkbox is that second case. With the box unchecked, the checker uses the payable day as the timestamp.

Facebook also limits how long a conversion can follow an ad click. That ClickMagick article puts the window at ninety days for events sent with an fbclid. If the wait runs past those ninety days, the checker flags the fbclid.

When a browser Purchase already fired on the click, a later server copy can be folded into it. The same spec asks for one event id on both copies, and the match runs for about forty-eight hours. The pixel and Conversions API guide shows where that id goes.

Receiving the network call and uploading the sale are two jobs. Sending the network sale to Meta after approval covers a tracker postback once the offer approves, and a checkout event when that checkout is the payment you record.

When both labels sit inside their windows, three sends can still carry the sale.

RedTrack's Facebook tracking page describes a pre-built Conversion API integration that sends online and offline conversion data back to Meta. Its Google Ads page describes a pre-built integration that sends online and offline conversion data back to Google. The entry-plan checker names the starting plan that documents a Meta send and a Google send.

ClickMagick's pricing page lists Audience Optimization on the Starter plan. The article above says those conversions go out in real time, as the tracked sale happens. If that tracked sale is the moment the network approves, that is when the conversion leaves.

A checkout event that fires when the order is paid matches that payment. Use it when the checkout is what got paid. A network approval that arrives later stays on the postback route in the two guides.

When the gclids are already in a system you run, Google's legacy upload guide says click-id conversions use the type UPLOAD_CLICKS. The June move is why that import belongs on Data Manager.

The count subtracts the click from the payable day, in calendar days. From 1 October 2026 to 15 October 2026 is 14 days. These labels come from vendor documentation and long-term user reports. The same reading is on the methodology page.

Meta is labeled only when that box is checked. At seven days or under, the event time passes, and it also passes when the timestamp is the payable day. Check the click-time box only if the upload would stamp the click. Past a week, that stamp is the case Meta rejects for a stale timestamp. Past the Facebook window, an fbclid send is the one that fails.

Google is labeled only when that box is checked. If the wait runs longer than the number in the field, the click falls outside the lookback you set, and a shorter wait falls inside that same lookback. Posting on the click, covered above, is why the payable day can come later and the click can still match.

After you create a new offline conversion action, Google asks you to wait four to six hours before the first upload.

From 13 July 2026 to 21 October 2026 is 100 days. Leave the Google field at 90 and that wait overshoots both the field and the Facebook window.