Meta Ads Attribution Window: What It Is and Why It Matters

A campaign can be generating real deposits and still look like it isn’t converting in Meta’s Ads Manager. Most of the time that happens, the cause isn’t the campaign. It’s the Meta Ads attribution window. This guide explains what it is and why ignoring it leads to the wrong decisions.

What is the Meta Ads attribution window

The attribution window is the period, counted from the person’s interaction with the ad, during which Meta credits a conversion back to that specific ad. It’s the time limit inside Meta’s attribution model. If the conversion event happens within that period, it counts for the campaign; if it happens later, Meta may no longer associate the event with it, even if the event itself is correct and arrived normally.

Click and view windows are different

Meta works with two types of window, which can be combined in the same campaign: the click window (how long after someone clicks the ad a conversion still counts) and the view window (how long after someone only sees the ad, without clicking, a conversion still counts). Meta’s default is 7 days after the click or 1 day after the view, but the exact setting can vary by account and by campaign objective, so check yours instead of assuming.

Meta’s window vs. Track4you’s attribution window

If you use Track4you, you’ll come across the same term somewhere else, and they’re two different things:

• Meta’s attribution window decides whether Ads Manager credits a conversion to an ad (the default of 7 days after the click / 1 day after the view). It applies to every event the pixel receives: enter_channel, FTD, deposit. That’s the window this article is about.
• Track4you’s attribution window is the period during which a channel join keeps being linked to the click that brought the lead in: up to 7 days after the click, following Facebook’s attribution rules. It’s what lets you see, in “Métricas” (Metrics), which campaign (from the ad’s UTMs) each person who joined came from.

Meta’s window answers “how much does Meta credit to this ad”; Track4you’s answers “who actually joined, and through which path.”

And in Integrations (registration, FTD, deposit) there’s no time limit on Track4you’s side: every conversion the platform sends back through the postback, even weeks after the click, is forwarded to the pixel and becomes signal for the algorithm. Whether it appears credited to a campaign in Ads Manager is decided by Meta’s window.

That’s also why the Track4you dashboard and Ads Manager don’t match one to one: different clicks are counted, different windows apply and the dates are recorded differently.

Why it matters more in Telegram funnels

The channel join (enter_channel) usually happens minutes after the click, comfortably inside any reasonable window in the vast majority of cases. The FTD is a different story: in several niches, people join the channel, follow the content, build trust and only decide to deposit days later. See the guide to S2S postbacks in iGaming for how that event reaches Meta. The longer that cycle, the higher the chance the deposit lands outside the window set in Meta, even if the postback fired correctly and the event reached Meta through the Conversions API.

What happens when the event arrives outside the window

The event doesn’t disappear. It reaches the pixel and shows up in Meta’s Events Manager as received, with the correct value, and it still counts as signal for the algorithm. What it doesn’t do is get credited back to that ad or campaign, because it falls past the period the window recognizes. So it doesn’t count as a conversion for that campaign in Ads Manager. From the point of view of someone reading the campaign report, results look worse than they are: the deposit happened and reached Meta, it just wasn’t credited there.

How it distorts the way you read results

A campaign can be bringing in leads who stick around and deposit consistently, just outside the window, and still look like it’s underperforming, because the FTD count Ads Manager shows is artificially low. A common mistake is pausing or cutting budget on that campaign thinking it doesn’t convert, when in fact the conversion reached Meta. It just wasn’t credited to the campaign because it fell outside the window. See the guide to optimizing campaigns for FTD for why running both objectives in parallel keeps you from depending on that limited number alone.

What to do about it

• Review the window set on the campaign if your deposit or decision cycle tends to be longer, within the options Meta’s interface allows.
• Run an enter_channel campaign in parallel to the FTD one: the join happens minutes after the click, so the window barely cuts that result, and signal volume holds up while FTDs are still few.
• Treat the postback as the source of truth for the real number of deposits. The conversion comes back from the platform with the click_id of the original click, so you see what the platform confirmed, including what Meta doesn’t credit back to the campaign.
• Look at retention alongside FTD, not just the isolated number. A lead who stays in the channel tends to deposit later, which is exactly the kind of conversion the attribution window loses most.

Common mistakes

• Assuming the window is always 7 days without checking the account: the actual setting may be different, and decisions based on a wrong assumption are expensive.
• Pausing a campaign for “lack of FTDs” without checking the postback: the campaign may be converting for real, just outside what Ads Manager can show.
• Treating Events Manager as if it were the campaign report: an event appearing there doesn’t mean it was attributed to that particular campaign.
• Ignoring your niche’s real decision cycle: niches with slower decisions (higher ticket, more research before committing) suffer more from this mismatch than fast-decision niches.

How Track4you helps in this flow

On the Pro and Enterprise plans, Track4you Integrations bridge the deposit: the integration’s promo link generates a unique click_id on every click and sends the lead to the platform’s sign-up page with that value in the URL; the platform returns the click_id in the S2S postback when the conversion happens, and Track4you sends the event to the pixel. A registration arrives as CompleteRegistration, a deposit as Purchase and the FTD as the custom event FTD (which has to be confirmed in Events Manager before it can be used in a campaign).

There’s no time limit on Track4you’s side: every conversion that arrives through the postback is sent to the pixel, even weeks after the click, and becomes signal for the algorithm. Whether it appears credited to a campaign in Ads Manager is decided by Meta’s attribution window (default: 7 days after the click / 1 day after the view). Every conversion that arrives also lands in the integration’s event history and in the Registrations, FTDs and Deposits cards on the Dashboard: the number the platform confirmed, to compare with what Ads Manager credited within its window.

Together with enter_channel and left_channel, which come from the funnel, that gives you visibility over the whole funnel, including the part Meta alone can’t credit back. Plans are at track4you.app.

Frequently asked questions

Terms like FTD, CAPI, postback and click_id have quick definitions in the glossary. To understand how CAPI and the Pixel work together, see the guide to the Facebook Conversions API.

Conclusion

The attribution window isn’t a minor technical detail. It’s the filter that decides what Meta shows as your campaign’s results, and it’s structurally shorter than the decision cycle in several niches. Understanding that changes how you read Ads Manager: a low FTD count isn’t always a sign of a bad campaign, and the postback, not Ads Manager, is the source that shows what really happened. With Track4you, that conversion reaches the pixel even when Meta doesn’t credit it to the campaign.