Why Do Facebook Conversions Show Up Days Later?

Nothing is broken when last Tuesday’s purchases climb on Saturday. Meta dates each result by the day the ad was served, then waits for the purchase to happen and for the event to reach it. A buyer who clicks on Monday and pays on Friday is counted on Monday, but only from Friday onward. Treat the most recent week as provisional, and judge a day once its attribution window has closed.

Why does Ads Manager add conversions to days that have already passed?

Because it reports by impression date. Meta’s example: if someone clicks an ad on Monday, Ads Manager reports on the impression served that Monday (How conversions are attributed). So when that person buys on Friday, the sale is filed under Monday. The Friday purchase does not exist in Meta’s data until Friday, so Monday’s row grows four days after Monday ends.

The same page says the default attribution setting for new ad sets is 7-day click or 1-day view. Under that setting, a click can collect a conversion for up to 7 days afterward, so any day in the last week can still gain results. Which window to report on and which to optimize for is a separate decision, covered in what is the difference between reporting and optimisation windows?

Commerce Manager works the other way. For tagged content and for events from connected data sources, it reports on the conversion date, so the same sale lands on Friday there (How conversions are attributed). The Marketing API lets you choose: its action_report_time parameter takes impression, conversion, mixed or lifetime. Meta’s reference gives the example of a person who saw an ad on 1 Jan and converted on 2 Jan: with impression the conversion shows on 1 Jan, with conversion on 2 Jan (Ad Account Insights reference).

How late can a conversion reach Meta?

Up to 7 days by default for website events sent through the Conversions API, and longer for offline events. Meta’s developer reference says a server event’s event_time “can be up to 7 days before you send an event”, and that if any event in a request is older than that, Meta returns an error for the whole request and processes none of it (Conversions API server event parameters).

Meta publishes recommended and maximum delays per use (Recommended and maximum delay times):

For attribution, the same page raises the web and app maximum to 62 days if you turn on extend attribution uploads in Events Manager settings. Meta adds that events sent after the maximum “will likely lead to poor performance” and may not be used. If your store or server batches purchases once a day, every conversion arrives at least a day late and is then filed under the earlier impression date.

Why do the last few days look weak and then recover?

Three effects stack up. First, recent days have not finished collecting: a click from yesterday still has most of its window ahead of it. Second, late server events land on past dates when they arrive. Third, Meta’s own processing keeps running: its Insights API guidance says insights refresh every 15 minutes, “may continue to update for a couple of days after an ad has completed”, and “do not change after 28 days of being reported” (Insights API best practices).

Meta also notes that a newly started ad can show no metrics for a short while, and calls these delays normal (Why an ad may not have data).

The practical result: yesterday’s cost per purchase usually looks worse than it will end up. Comparing today’s partial numbers with last month’s settled numbers will make every new ad look like a loser.

Are some of the late conversions estimated by Meta?

Some can be. Meta says it uses statistical modeling “where conversion data may be partial or missing”, for example because of people’s privacy choices, and that it also models how reported conversions are distributed across campaigns, ad sets and ads (About Meta’s modeled conversions). Modeled results are part of what fills in after the fact. The insights reference also lists an is_conversion_id_modeled breakdown among its options. Whether to trust those figures is its own question: see should I trust Meta modeled conversions?

How do I read recent results without being misled?

Judge closed periods and keep the open ones on a watch list. These steps assume the default 7-day click or 1-day view setting.

1. Set the Ads Manager date range to end 7 days ago before you pause or scale an ad on purchase results.
2. Open Ads Manager, click the Columns: Performance menu, select Compare attribution settings and add 1-day click beside 7-day click, to see how much of each day arrived later (Compare attribution settings).
3. Check with your developer or app how soon purchases are sent through the Conversions API; Meta recommends within 1 hour for sales ads.
4. Pull conversion-date results through the Marketing API with action_report_time=conversion when you must match store order dates.
5. Compare Meta with your store on weekly totals, not single days, since the two systems date each sale differently.
6. Re-run any report you shared within the last 28 days before you treat its numbers as final.

Day-level gaps against your store have other causes too, such as time zones and double counting: see why do Meta and my store report different purchase counts? and why does Meta show more purchases than Shopify? For the wider attribution picture, start with Can I Trust My Facebook ROAS? What to Check.

Can software help?

Bach.ai (by Wittelsbach) connects to a Meta ad account, audits it daily, finds revenue leaks with an estimated revenue impact, and proposes fixes. It applies a change on Meta only after you approve it.

FAQ

Why did yesterday’s ROAS change today?

Purchases made today by people who clicked or viewed an ad yesterday are credited to yesterday, because Ads Manager reports by impression date. Server events that arrived late, and Meta’s own processing, also update past days. Meta says insights can keep changing until 28 days after they are first reported.

Why does Commerce Manager show the sale on a different day?

Commerce Manager reports on the conversion date, while Ads Manager reports on the impression date. Take a click on Monday and a purchase on Friday: Ads Manager files the sale under Monday, the impression date, and Commerce Manager files it under Friday. Both are counting the same sale; they file it under different days.

When are Facebook conversion numbers final?

Meta’s Insights API guidance says insights “do not change after 28 days of being reported”. In practice, most movement happens within the attribution window, which is 7 days after a click under the default setting, plus the time your server events take to arrive.

Can I see conversions by purchase date in Ads Manager?

Ads Manager reports by impression date. To get the purchase date, use the Marketing API’s action_report_time=conversion, or Commerce Manager, which reports by conversion date for its own reports. Your store’s order report also dates sales by the day they happened.

Sources

Sources: Meta Business Help Center, How conversions are attributed in Commerce Manager, Recommended and maximum delay times for web, app and offline events, About Meta’s modeled conversions, Understand why an ad may not have data or metrics and Compare attribution settings in Meta Ads Manager; Meta for Developers, Ad Account Insights reference, Conversions API server event parameters and Insights API best practices (checked 2 Oct 2026).