Key takeaways
- An offline conversion API reports sales that close off-site, by phone, in store, or in a CRM, back to the ad platform that started them.
- Google Ads and Meta both provide one: Google through the Data Manager API, Meta as the Offline Conversions API.
- The most accurate match uses a click identifier captured at the enquiry, such as GCLID for Google, stored and returned with the sale.
- Where no click ID exists, platforms match on hashed identifiers like email and phone instead.
- Sending offline outcomes lets automated bidding optimise for revenue, not just for form-fills or calls.
- The loop only helps if the linking identifier was captured at enquiry; if it was never stored, the sale cannot be matched later.
- A leading pizza QSR chain improved purchase ROAS by 38.5% using the Meta Offline Conversions API through Datahash.
What is an offline conversion API?
An offline conversion API is a programmatic way to tell an ad platform that a conversion happened somewhere it could not see. Most ad measurement watches the website: a purchase fires a pixel or a tag. But many businesses close the sale elsewhere. A car dealer takes a deposit over the phone, a B2B lead signs weeks later, a shopper buys in store after seeing an ad. The offline conversion API carries those outcomes back. Google Ads Help documents this as Data Manager API, and Meta for Developers documents it as the Offline Conversions API, part of the same Conversions API family. Both do the same job: connect a real sale to the ad that influenced it.
How does an offline conversion API work?
An offline conversion API works by matching a stored identifier to a completed sale and sending that pairing back to the platform. The mechanism runs in order:
- At enquiry, you capture a linking identifier: the click ID from the ad, or the customer’s email and phone.
- You store that identifier against the lead in your CRM or point of sale.
- When the sale closes, you attach the outcome and its value to the stored identifier.
- You send the identifier, the conversion, and the value to the platform through its offline conversion API, hashing any personal identifiers first.
- The platform matches the identifier to the original click and attributes the conversion.
Google Ads Help notes that a match built on a stored click identifier is the most accurate route, because it ties the sale to a specific ad interaction rather than inferring it from contact details.
How does the Google Ads Data Manager API work for offline conversions?
Google Ads is moving its offline conversion workflows to the Data Manager API. It relies on the GCLID, the Google Click Identifier, which Google appends to the landing page URL when someone clicks an ad. You capture that GCLID on the lead form, store it with the lead, and when the deal closes you send the GCLID with the conversion name, value, and time through the Data Manager API. Google matches the GCLID to the original click and credits the campaign. Where no GCLID exists, enhanced conversions for leads lets Google match on hashed contact details instead. The Google Ads Developer documentation covers both paths.
How does offline conversion tracking work across platforms?
Offline conversion tracking works the same in principle on every platform, and differs only in the identifier each one matches on. In practice you set up each destination separately. Datahash documents sending offline conversions to Google Ads, sending offline conversions to Meta, and the TikTok offline events API, each covering one destination in the same loop. The comparison below shows what each matches on:
| Platform | Primary match key | Fallback |
|---|---|---|
| Google Ads | GCLID stored at the click | Hashed email and phone via enhanced conversions for leads |
| Meta | Hashed email and phone | Other identifiers you hold on the record |
| TikTok | Hashed identifiers with event data | Event ID for deduplication |
How do you set up an offline conversion API?
Setting up an offline conversion API is a five-step process that starts before any sale closes, because the linking identifier has to be captured up front. Run the steps in order:
- Decide the match key: a click identifier where you can capture it, or hashed email and phone otherwise.
- Capture that identifier at the point of enquiry and store it against the lead.
- Define the offline conversions that matter, such as qualified, sold, and the deal value.
- Connect your CRM or point of sale to each platform’s offline conversion API, hashing identifiers before send.
- Check match rates, and improve identifier coverage where they come in low.
For a batch process, Datahash documents preparing a CSV of offline conversions so the historical sales upload matches the same schema as the live feed.
What are the use cases for an offline conversion API?
An offline conversion API earns its place wherever the sale closes away from the website, which is most of the economy outside pure e-commerce. The use cases below are the common ones:
- Automotive and high-value retail, where an online enquiry becomes a phone call and a deposit taken in the showroom.
- B2B and considered services, where a lead form turns into a deal that closes weeks later in the CRM.
- Bricks-and-mortar retail, where a shopper sees an ad online and buys in store, matched through store sales.
- Contact-centre and appointment businesses, where the conversion is a booked and attended visit, not a web checkout.
- Subscriptions billed offline, where the charge clears in a billing system rather than on the site.
In every case the pattern is the same: the ad drove an enquiry the platform could see, and the sale happened somewhere it could not. The offline conversion API is what connects the two, so the campaign is measured on revenue rather than on form-fills.
What are the benefits of offline conversion tracking?
The benefits of offline conversion tracking all follow from giving the platform a truer picture of what your ads produce. When the real sale is reported back, automated bidding stops optimising for cheap leads and starts optimising for revenue, so the budget flows toward the audiences that actually buy rather than the ones that merely enquire. Attribution becomes honest: a campaign that looked weak on form-fills can turn out to be your best source of closed deals once the offline outcomes are counted. Reporting reconciles with the business, because the numbers the platform shows now line up with the sales your finance team records. And the audiences the platform builds, lookalikes and retargeting pools, are seeded from real customers rather than form submitters, which makes them sharper. None of this is visible without the loop; offline conversion tracking is what makes the invisible half of the funnel countable.
How do you track offline conversions in GA4?
You track offline conversions in GA4 by importing them through the Measurement Protocol or a data import that ties the offline event to the original session or user. The offline sale is sent to GA4 with the identifiers that link it back to the online visit, so the analytics view reflects the full journey rather than stopping at the last web action. GA4 is the measurement layer; the ad platforms are separate destinations, which is why an offline sale usually needs to be sent to Google Ads, Meta, and GA4 each in the format that system expects. A single connector that fans one offline event out to all of them keeps the schema consistent and the numbers reconciled across reporting and bidding.
What are the limits of an offline conversion API?
An offline conversion API cannot recover a link you never captured. If the click identifier or contact detail was not stored at enquiry, there is nothing to match the sale against later, and the conversion stays invisible. Match rates are never one hundred percent, because some customers use different details online and offline. The loop also only helps if you keep it running: a single upload improves one report, but only a regular feed changes how the platform bids. And it reports revenue; it does not create it. An offline conversion API connects signal you already hold. It does not replace a CRM that fails to capture the basics.
What Datahash does about this
Datahash runs offline conversion APIs across Google, Meta, TikTok, and Snap from one first-party data layer. It takes the closed sale from your CRM or point of sale, hashes the identifiers, and sends the outcome to each platform in the format that platform expects, so you are not building a separate offline pipeline per destination. The hashing happens before anything leaves your systems, keeping the flow consistent with GDPR and DPDP. A leading pizza QSR chain improved its purchase ROAS by 38.5% with the Meta Offline Conversions API, and Raymond recorded a 3.2x increase in overall ROAS on the same connection, because bidding could finally optimise for sales that closed away from the site. You can also send offline conversions to Meta from HubSpot directly, and match rates are visible per connection so the recovery is measured, not assumed.