Offline conversion tracking means sending what happens after a lead is created (a qualified lead, a booked appointment, a closed sale) from the CRM back to Google Ads and Meta, matched to the ad click that started it. Without it, ad platforms only see form fills and calls, so automated bidding learns to produce more form fills, whether or not they ever become customers. With it, bidding can learn from the outcomes the client actually gets paid for.
Key takeaways
- Offline conversion tracking only works if every lead is saved in the CRM with its click IDs (gclid, gbraid, wbraid, fbclid) or with customer data that can be matched, such as a hashed email.
- Pick two or three CRM stages that mean something, such as qualified, booked and won, and decide which one is the primary conversion for bidding.
- Google now routes offline imports through Data Manager and the Data Manager API; native CRM connectors, scheduled uploads and enhanced conversions for leads are all valid paths.
- Meta accepts CRM events through the Conversions API, matched on lead ID, fbclid-based click ID or hashed customer data.
- Recent dates always look low, because stages change days or weeks after the click. Judge the setup on matched records and diagnostics, not on last week's totals.
What is offline conversion tracking?
An "offline" conversion is any conversion that happens somewhere the ad platform's tag can't see. For most lead-gen clients that means inside the CRM: a sales rep marks a lead as qualified, a call is booked, a deal is won. The word "offline" is a little misleading. The event usually happens in software, just not on the website where the Google tag or Meta Pixel lives.
Offline conversion tracking closes that loop. The ad click leaves an identifier on the lead. The CRM keeps it. When the lead moves to a stage you care about, the CRM (or a connector) sends that stage back to the ad platform with the identifier, a timestamp and, ideally, a value. The ad platform matches it to the original click and records a conversion against the campaign, ad group and keyword that produced it.
Google calls this offline conversion import, and its newer, more durable form enhanced conversions for leads. Meta handles it through the Conversions API, with a dedicated CRM integration for lead ads. The names differ, but the pattern is the same everywhere: capture an identifier at the start, keep it with the lead, send the outcome back later.
Why does bidding need offline conversions?
Smart Bidding and Meta's delivery system optimize toward whatever you tell them is a conversion. If the only conversion is "form submitted," they will find people who submit forms. That includes students, job seekers, competitors, spam and people who wanted a different service. None of that is a tracking error. It is the system doing exactly what it was asked.
When qualified leads or sales are sent back, the platform gets a much better description of a good outcome. It can learn which searches, audiences and placements produce customers rather than contacts. We are careful about what we promise here: offline conversions do not guarantee better results on their own. They give bidding correct information. What the client's campaigns do with better information depends on volume, budget, offer and everything else in the account.
There is a second benefit that agencies often value more than the bidding one: reporting. Once won deals flow back, you can show a client cost per qualified lead and revenue by campaign inside the ad platform, instead of arguing about form fills.
Diagram
Suggested diagram: a left-to-right flow. An ad click carries a gclid or fbclid onto the landing page; a form stores it in hidden fields; the CRM saves it with the lead; the lead moves through stages (new, qualified, booked, won); each stage change is sent back to Google Ads and Meta, where it is matched to the original click. Alt text: "Flow showing a click ID travelling from the ad click to the CRM and back to Google Ads and Meta as stage-based offline conversions."
How do you capture GCLID, GBRAID, WBRAID and FBCLID?
Everything downstream depends on this step, and it is the step most often missing when we audit an account. If the click ID never reaches the CRM, no later integration can match the lead back to an ad.
What each identifier is
- gclid is the Google Click ID. Google Ads adds it to the landing page URL when auto-tagging is on.
- gbraid and wbraid are the parameters Google uses for some iOS traffic where a gclid isn't passed. Google's documentation describes wbraid for web measurement and gbraid for app measurement. Store whichever arrives.
- fbclid is the parameter Meta adds to outbound clicks. Meta's Pixel turns it into the
_fbc cookie, and the Conversions API accepts it as the fbc click ID.
The capture pattern
- Confirm auto-tagging is on in every client Google Ads account. Without it there is no gclid to capture.
- Read the parameters on landing. A small script or GTM tag reads gclid, gbraid, wbraid and fbclid from the URL and stores them in a first-party cookie or local storage, because the visitor rarely converts on the landing page itself.
- Write them into hidden form fields on every lead form, including multi-step forms and embedded booking widgets.
- Map the hidden fields to CRM properties. Create properties such as
gclid, gbraid, wbraid and fbclid on the contact or lead record, and map the form fields to them.
- Collect contact data too. Email and phone let Google and Meta match leads with no click ID, which matters for enhanced conversions for leads and for Meta.
- Test with a real click. Click a live ad (or add a test gclid to the URL), submit the form, and check the value landed on the CRM record.
A minimal version of the landing-page script looks like this. In production we usually run it through GTM and respect the client's consent setup before storing anything.
<script>
(function () {
var params = new URLSearchParams(window.location.search);
var keys = ["gclid", "gbraid", "wbraid", "fbclid"];
var maxAge = 90 * 24 * 60 * 60; // seconds
keys.forEach(function (key) {
var value = params.get(key);
if (value) {
document.cookie = "ag_" + key + "=" + encodeURIComponent(value) +
"; max-age=" + maxAge + "; path=/; SameSite=Lax";
}
});
// On form load, copy cookie values into hidden inputs named gclid, gbraid, wbraid, fbclid
})();
</script>
Two traps to watch for. First, forms on a different domain (a scheduling tool, a hosted form) need the click ID passed across, or they need their own capture. Second, some CRMs overwrite properties on every new submission, so a returning visitor's original click ID gets replaced by a blank. Decide whether the field should keep the first or latest value, and set the form mapping to match. Our guide on lead source attribution in HubSpot and GoHighLevel covers these field choices in more detail, and a consistent UTM naming convention keeps the source fields next to the click IDs readable.
Which CRM stages should become conversion actions?
Before anything is connected, agree with the client which stages count. This is a business conversation, not a tracking one, and it is the step that decides whether the whole project is useful.
A sensible default ladder
| Stage | What it means | Typical use in Google Ads |
| Lead | Form or call received | Online conversion from the tag; often secondary once offline stages are reliable |
| Qualified lead | Sales confirmed fit: right service, area, budget | Often the best primary goal for lead-gen accounts |
| Booked / opportunity | Appointment, demo or quote stage reached | Primary or secondary, depending on volume |
| Won | Paid customer | Primary for value-based bidding when volume allows; otherwise secondary for reporting |
The criteria for a good stage are simple. It must be used consistently by the sales team, it must happen reasonably soon after the click, and it must happen often enough for bidding to learn from it. A "won" stage that occurs four times a month, months after the click, is a great reporting metric and a weak bidding signal. A "qualified" stage that sales updates within a day or two is often the better primary goal.
Primary vs secondary
In Google Ads, primary conversion actions are included in the Conversions column and used by bidding. Secondary actions are recorded in All conversions for reporting but don't drive bidding, unless they are part of a custom goal. The usual move is to keep the website lead action, add offline stages as separate actions, and then switch which ones are primary once the uploads are proven. Switching the primary goal changes what bidding optimizes toward, so plan the change with the account manager rather than flipping it mid-month.
Set the counting option deliberately. For a lead or qualified-lead stage, "One" (one conversion per click) is usually right. For revenue stages where repeat purchases matter, "Every" fits better. Google's help on conversion counting options explains both.
For Meta, map the same stages to events. Meta's CRM integration for lead ads expects you to send the lead's stages as events from your CRM, so the same ladder works there.
How do you send CRM data to Google Ads?
There are four practical routes. Which one fits depends on the CRM, the volume and how much engineering the client can support.
1. Native CRM integrations
HubSpot, Salesforce and several other CRMs connect to Google Ads directly. HubSpot's ads tool can sync lifecycle stage changes to Google Ads as conversion events. Its documentation notes that only stage changes after the event is created are synced and that native lifecycle stage events use a fixed value rather than the deal amount. Salesforce and HubSpot can also be connected through Google's own Data Manager.
Native integrations are quick to set up and easy for the client to understand. Their limits are flexibility (which stages, which values, which objects) and visibility when they break.
2. Google Ads Data Manager
Data Manager is Google's own place in the Google Ads interface to connect data sources, including CRMs, cloud storage and spreadsheets, for conversion imports. Google's help for the Salesforce and HubSpot connectors says the first successful run imports recent data and later runs import changes since the last run. For Salesforce, separate connections are needed for different objects such as leads and opportunities. This is now the route Google points most advertisers toward for imports.
3. Scheduled file uploads
Where there's no connector, a scheduled export from the CRM to a Google Sheet, an SFTP location or cloud storage, picked up by Google on a schedule, is still available. Google now labels file-based imports a legacy feature and points new setups to Data Manager, so treat this as the fallback rather than the first choice. The format is a simple table. A gclid-based file looks roughly like this:
Parameters:TimeZone=America/New_York
Google Click ID,Conversion Name,Conversion Time,Conversion Value,Conversion Currency
EAIaIQobChMI_example1,Qualified Lead,2026-11-03 14:22:00,150,USD
EAIaIQobChMI_example2,Closed Won,2026-11-04 09:05:00,2400,USD
Column names and accepted time formats are set out in Google's help for file imports, which Google now labels a legacy feature and which points standard uploads to the templates in Data Manager; use the current template there rather than copying headers from an old file. The values above are illustrative.
4. The API
For custom backends and high volume, conversions can be sent programmatically. This changed in 2026: Google announced that offline conversion imports and enhanced conversions for leads uploads move to the Data Manager API, with the Google Ads API no longer accepting new adopters for these uploads from June 15, 2026. Only integrations whose Google Cloud project (or, for older setups, legacy developer token) sent offline conversion uploads between December 17, 2025 and June 15, 2026 stay allowlisted on the Google Ads API while they migrate; new ones get a CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE error. The Data Manager API also does not support retractions: you can restate a conversion's value by re-sending the same transaction ID, but you cannot remove the conversion. If you are building anything new, build it on the Data Manager API and read Google's upgrade guide first.
Enhanced conversions for leads: the gclid-less option
Enhanced conversions for leads works differently. The Google tag captures hashed customer data (usually email, sometimes phone) when the form is submitted. Later, you upload the conversion with the same hashed data, and Google matches it to the signed-in user who clicked the ad. No gclid needs to be stored, which makes it more resilient where click IDs go missing.
Google describes it as the upgraded version of offline conversion import and recommends it for new setups. Some details to plan for: the customer data terms must be accepted, data must be normalized and hashed with SHA-256 if you hash it yourself, and Google asks you to upload all conversions for the stage, not just the ones you think came from Google Ads. If you do have gclids, keep sending them as well, because they make attribution to the specific click more precise. Our enhanced conversions setup guide covers the tag side step by step.
Example
Illustrative scenario. A home services client uses HubSpot. Leads come from Google Search and Meta. We store gclid, gbraid, wbraid and fbclid on every contact, collect email and phone, turn on enhanced conversions for leads on the website lead action, and connect HubSpot through Data Manager. Three conversion actions are created: Lead (website tag), Qualified Lead (from the HubSpot lifecycle stage) and Job Booked (from a deal stage). Qualified Lead becomes primary after two weeks of clean diagnostics; the others stay secondary for reporting. The same stages go to Meta through the Conversions API. The names and stages here are invented to show the pattern.
For a deeper walkthrough of the Google side, including file formats and diagnostics, see our guide to offline conversion import from your CRM.
How do you send CRM events to Meta?
Meta takes offline and CRM events through the Conversions API, sent to the same dataset (Pixel) the ad account uses. There are two common situations.
Leads from Meta lead ads (Instant Forms)
Meta's CRM integration for lead ads is designed for this case. The CRM pulls leads from Instant Forms, keeps Meta's lead ID with each record, and sends stage changes back as events. Meta documents that the lead ID is sent unhashed and that you can fall back to other customer parameters when you don't have it. This integration feeds the Conversion Leads optimization goal. Meta lists eligibility guidance for it, including minimum lead volumes and upload frequency, so check the current requirements before promising it to a client.
Leads from website forms
For leads that came through the website, send the CRM stage as a server event with the best matching data you have: the click ID built from fbclid (sent as fbc), the browser ID (fbp) if you stored it, and hashed email and phone. Use a distinct event name for each stage so Meta doesn't confuse a qualified lead with the original form fill.
A trimmed example of a CRM stage event sent to the Conversions API:
{
"data": [
{
"event_name": "QualifiedLead",
"event_time": 1762272000,
"action_source": "system_generated",
"event_id": "crm-stage-48213-qualified",
"user_data": {
"em": ["<sha256 of normalized email>"],
"ph": ["<sha256 of normalized phone>"],
"fbc": "fb.1.1762000000000.IwAR_example",
"lead_id": 1234567890
},
"custom_data": {
"value": 150,
"currency": "USD",
"event_source": "crm",
"lead_event_source": "HubSpot"
}
}
]
}
The action_source value and the custom_data fields shown here follow Meta's CRM integration guide for lead ads; for website-originated leads, confirm the right action source for your case in Meta's parameter reference. Note the timing rule too: Meta rejects events whose event_time is too far in the past (its documentation sets the limit at seven days before the event is sent, and one event older than that causes the whole request to be rejected), so stage changes need to be sent soon after they happen, not batched monthly.
Several CRMs, including HubSpot, have native Meta Conversions API connections for stage events. They are worth trying first, with the same caveats as the Google side: check which stages they send, what value they attach and how you'll know when they stop.
What values should offline conversions carry?
Values turn offline conversion tracking from "more qualified leads" into "more valuable outcomes." They are also where it's easiest to send misleading data.
- Won deals: use the real deal amount, or gross profit if the client is comfortable sharing it and margins vary a lot between services.
- Earlier stages: use an expected value, such as average deal value multiplied by the share of that stage that historically closes. Agree the numbers with the client and write them down.
- Consistency: use one currency per conversion action and keep the logic stable. Constantly changing values confuse value-based bidding.
Don't move a client to value-based bidding or target ROAS until values are flowing reliably and you trust them. Our guide to assigning conversion values to leads walks through the arithmetic and the conversation with the client.
Why do recent offline conversion reports look low?
This is the most common panic call after go-live, and it's almost always normal.
Google Ads reports conversions against the date of the click by default, not the date of the conversion. A lead clicked on November 1 and qualified on November 12 shows up against November 1, but only after the November 12 upload. So the last few weeks of any report are always incomplete; they fill in as stages change. Add the "Conversions (by conv. time)" column if you want to see conversions on the date they happened. Google explains both views in its help on understanding conversion tracking data.
Several other delays stack on top:
- Sales latency: how long the client's team takes to update stages. This is often the biggest delay and the one tracking can't fix.
- Upload frequency: a daily sync adds up to a day; a weekly manual upload adds up to a week.
- Processing time: Google says to wait several hours after creating a new conversion action before uploading to it, and conversions can take time to appear after upload.
- Windows: Google accepts gclid-based conversions up to 90 days after the click. Stages that take longer than that can't be matched by gclid, which is one more reason to prefer earlier stages as bidding signals.
When clients compare these numbers with the CRM, the gap can look alarming for other reasons too. We cover that in our pillar on ad platform vs CRM reconciliation.
What are the most common upload errors?
Google shows upload results and diagnostics for each offline conversion action, and Meta shows server event diagnostics in Events Manager. Read them weekly for the first month. The errors we see most often fall into a short list:
- Unrecognized or malformed click ID. The gclid was truncated, URL-encoded twice, or copied from the wrong field.
- Click ID from a different account. The gclid belongs to a Google Ads account other than the one receiving the upload, often in MCC setups where conversions are tracked in the manager account.
- Conversion before the click. Usually a time zone problem: the CRM exports UTC and the file declares local time, or the other way round.
- Click too old. The stage happened outside the conversion window or past the 90-day limit.
- Conversion action not found or not ready. The name in the file doesn't exactly match the action, or the action was created hours ago and isn't ready yet.
- Duplicates. The same record uploaded twice, or two integrations sending the same stage. Use an order or transaction ID where the method supports it.
- Low match rates for customer data. Email not normalized (spaces, capitals) before hashing, phone numbers without country codes, or data hashed twice.
Google keeps a help page on fixing discrepancies and errors in offline conversion imports that maps diagnostics to fixes. Error names in the interface change over time, so match what you see to the current page rather than to a list in a blog post.
How do you test offline conversion tracking?
A setup is not done when the connector says "connected." It is done when you can follow a real record from click to stage to platform.
- Create a test lead from a real ad click (or a URL with a test click ID) and confirm click IDs, email and phone land on the CRM record.
- Move the test record through each stage in the CRM, the same way a sales rep would.
- Watch the integration's log or the next scheduled upload and confirm the record was sent with the right stage name, time and value.
- Check Google Ads diagnostics for the conversion action: records received, matched and any errors.
- Check Meta Events Manager for the server event: received, parameters present, and match quality signals.
- Write it down. A test log with record IDs, timestamps and screenshots of diagnostics is the evidence the client (and the next person on the account) will need.
- Remove test records or mark them so they don't pollute reporting.
Diagram
Suggested diagram: a three-column test log template with rows for each stage (Lead, Qualified, Booked, Won) and columns for CRM record ID and timestamp, upload status, and Google Ads / Meta diagnostics result, with pass/fail ticks. Alt text: "Offline conversion test log showing each CRM stage checked in the CRM, the upload and the ad platform diagnostics."
How do you keep offline conversions working?
Offline conversion tracking breaks quietly. Nothing on the website looks different. Bidding just starts learning from less data, and nobody notices until a monthly report looks odd. The usual causes:
- A form is rebuilt and the hidden click ID fields are dropped.
- The CRM admin renames a stage or adds a new pipeline.
- An integration's login expires or a user who authorized it leaves the company.
- Someone adds a second integration that sends the same stages.
- The sales team stops updating stages consistently.
A light monthly routine catches most of this: check that new leads still have click IDs, check upload diagnostics in both platforms, compare stage counts in the CRM with conversions received, and re-run one test lead after any site or CRM change. This is the work our offline conversions service sets up and documents, and if attribution in the CRM itself is the weak point, our CRM lead attribution service starts there.
Guides in this cluster
More guides on offline conversions and CRM attribution are being added to this cluster.
Want us to check one of your client accounts? Get a free tracking check →