A lead arrives through an ad, but the sale closes later in a call or CRM. Unless that outcome is sent back, the ad platform may only know about the lead. Offline conversion tracking connects the later outcome to the acquisition data you were allowed to collect.
This guide uses one simple scenario throughout: a deal that is won through a sales process, not a checkout. It explains why that outcome needs to be measured, what you need to collect up front, how each ad platform accepts it, and how the credit is counted.
The scenario: a deal that closes off the website
Consider an illustrative B2B services journey from a Google or Meta ad to a CRM outcome:
- Day 1: A prospect clicks a Google ad and lands on the website.
- Day 1: They fill in a “Book a consultation” form. Google Ads records a conversion.
- Day 3: A sales rep calls them. The lead becomes qualified in the CRM.
- Day 20: A proposal goes out and an opportunity is created, worth $24,000.
- Day 45: The contract is signed. The deal is marked closed-won.
Steps 3 to 5 happen on the phone, over email, and in the CRM. None of them touch the website, so none of them reach Google. As far as Google is concerned, this campaign produced one form fill, exactly the same as a form fill from someone who never answered the phone.
What is an offline conversion?
An offline conversion is any valuable outcome that happens outside the place where your ad platform can watch. Common examples:
- A deal marked closed-won in a CRM
- A signed contract or accepted proposal
- A sale taken over the phone or in person
- A lead that sales marks as qualified (SQL) or turns into an opportunity
- An appointment that was actually attended, not just booked
“Offline” does not mean the customer was never online. It means the outcome was recorded somewhere your tracking tags do not run. Sending it back to the platform is called an offline conversion import or upload. Offline conversion tracking is the whole loop: capturing the match keys, keeping them on the CRM record, and uploading each outcome.
What changed in 2026
The upload routes moved in the last two years. If your setup was built before 2026, check it against these changes.
- Google Ads imports moved to the Data Manager API. Google says offline conversion imports and enhanced conversions for leads uploads are moving to the Data Manager API (Google Ads Help). From June 15, 2026, developer tokens with no offline conversion upload requests between December 17, 2025 and June 15, 2026 are restricted in the Google Ads API and get a
CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATUREerror. Google’s advice is to migrate those workflows to the Data Manager API (Google Ads API deprecations). Our Google Ads offline conversion import guide covers who has to act and each upload route. - One enhanced conversions setting. Since April 2026, enhanced conversions for web and for leads are combined into a single on/off setting, and existing users were migrated automatically (Google Ads Help). Our enhanced conversions guide covers both setups.
- The legacy Salesforce connector is gone. Google ended support for the legacy Salesforce integration on May 31, 2025 (Google Ads Help). If a Salesforce sync still sits in your account, confirm it is actually sending.
- Meta offline events go to a dataset through the Conversions API. Meta’s old Offline Conversions API stopped supporting offline events from Graph API v17.0 (v17.0 changelog). Offline events sent through the Conversions API must be associated with a dataset (Meta offline events guide).
Why measuring closed deals matters
1. Your ad platforms optimize toward whatever you tell them is a win
Ad platforms can use conversion events as inputs to bidding when the relevant campaign and conversion settings are configured to do so. If the only event being reported is a form fill, that signal does not distinguish a lead that later qualifies from one that does not.
Sending later qualified-lead or closed-deal events can give the platform additional outcome data. Whether those events affect bidding depends on the account’s conversion and campaign settings; review the configuration before treating a reporting signal as an optimization input.
2. Lead counts hide which campaigns actually make money
Two campaigns can produce the same number of leads and very different revenue. Without offline conversions you cannot tell them apart.
1 / 6
If you only report cost per lead, the natural move is to cut Campaign B and scale Campaign A. That is exactly backwards.
3. You can report what leadership actually asks about
Leadership rarely asks “how many leads did we get?” They ask “what did we get for the money?” Offline conversions let you answer with real customer acquisition cost, pipeline created, and revenue by channel and campaign, instead of a lead count that sales may not trust.
4. Long sales cycles stop looking like failures
When deals take weeks or months to close, ad dashboards show spend today and nothing to show for it. Feeding back each pipeline stage (qualified, opportunity, won) gives you earlier signals that a campaign is working, long before the contract is signed.
The catch: you have to capture the link at the lead stage
To match a later CRM outcome to an ad interaction, capture a supported click identifier or another permitted match key when the lead is created. The landing page or form is the practical point to save those values before they are separated from the browser session.

