Start free
Kunads / Answers / How do I track offline conversions from my ads?

How do I track offline conversions from my ads?

Updated 2026-11-19 · Editorial policy

Track offline conversions in three steps: save the ad's click ID (or Meta's lead ID) with each lead, mark the lead as qualified or won in your CRM, and send that event back, to Google through Data Manager and to Meta through the Conversions API or a CSV upload. Then optimise for the deals, not the form fills.

Which identifiers do I need to save on each lead?

Save the platform's own click or lead identifier plus the person's email and phone, because those are what Google and Meta match an offline sale against. Without them the sale can still go into a report, but the platform cannot tie it to an ad or learn from it.

Then mark what happened in the CRM

Pick one or two events that matter: "qualified lead" and "won deal" are common. Record the date and the value. Use the profit or deal value you want bidding to chase. A won deal with a real value is far more useful to the platforms than a lead with a guessed one.

How do I send offline conversions to Google Ads?

Through Data Manager: in the Google Ads interface without code, or through the Data Manager API for a developer-built integration.

Sending them to Meta

Example one: a solar installer

A solar installer gets 400 leads a month from Google and Meta. 60 become site visits, 20 sign. Each signed job keeps about €2,500.

With only 20 won deals a month, that event alone is thin for bidding. Optimise on "qualified" (60 a month) and report on "won".

Five steps from a form fill to an offline conversion: save the click ID, mark 60 qualified and 20 won deals, attach €2,500 per job, send to Google and Meta, bid on qualified.

Example two: a long sales cycle

A B2B software firm gets 120 demo requests a month, signs 6, and each contract is worth €9,000. A lead is worth €9,000 × 6 ÷ 120 = €450. The catch is timing: the average deal closes 75 days after the first click. Google's help on conversion measurement notes that click IDs must be within 90 days for an offline import, and each conversion action has its own click-through window, so set that window long enough or the slowest deals are rejected. Deals that close later than any window allows can only be reported, not imported.

Six deals a month is far too few for either platform to learn from. Send an earlier event as well, such as "demo held", and give it a value based on what share of held demos sign. That is a judgement call you should write down and revisit each quarter as real close rates come in.

Shops, tills and missing identifiers

Retail shops with a till use the same route with store sales and customer information instead of click IDs; match rates are lower. If you cannot capture any identifier, offline data can still go in reports through a CRM export, but the platforms cannot learn from it. Full detail is in how to send CRM conversions to Meta and Google and the Data Manager API guide.

Kunads takes won deals from any CRM through a Sheet, CSV, API or webhook and can send won-deal value back to Meta (Conversions API) and Google (Data Manager API) as a separate conversion, opt-in per account. CRM pipeline stages and lead-form connectors are not built yet.

Breakeven, per campaign. Give Kunads your margin once; it marks which Meta and Google campaigns sit below it and by how many euros.

Find my losing campaigns Try it for 14 days