What is the Google Ads 7-day offline conversion limit?
The Google Ads 7-day offline conversion limit is a documented processing rule under which offline conversions uploaded more than seven days after the conversion event are excluded from Google’s data-driven attribution model, even though standard reporting columns still record them in full. In plain terms: if you upload a converted lead or a closed deal to Google Ads more than a week after it happened, the attribution engine ignores it, and only your standard reports still count it.
This matters because data-driven attribution is not just a reporting view. Its output feeds Smart Bidding. So a late-uploaded conversion does not merely go missing from one report; it is invisible to the algorithm that decides how to bid. The conversion still happened, your business still earned it, and your standard reports still show it, but as far as Google’s automated bidding is concerned, that conversion never existed and cannot teach the system anything.
The rule was not announced in a blog post or a product update. It sits inside the Google Ads Help Center page on attribution reports, in the section explaining why attribution reports disagree with standard reporting columns. It was spotted by Hana Kobzova and carried into wider circulation by Google Ads consultant Adriaan Dekker in a LinkedIn post, and reported by PPC Land in late August. Because it is a documented processing rule rather than a headline feature, many advertisers who rely on offline conversions do not yet know it exists.
If you run lead generation, B2B, or any business where the sale closes days or weeks after the click, this rule affects you directly, and this guide explains exactly what it does, who it hurts, and what to do about it.
What are offline conversions, and why does upload timing matter?
Offline conversions are conversions that happen after and away from the website click, a lead that becomes a qualified opportunity, a phone call that becomes a booked job, a form fill that becomes a signed contract, uploaded back into Google Ads once the outcome is known. Upload timing matters because the whole point of offline conversion import is that the outcome is separated in time from the click, and Google has now put a seven-day cap on how much of that separation the attribution model will tolerate.
Here is the mechanism. When someone clicks a Google ad, Google attaches a unique Google Click Identifier (GCLID) to the landing page. That identifier is captured at click time and stored alongside the lead’s record in your CRM. Later, when the lead converts offline, you upload the conversion back to Google Ads with that identifier, so Google can connect the closed deal to the original click. Google published an explainer on this mechanism, and the gap between click and outcome can be days or weeks, which is exactly why offline conversion import exists.
The new limit adds a constraint that did not obviously exist before: the outcome may take weeks, but the upload must reach Google within seven days of the conversion event for the attribution model to use it. Miss that window, and the conversion lands in standard reports but bypasses the model. This is a timing rule about when you upload, layered on top of the older reality that conversions happen late.
Who does the Google Ads 7-day offline conversion limit affect most?
The Google Ads 7-day offline conversion limit affects lead generation and B2B advertisers most, because they are the businesses whose conversions happen furthest from the click and whose upload processes are most likely to lag. Any advertiser who relies on offline conversion data feeding Smart Bidding is exposed.
The businesses most at risk are:
- B2B and long-sales-cycle advertisers. When a deal closes a fortnight or more after the click, the sales team logs it, and it gets uploaded on a weekly or monthly batch, the upload can easily arrive more than seven days after the conversion event, especially if “the event” is dated to the deal close.
- Lead-gen businesses using CRM batch uploads. Many advertisers upload offline conversions on a schedule, weekly, or worse, monthly, which can push uploads past the seven-day window even when the conversion itself was recent.
- Anyone relying on manual or infrequent uploads. If a person exports a CRM report and uploads it when they remember, timing slips are inevitable.
- The long-cycle niches specifically. Businesses like commercial cleaning, where the average sales cycle runs around 167 days, or considered-purchase trades like excavation and hardscaping, live and die by offline conversion data, and are precisely the accounts this rule can quietly starve.
The advertisers least affected are ecommerce businesses whose conversions happen on-site at click time, and any account whose offline upload process already runs daily and promptly. If your conversions are online and immediate, this rule is largely academic. If your real revenue closes offline and later, it is not.
Why does this rule cause two different conversion numbers in one account?
This rule causes two different conversion numbers in one account because standard reporting columns and the data-driven attribution model apply different rules to the same set of events. Standard reporting columns record every uploaded offline conversion retroactively, regardless of when it arrives; the attribution model ignores any that arrived more than seven days after the event. Same account, same conversions, two totals.
This gap is the practical danger, because those two numbers sit side by side in the same account and are frequently compared. An advertiser looking at standard reporting sees the full picture, including late uploads. An advertiser looking at attribution reports, or relying on Smart Bidding which is fed by the attribution model, sees a smaller number that silently excludes the late arrivals. Neither number is wrong; they are answering different questions. But if you do not know the rule exists, the discrepancy looks like a tracking bug, and you may waste hours hunting a problem that is actually documented behavior.
The deeper issue is which number drives your bidding. Because Smart Bidding optimizes on the attribution model’s output, the smaller, late-excluding number is the one steering your spend. So even if your standard reports look healthy, your bidding may be learning from an incomplete set of conversions, missing exactly the late-closing deals that are often your most valuable.
How does this affect Smart Bidding and performance?
This rule affects Smart Bidding by removing late-uploaded conversions from the data the algorithm learns from, which can degrade bidding accuracy for any account whose valuable conversions tend to arrive late. If your best deals close weeks after the click and get uploaded outside the seven-day window, Smart Bidding never learns what led to them, so it cannot find more of them.
The chain of consequences works like this:
- A valuable lead clicks an ad and, weeks later, becomes a closed deal.
- The deal is uploaded to Google Ads more than seven days after it closed.
- Standard reports record it, but the attribution model ignores it.
- Smart Bidding, fed by the attribution model, never sees it.
- The algorithm does not learn which keywords, audiences, and campaigns produced that valuable late-closing deal.
- Over time, bidding optimizes toward the conversions it can see, which may be the faster, smaller, less valuable ones, and away from the slow, high-value deals that were your real prize.
This is the same failure mode we warn about across all measurement work: when the conversion signal feeding automation is incomplete or wrong, the automation confidently optimizes toward the wrong thing. We have written before about how optimizing toward the wrong conversion signal quietly wrecks an account, and this rule is a new, specific version of that problem: not a wrong signal, but a silently truncated one.
What should you do about the Google Ads 7-day offline conversion limit?
The single most important action is to upload offline conversions within seven days of the conversion event, ideally daily and automatically, so they reach the data-driven attribution model and feed Smart Bidding. Everything else follows from getting your upload timing inside the window.
Here is what to do, in order:
- Move to daily, automated uploads. Replace weekly or monthly batch uploads with a daily automated pipeline, so no conversion waits more than a day, let alone seven, before it is uploaded. This is the core fix.
- Audit your current upload latency. Check how long, on average, your offline conversions currently take to go from event to upload. If it is regularly more than seven days, you have conversions silently missing from attribution right now.
- Understand what “the event” date means in your setup. Confirm whether your conversion event is dated to the lead date or the deal-close date, because that determines when the seven-day clock starts. Uploading a deal that closed today is fine; uploading a lead whose event date is three weeks ago may already be outside the window.
- Reconcile your two numbers. Compare your standard reporting conversion total against your attribution total. If they diverge, late uploads are the likely cause, and closing the timing gap will bring them back into line.
- Use enhanced conversions for leads (EC4L) alongside GCLID. A robust offline setup uses both the click identifier and hashed first-party data, which improves match rates and resilience. This does not change the seven-day rule, but a healthy, prompt pipeline is easier to maintain when the whole measurement stack is sound. We cover the full approach in our guide to conversion tracking.
- Automate the pipeline rather than relying on manual uploads. Manual exports and uploads are where timing slips happen. A CRM integration that pushes conversions automatically is the durable fix.
The goal is simple: get every offline conversion uploaded promptly, within the seven-day window, so the model and the bidding see your real revenue, including the valuable deals that took weeks to close.
Does this change how offline conversions appear in standard reports?
No, this rule does not change how offline conversions appear in standard reporting columns. Standard reports continue to record every uploaded offline conversion in full, retroactively, regardless of how long after the event it arrives. The seven-day limit applies only to the data-driven attribution model, not to standard reporting.
This is precisely why the rule is easy to miss. If you only ever look at standard reporting columns, you will see all your offline conversions, including late uploads, and everything will look normal. The exclusion is invisible in the place most advertisers look. It only shows up when you compare standard reports against attribution reports, or when you notice Smart Bidding behaving as if it cannot see your best late-closing conversions. The safest assumption is that the rule is affecting your bidding even when your standard reports look complete.
How does this fit into Google’s broader changes to offline data?
This rule is one step in a long sequence of changes Google has made to how offline conversion data enters its advertising system, all tightening the requirements on advertisers who feed offline conversions into Google Ads. Google has been steadily raising the bar on offline data quality, freshness, and pipeline compliance.
Recent related changes include:
| Change | What it did |
|---|---|
| Data Manager API launch | Became the required successor for offline conversion workflows |
| Ads API new-adopter cutoff for offline imports | Stopped accepting new integrations via the old method, requiring migration |
| Session attribute and IP restrictions | Removed certain attribution signals from conversion imports |
| The 7-day upload rule | Excludes late-uploaded offline conversions from attribution and bidding |
The common thread is that Google increasingly rewards advertisers with clean, prompt, well-integrated offline data pipelines and penalizes those relying on slow, manual, or outdated processes. The practical takeaway is consistent across all of it: if offline conversions are part of how you measure success, your data pipeline needs to be automated, prompt, and maintained, not an afterthought. This rule simply adds a specific, seven-day cost to letting uploads lag.
Key facts about the Google Ads 7-day offline conversion limit
| Question | Answer |
|---|---|
| What is the rule? | Offline conversions uploaded more than 7 days after the event are excluded from data-driven attribution |
| Does it affect standard reports? | No, standard reports record all uploaded conversions in full |
| Does it affect Smart Bidding? | Yes, because Smart Bidding is fed by the attribution model |
| Who is most affected? | Lead gen, B2B, and long-sales-cycle advertisers |
| Who is least affected? | Ecommerce and any account uploading offline conversions daily |
| Where is it documented? | Google Ads Help Center, attribution reports section |
| The core fix | Upload offline conversions within 7 days, ideally daily and automated |
Frequently asked questions
What is the Google Ads 7-day offline conversion limit? It is a documented processing rule under which offline conversions uploaded more than seven days after the conversion event are excluded from Google’s data-driven attribution model, though standard reporting columns still record them in full. Because data-driven attribution feeds Smart Bidding, a late-uploaded conversion is invisible to the algorithm that decides how to bid, even though the conversion genuinely happened and appears in standard reports.
Does the 7-day limit delete my late conversions? No. Late-uploaded offline conversions still appear in full in standard reporting columns; they are not deleted. What happens is that they are ignored by the data-driven attribution model, and therefore by Smart Bidding. So you keep seeing them in standard reports, but they stop influencing how the algorithm optimizes your bids, which is where the real cost lies.
Who does the 7-day offline conversion rule affect? It most affects lead generation, B2B, and long-sales-cycle advertisers, whose valuable conversions close days or weeks after the click and are often uploaded on weekly or monthly batches. Businesses with long cycles, such as commercial cleaning or considered-purchase trades, are especially exposed. Ecommerce advertisers whose conversions happen on-site at click time, and anyone already uploading daily, are largely unaffected.
Why do my Google Ads reports show two different conversion totals? Because standard reporting columns and the data-driven attribution model apply different rules to the same events. Standard columns record every uploaded offline conversion regardless of timing, while the attribution model excludes any uploaded more than seven days after the event. Same account, same conversions, two totals. It is documented behavior, not a tracking bug, and closing your upload-timing gap brings the numbers closer together.
How do I fix the 7-day offline conversion problem? Upload offline conversions within seven days of the event, ideally through a daily, automated pipeline rather than weekly or monthly manual batches. Audit your current upload latency, confirm what date your conversion event uses so you know when the clock starts, and reconcile your standard and attribution totals to spot missing late uploads. Automating the CRM-to-Google-Ads pipeline is the durable fix, since manual uploads are where timing slips happen.
Does this rule affect Smart Bidding? Yes, and this is the most important consequence. Smart Bidding optimizes on the data-driven attribution model’s output, so any offline conversion excluded for being uploaded late is also invisible to the bidding algorithm. If your most valuable deals close slowly and get uploaded outside the window, Smart Bidding never learns what produced them and cannot find more, gradually steering spend toward the faster, often less valuable conversions it can see.
Is uploading within 7 days enough if my deals take weeks to close? Yes. The seven-day window applies to how quickly you upload after the conversion event, not how long the deal took to close. A deal can take two months to close; as long as you upload it within seven days of it closing, it reaches the attribution model. The problem arises only when the upload itself lags, or when the event is dated to the original lead rather than the actual conversion.
About The Author