If the form does not capture a supported match key, the CRM may retain only a broad source such as “paid search.” You can still report that context internally, but the platform may not be able to match the later outcome to a specific ad interaction.
What to capture when someone becomes a lead
These are the fields to store on every new lead, usually through hidden form fields or a tracking script that writes them into your CRM.
Click identifiers (the most important part)
Some advertising platforms append a click identifier when the relevant tracking is enabled. Save supported identifiers that are present, and confirm the current platform upload rules before using them:
| Platform | Parameter(s) | What it is |
|---|---|---|
| Google Ads | gclid, gbraid, wbraid | Google’s click IDs. gbraid and wbraid appear on some iOS and app traffic instead of gclid. |
| Meta (Facebook / Instagram) | fbclid, plus the _fbc and _fbp cookies | Meta’s click ID and browser ID, used to match the lead back to an ad. |
| Microsoft Ads | msclkid | Microsoft (Bing) click ID. |
li_fat_id | LinkedIn first-party ad tracking ID. | |
| TikTok | ttclid | TikTok click ID. |
Click IDs arrive in the landing-page URL and are easy to lose before the form. Our default recommendation is to store them in a first-party cookie set from your own tracking domain, such as a server-side Google Tag Manager container on a subdomain of your site. Google recommends serving the server container from the same origin as the website, because server-set cookies need the two to share a domain (Google’s custom domain guide). The server-side tagging guide walks through the setup.
Campaign context
- UTM parameters:
utm_source,utm_medium,utm_campaign,utm_term,utm_content. These power your own reporting even where a platform does not use them. - Landing page: the first page they arrived on, with its full query string.
- Referrer: where they came from, for organic and referral traffic.
Contact details (for matching)
- Email address and phone number. Most platforms can match on these when you are permitted to send them. Each platform has its own normalization, hashing, consent, and upload rules; the table below summarizes them.
Timing and consent
- Lead created timestamp, with time zone. Uploads need an accurate conversion time, and platforms reject events that fall outside their window.
- Consent and permitted use. Record the applicable consent or other permission basis, and follow the platform rules and legal requirements for the data you send.
The thread that ties it together
- A stable lead or contact ID that follows the person into the deal. When the deal closes, you need to look up the original lead and its click IDs. If deals are created as fresh records with no link back to the contact, the chain breaks.
- Deal value and close date on the won record, so the platform learns which leads are worth the most.
How to measure offline conversions
Once the lead fields are in place, measuring offline conversions is a repeatable loop:
- Capture. The form stores click IDs, UTMs, contact details, timestamp, and consent on the new lead.
- Carry. The CRM keeps those fields on the contact and links every deal back to it.
- Define stages. Pick the CRM stages you will send (for example qualified, opportunity, won) and create a matching offline conversion action or goal in each ad platform.
- Close. Sales moves the deal through stages and marks it won with a value.
- Send. A supported integration or upload sends each outcome with the match fields, timestamp, and value required by that platform, inside its upload window.
- Check. Review match rates and upload errors in each platform, and reconcile uploaded revenue against the CRM.
Send useful intermediate outcomes as well as the final win. If your deals often close after a platform’s upload window, an earlier qualified-lead or opportunity event may fit where the close does not.

