What offline conversion import is
Offline conversion import is a way to report something that happened after the website visit, such as a lead being qualified, an opportunity being created or a customer being won, back to Google Ads. Each outcome is matched to the original Google Ads interaction using an identifier saved when the lead came in, so Google Ads can record it as a conversion.
Offline conversion import is one mechanism among several, and not every business needs it. It is worth considering when lead quality varies enough that the initial conversion is not a reliable guide.
Why the initial lead conversion is often not enough
The initial conversion happens immediately, so it is quick and plentiful, but it can't tell a customer from a time-waster, a supplier or spam. Campaigns that generate the most form submissions are not always the ones that generate the most customers. Without downstream feedback, optimization and reporting can favor volume over value.
Online conversion vs offline outcome
- Online conversion: recorded as it happens on the website or call, such as a confirmed form submission.
- Offline outcome: a later result recorded elsewhere, such as in a CRM, after review, a conversation or a sale.
The online conversion is the foundation. The offline outcome adds depth. If the online tracking is wrong, importing outcomes on top of it only carries the problem forward.
What business outcomes can be sent back
The right outcomes depend on the business, but common candidates are:
- A valid lead, once spam and duplicates are filtered out.
- A qualified lead that meets your criteria.
- An opportunity, such as a booked consultation, quote or estimate.
- A customer, a closed-won deal or a completed job, where volume allows.
Each stage that is sent back needs to be reliably recorded, consistently defined and numerous enough to be useful. Fewer, well-defined outcomes are better than many loosely defined ones.
Capturing click and lead identifiers
Offline outcomes can only be matched if the identifier from the original click is saved with the lead. This is the most common failure point, because the identifier has to survive the journey from the landing page to the form to the CRM record.
- Capture the identifier on the landing page when the visitor arrives.
- Store it with the lead at submission, for example in a hidden form field.
- Make sure it reaches the CRM record and is not overwritten or dropped.
- Give each lead a stable lead ID of its own, so outcomes can be traced and deduplicated.
GCLID and other applicable identifiers
Different identifiers apply in different situations. The table below summarizes them conservatively; which one is available depends on the campaign and source, consent, the browser and device environment, the tracking setup and the Google Ads configuration.
| Identifier | What it is | Where it applies | Caveat |
|---|---|---|---|
| GCLID | The Google click identifier added to the landing page URL when auto-tagging is on. | Standard Google Ads clicks where auto-tagging and the page URL carry it through. | Must be captured and stored with the lead. Not every lead will have one. |
| GBRAID / WBRAID | Alternative click identifiers used in some privacy-restricted contexts. | Where they apply, such as certain iOS and app-related journeys. | Handled separately from GCLID; availability depends on the environment. |
| Enhanced conversions for leads | Hashed first-party contact data, such as an email or phone number, matched by Google. | Where the setup, consent and form data allow it. | Needs consent and its own review. Not a drop-in replacement for the click ID. |
| First-party lead ID | Your own stable ID for the lead, in the website and the CRM. | Everywhere, as the business's own link between lead and outcome. | Helps tracing and deduplication; it does not match by itself to a Google click. |
Do not assume every lead has a click identifier. Some leads arrive without one, for example from direct visits, other channels or restricted environments, and cannot be matched back to a Google Ads click.
CRM and lead-status connection
Conceptually, the flow is: an ad click leads to a lead record; the identifier is preserved on that record; a salesperson or process updates the lead status in the CRM or lead sheet; a selected status becomes eligible for import; and the conversion is matched back to the click where possible.
Mapping lead stages to conversion actions
Each stage you want to report becomes its own conversion action in Google Ads, with a clear name. A hypothetical mapping looks like this. It is an illustration, not a prescription.
Hypothetical mapping, not a prescription
| Lead stage | Possible conversion action | Considerations |
|---|---|---|
| Raw lead | Lead (online) | Quick and plentiful. Often stays a useful signal and may be Primary at first. |
| Valid lead | Valid lead | Filters spam and duplicates. Optional if the raw lead is already clean. |
| Qualified lead | Qualified lead | A deeper signal. Can become Primary when volume and reliability allow. |
| Opportunity | Opportunity | Useful where a consultation, quote or estimate is a clear step. |
| Customer | Customer / closed-won | The clearest outcome but often late and low volume. Often best for analysis. |
Qualified lead conversion actions
Qualified lead tracking is the measurement concept: deciding which leads were genuinely worth having and recording that. Offline conversion import is one possible mechanism for sending those downstream outcomes back into Google Ads. Keeping the two ideas separate makes it easier to design the process and to explain it to the team who set the statuses.
The full guide to qualified lead tracking in Google Ads
Customer and closed-won outcomes
A closed-won outcome is the clearest business result, but it usually arrives late and in small numbers. For businesses with a long sales cycle or few sales, there may not be enough closed outcomes for bidding to learn from. In those cases, a qualified lead or opportunity can be a more practical signal, with customer outcomes used for analysis.
Primary vs Secondary considerations
An initial raw lead may remain useful as a conversion signal. A qualified lead can represent a deeper conversion. A customer or closed outcome may represent an even later stage. That does not mean every downstream action should be Primary. Classification depends on conversion volume, the length of the sales cycle, the business objective and how reliable the data is.
Primary vs secondary conversions in Google Ads: the detailed guide
Deduplication
- Each real outcome should be counted once per conversion action.
- Use a stable lead or order ID where the import method supports it, so repeated uploads are not counted twice.
- Do not record the same outcome through both an offline import and another tracking path under the same name.
- Keep raw leads and qualified outcomes as separate, clearly named conversion actions.
- Confirm how your chosen import method treats a repeat upload before relying on it.
Timing and data-quality considerations
- Outcomes usually arrive days or weeks after the click, so recent performance looks incomplete until reviews catch up.
- Timestamps should be accurate and consistent, including time zone, because they place the outcome relative to the click.
- There are platform limits tied to the click and the conversion action settings. Check Google's current documentation instead of relying on a remembered number.
- Import frequency matters less than regularity: a steady, reviewed process beats occasional large uploads.
- Imported data should be checked before it is allowed to influence bidding.
Example offline conversion flow
A typical flow for a lead-generation business looks like this. Each step is a handoff where information can be lost.
- Google ad clickA click identifier is created
- Landing pageThe identifier is captured
- Form / call / bookingThe action is recorded
- Lead createdStored with the identifier
- CRMThe lead record is kept
- Lead reviewedA status is set
- Qualified / opportunity / customerA selected outcome
- Outcome sent backMatched to the original click
- Better measurementReporting and optimization improve
A worked example (hypothetical numbers)
The numbers below are a hypothetical example, not an Adlyvo result and not a case study. Imagine one campaign produced these outcomes over a period:
Hypothetical example, not an Adlyvo result
- Form leads40
- Valid leads25
- Qualified leads12
- Customers5
If Google Ads sees only the 40 form submissions, it cannot distinguish the 5 customers from the 35 leads that did not become customers. It does not know customer outcomes unless they are sent to it. With downstream outcome feedback, such as the 12 qualified leads or the 5 customers, measurement can reflect deeper business value, and campaigns can be compared on more than form volume.
Common implementation mistakes
- Not capturing click identifiers: without them, outcomes cannot be matched.
- Losing identifiers before CRM entry: the value is captured on the page but dropped on the way into the record.
- Inconsistent lead statuses: different people use different labels for the same stage.
- Duplicate uploads: the same outcome sent more than once.
- Wrong timestamps: outcome times that are missing, in the wrong time zone or earlier than the click.
- Importing test leads: internal test submissions treated as real outcomes.
- Importing spam or unqualified leads as valuable conversions.
- Changing lead IDs unexpectedly: the link between lead and outcome breaks.
- Using unreliable data for bidding: small or inconsistent outcome data steering automation.
- Mixing raw leads and qualified outcomes without clear naming.
- No deduplication strategy.
- Treating upload success as proof of correct business logic: an accepted file does not mean the right outcomes were sent.
When offline conversion import is worth using
It is usually worth the effort when:
- Lead quality varies enough that raw form counts are a poor guide.
- Click identifiers are reliably captured and stored.
- Lead outcomes are recorded consistently by a person or process.
- There is enough outcome volume to analyze, and ideally to learn from.
It is usually too early when lead volume is very low, when outcomes are not recorded, or when basic conversion tracking is not yet reliable. Fix the foundation first. Not every business needs it.
How Adlyvo approaches offline lead feedback
- Define the meaningful downstream outcomes for the business.
- Preserve click and lead identifiers where they are required.
- Map CRM lead stages to clear conversion actions.
- Configure conversion actions and separate raw leads from qualified outcomes.
- Avoid duplicates.
- Validate imported outcomes before relying on them.
- Use the downstream data for analysis and, where appropriate, for optimization.
Server-side tracking is a separate decision. Offline conversion import does not require it, and it is added only where browser-side measurement has a real gap.
How Adlyvo sets up Google Ads conversion tracking
Google Ads conversion tracking service
Google Ads server-side conversion tracking explained
Managing Google Ads campaigns around qualified leads
How Adlyvo works as a Google Ads specialist
Google Ads call tracking: measuring phone leads
Verified account results with tracked calls and conversions
Frequently Asked Questions
What is offline conversion import in Google Ads?
A way to send later outcomes, such as qualified leads or customers, back to Google Ads and match them to the original ad interaction, using an identifier saved with the lead.
Why should I import qualified leads?
Because the initial form or call conversion cannot show lead quality. Importing qualified leads lets reporting, and where appropriate optimization, reflect which leads were genuinely worth having.
Do I need a CRM?
Not strictly, but you need a reliable record of lead outcomes tied to an identifier. A CRM is the usual place for that, though a well-kept lead sheet can serve a small operation.
What is a GCLID?
The Google click identifier added to the landing page URL when auto-tagging is on. Storing it with the lead lets an outcome be matched back to the click that produced it.
Can phone leads be imported as offline conversions?
Where the call source and setup support it, yes. Matching depends on the identifier or call details available, so it varies by setup. See the call tracking guide for the distinctions.
Can customer outcomes be sent back to Google Ads?
Yes, as imported conversions, if each customer outcome can be matched to the original click. For small numbers of sales, they are often better used for analysis than bidding.
Does offline conversion import require server-side tracking?
No. They are different mechanisms. Server-side tracking is added only where browser-side measurement has a real gap.
How do I prevent duplicate offline conversions?
Count each outcome once per conversion action, use a stable lead or order ID where the method supports it, keep raw and qualified actions separately named, and avoid recording the same outcome through two paths.
Should qualified leads be Primary conversions?
Sometimes. It depends on conversion volume, the sales cycle, the objective and data reliability. Until qualified outcomes are reliable and plentiful, the raw lead often stays Primary with qualified leads tracked alongside.
How long after a lead can an offline outcome be sent back?
There are platform limits tied to the click and the conversion action settings, and they can change. Check Google's current documentation for the limits that apply to your account, and send outcomes promptly instead of relying on a window.
Related resources and services
Google Ads qualified lead tracking guide
Primary vs secondary conversions guide