Offline conversion requirements by platform
Each platform accepts different match keys and has its own upload window. This table lists what the platforms’ own documentation confirms. Where a cell says to check the docs, the rule was not confirmed on a primary source when this guide was updated.
| Platform | Match keys | Hashing | Upload window | Upload route |
|---|---|---|---|---|
| Google Ads Google Ads offline conversion import Enhanced conversions guide | gclid (or gbraid/wbraid), or email and phone for enhanced conversions for leads | SHA-256 after normalizing: lowercase, trimmed email, with dots and plus suffixes removed for Gmail addresses; phone in E.164 format | 90 days after the click for GCLID imports; 63 days for enhanced conversions for leads | Data Manager or the Data Manager API. Google Ads API uploads are restricted for inactive developer tokens since June 15, 2026 |
| Meta Conversions API deduplication | Email, phone, external_id, fbc/fbp, and lead_id for Lead Ads | SHA-256 for email and phone; do not hash fbc, fbp or lead_id | Offline and store events: event_time no more than 7 days before sending. CRM lead stages: check the platform’s current upload documentation | Conversions API, with events associated with a dataset |
| Microsoft Advertising Microsoft Ads offline conversions | msclkid, or email and phone for enhanced conversions | SHA-256 for email; phone in E.164 format | Conversion time within the last 90 days, and inside the goal’s conversion window | Offline conversion goal, then upload in the web interface or the ApplyOfflineConversions API |
SHA-256 email, LinkedIn first-party ad tracking ID (li_fat_id), first and last name, external IDs, or a Lead Gen form response | SHA-256 for email | Conversion time within the past 90 days | Conversions API, directly from Campaign Manager or through a partner | |
| TikTok | Email or phone | Plain text or SHA-256 in the offline events upload; phone in E.164 format | Check the platform’s current upload documentation | Events API, or a CSV upload in Events Manager |
If you run your CRM on GoHighLevel, the GoHighLevel offline conversions guide shows how to send won deals to Google Ads and Meta.
What affects match rates
A match rate is the share of uploaded conversions the platform could connect to an ad interaction. Only matched conversions count toward reporting and bidding. These are the usual reasons it drops:
- Missing click IDs. Auto-tagging is off, a redirect stripped the query string, or the form never saved the value. Without a click ID, the platform has to rely on customer details alone.
- Unnormalized emails and phones. Uppercase letters, stray spaces or a phone number without a country code hash to a different value, so it cannot match. Normalize before hashing, following each platform’s rules.
- Late uploads. Conversions sent after the platform’s window are rejected or not imported. A weekly batch can push the last few days of a window out of reach.
- Consent. If a visitor declined ad measurement, you may not be allowed to store or send their click ID or details. That lowers the match rate, and it should.
- Wrong conversion time or time zone. A close date earlier than the click, or a time in the wrong zone, can make an otherwise valid conversion fail.
- One identifier only. LinkedIn’s documentation recommends sending multiple user identifiers when available to increase match rates. The same logic holds on other platforms that accept more than one key.
Offline conversion attribution: who gets the credit
When you upload a conversion, each ad platform credits it to the ad interaction it matched, using that platform’s own attribution settings and windows. LinkedIn, for example, sets a post-click attribution window on each conversion rule. Google Ads and Microsoft Advertising apply the settings of the conversion action or goal you upload to.
Because each platform only sees its own ads, more than one can claim the same deal. A prospect who clicked a LinkedIn ad and later a Google ad may be counted as a conversion in both. That is why the totals across platforms often add up to more than the deals in your CRM.
A practical split:
- Ad platforms: use uploaded conversions to compare campaigns and to feed bidding inside each platform.
- CRM: use it as the count of record for deals and revenue, with the captured UTMs and click IDs for source reporting across channels.
- GA4 or a warehouse: use it for site behavior and any cross-channel model you build yourself, knowing it will not match the platforms’ numbers.
GA4 and offline conversions
People often ask whether GA4 can track offline conversions. It can record some of them, with limits that matter for long sales cycles:
- Measurement Protocol lets your server send events to GA4, including offline interactions. Google says it is meant to supplement the GA4 tag, not replace it, so it works best when you have stored the identifier the tag created for that visitor (Measurement Protocol overview). Events can only be backdated up to 72 hours (Measurement Protocol reference), so a deal that closes on day 45 is recorded on the day you send it.
- Data import can upload events that were not collected in real time, by CSV or SFTP. Imported data is joined as GA4 collects and processes data; it is not joined with data already processed (GA4 data import).
So GA4 is useful for seeing which site journeys lead to qualified leads, but it is not the route for sending closed deals to ad platforms. Send offline conversions to each platform directly, and report revenue from the CRM.
Which CRM are you on?
The route depends on where the deal lives. A short note for each common CRM:
- GoHighLevel: follow the GoHighLevel offline conversions guide for Google Ads and Meta.
- HubSpot: follow the HubSpot offline conversions guide to send lifecycle stages and closed-won deals to Google Ads and Meta.
- Salesforce: the legacy Google Ads connector ended on May 31, 2025, so plan a current route, such as a supported connector, middleware or your own upload job.
- Pipedrive: store click IDs in custom fields on the person or deal, then send won deals through a connector or a scheduled upload.
- Zoho CRM: the same pattern: custom fields for click IDs, a link from deal to contact, and a connector or scheduled upload for each stage.
Common beginner mistakes
- Saving UTMs but not click IDs. UTMs help your reporting but do not let a platform match a conversion to a click.
- Losing parameters before the form. Redirects, cross-domain booking tools, and embedded forms often strip the query string. Store click IDs in a first-party cookie on landing so they survive navigation.
- Overwriting the first touch. When a returning contact submits another form, a blank or newer value can wipe out the original click ID. Decide which touch you keep and protect it.
- Deals with no link to the lead. Opportunities created by hand without associating the original contact leave nothing to upload.
- No deal value. Uploading “won” without an amount tells the platform every customer is worth the same.
- Duplicate uploads. Sending the same deal twice inflates results. Use a consistent order or deal ID so each outcome is counted once.
- An old upload route. A sync built on the legacy Salesforce connector or an inactive Google Ads API token may have stopped without anyone noticing. Check recent upload history in each platform.
- Ignoring consent. Sending data for people who did not agree to ads measurement creates real compliance risk.
Final takeaways
Offline conversions close the gap between what your ads produce and what your business actually earns. They add later CRM outcomes to advertising reports and give you a basis for comparing lead quality and revenue, subject to each platform’s matching and attribution rules.
They only work if the groundwork is laid at the start of the journey. A click ID captured on the landing page can be carried through the CRM and sent with the later outcome. If it is missing, and no other permitted match key is available, that outcome may not be attributable to the ad account.
Want it done for you? MetricMaven sets up the full offline conversion loop for teams whose best customers close off the website, including:
- Lead capture that stores click IDs, UTMs, consent, and contact details on every form
- CRM field mapping so deals stay linked to the lead that started them
- Stage-by-stage uploads to Google Ads, Meta, and LinkedIn with deal values
- Monitoring for match rates, upload errors, and missing click IDs
To check the website side first, Maven’s tracking audit shows which pixels and events in your GTM container are broken, degraded or stalled.
Every guide in this series
By ad platform
- Google Ads offline conversion import: how to upload CRM conversions through Data Manager
How to get offline and CRM conversions into Google Ads after the June 15, 2026 move to the Data Manager API: who has to act, GCLID import vs enhanced conversions for leads, each upload route step by step, field mapping, checks and common errors.
- Microsoft Ads offline conversions: how to import CRM outcomes into Microsoft Advertising
How to send offline and CRM conversions to Microsoft Advertising (Bing): capture the MSCLKID, create an offline conversion goal, upload by file, schedule or API, add hashed email and phone for enhanced conversions, and fix the common errors.
- ChatGPT Ads offline conversions: how to send CRM, phone and in-store sales to OpenAI
How to get offline outcomes into ChatGPT Ads: what OpenAI’s Conversions API accepts for CRM, phone and in-store events, which stages to send, the 7-day and 30-day clocks, LiveRamp’s invite-only program, and what isn’t documented yet.
By CRM
- GoHighLevel offline conversions: sending won deals to Google Ads and Meta
Google Ads and Meta only see the form fill unless you send outcomes back. Here is how to capture the match keys at lead time, trigger on won deals in GoHighLevel, and send them without double counting.
- HubSpot offline conversions: how to send lifecycle stages and closed-won deals to Google Ads and Meta
How to send HubSpot lifecycle stages and closed-won deals to Google Ads and Meta as offline conversions: HubSpot’s ad conversion events, Google’s Data Manager connection, the Meta Conversions API, click ID capture, which stages to send, and when you need a custom route.
Matching and match keys
- Enhanced conversions in Google Ads: how web and lead setups work
Enhanced conversions add hashed first-party customer data to Google Ads conversions so more of them can be matched to ad clicks. Here is how the web and lead versions differ, how to set them up, and how to check they work.
- Enhanced conversions for leads not working (but offline imports work)
Your GCLID imports land, but enhanced conversions for leads never show. A symptom, cause, check and fix diagnostic built on Google’s own docs: the two diagnostics reports, customer data terms, the tag on your forms, hashing, the API cutoff and consent.
- Meta Conversions API deduplication: how pixel and server events are matched
When the Meta Pixel and the Conversions API both report the same conversion, deduplication decides whether Meta counts it once. Here is how the matching works and how to check it.
Part of: Why your numbers don't match
Also in When the gap is attribution: GA4 multi-touch attribution without BigQuery: what the built-in reports can and can’t do, GA4 multi-touch attribution in BigQuery: build a custom attribution model in SQL, HubSpot multi-touch attribution: native reports vs. a warehouse model
Frequently asked questions
What is offline conversion tracking?
Offline conversion tracking records outcomes that happen after the website visit, such as a qualified lead, a signed contract or a closed-won deal in your CRM, and sends them back to the ad platform that drove the lead. It works by saving a click ID or customer details when the lead arrives, then uploading the later outcome with its time and value.
How do I measure offline conversions?
Capture click IDs, UTMs, contact details, a timestamp and consent on every new lead. Keep those fields on the CRM contact and link every deal to it. Create an offline conversion action or goal in each ad platform, send each stage (qualified, opportunity, won) with its value through a supported upload, then check match rates and reconcile uploaded revenue against the CRM.
How does offline conversion attribution work?
Each ad platform credits an uploaded conversion to the ad interaction it matched, using its own attribution settings and windows. Google Ads, Meta and LinkedIn each claim the deals they can match, so their totals can overlap. Use your CRM as the count of record and the platform figures to compare campaigns within each platform.
Can GA4 track offline conversions?
Partly. The GA4 Measurement Protocol can send server-to-server and offline events, but it supplements the GA4 tag rather than replacing it, and events can only be backdated up to 72 hours. GA4 data import can upload events by CSV or SFTP, but imported data is joined as new data is processed, not added to past reports. For deals that close weeks later, send them to the ad platforms directly and report revenue from the CRM.
What is a GCLID and why does it matter?
A GCLID is a Google click identifier that Google Ads auto-tagging adds to the landing-page URL. When it is captured and kept on the lead record, it lets Google Ads match a later CRM outcome to the click. Google accepts GCLID-based offline imports up to 90 days after the click.
Can I send offline conversions without a click ID?
Often, yes. Google Ads enhanced conversions for leads, Meta, LinkedIn, Microsoft Advertising and TikTok can match on customer details such as email or phone, normalized and usually hashed with SHA-256. Requirements differ by platform, so send a click ID and customer details together when you have consent for both.
How long after the click can I upload a closed deal?
It depends on the platform and identifier. Google Ads accepts GCLID imports up to 90 days after the click and enhanced conversions for leads up to 63 days. Microsoft Advertising and LinkedIn require the conversion time to be within the last 90 days. For Meta and TikTok, check the current upload documentation. If deals close later than that, also send an earlier stage such as qualified lead.
Do I need a CRM to use offline conversions?
You need some system of record that stores the lead, its captured click IDs, and the eventual outcome and value. For most teams that is a CRM such as HubSpot, Salesforce or GoHighLevel, but a well-kept spreadsheet can work while you start.
Sources and references
- Google Ads Help: About offline conversion imports
- Google Ads Help: Guidelines for importing offline conversions
- Google Ads Help: Offline conversion import and enhanced conversions for leads upload windows
- Google Ads Help: Upgrade offline conversion imports (Data Manager API)
- Google Ads API: Deprecations and restrictions
- Google Ads Help: Legacy Salesforce integration
- Google Data Manager API: Format user data
- Meta for Developers: Conversions API for CRM integration
- Meta for Developers: Offline events with the Conversions API
- Meta for Developers: Customer information parameters
- Meta for Developers: Graph API v17.0 changelog
- Microsoft Learn: LinkedIn Conversions API overview
- Microsoft Learn: LinkedIn Conversions API (streaming conversion events)
- Microsoft Advertising API: OfflineConversion data object
- TikTok Ads Help: Upload offline events for Events API
- Google Analytics: Measurement Protocol overview
- Google Analytics: Measurement Protocol reference
- Google Analytics Help: About data import
- Google Tag Manager: Map server-side tagging to a custom domain
