Topics: Meta & Google ads
Want this done for your business? Get a fixed quote or book a free 30-minute call.
Quick answer: Offline conversion tracking reports what happened after an enquiry (qualified, booked, sold) from your CRM back to the ad platforms. On Google, use enhanced conversions for leads or a click ID (GCLID) import; on Meta, use the Conversions API for CRM with lead IDs and stage updates. Both platforms then optimise towards people who resemble your customers rather than whoever fills in forms most readily.
Google Ads and Meta are very good at finding more of whatever you call a success. Call a form submission a success and they'll find you form submissions, including the student practising on forms, the competitor checking your prices and the person who typed a fake number. Offline conversion tracking changes what they're rewarded for. This guide covers both platforms, which stages to send, what to prepare and how to stay on the right side of privacy law.
What is offline conversion tracking and why does it reduce junk leads?
It's the loop that tells an ad platform which of its leads turned into real opportunities, so it can find more people like them. Website tracking stops at the form; offline tracking picks up where your sales process begins.
The loop works like this:
- Someone clicks an ad and enquires. Their click ID or lead ID is stored with the enquiry.
- Your team qualifies, books or sells, and the CRM records the stage and date.
- A connector uploads those stage changes to Google Ads or Meta.
- The platform matches each upload to the original click or lead.
- Bidding and delivery shift towards the patterns behind leads that progressed.
The result isn't instant, and it doesn't fix a weak offer. But it's the most direct way to stop paying for junk leads without shrinking your volume to nothing.
How do enhanced conversions for leads and GCLID imports differ?
Enhanced conversions for leads matches on hashed contact details captured at the form; GCLID import matches on a click ID you store yourself. Google recommends enhanced conversions for leads for new set-ups, while GCLID import still works and remains common.
| Enhanced conversions for leads | GCLID import | |
|---|---|---|
| Identifier | Hashed email or phone captured by the Google tag on your form | The gclid value from the landing page URL |
| What you store | Email and phone in your CRM, which you already have | GCLID in a hidden form field saved to the lead record |
| Common failure | Forms where the tag can't read the email or phone fields | Redirects, page builders or forms that drop the URL parameter |
| Upload route | Data Manager, a CRM integration or a scheduled file | The same, keyed on GCLID and conversion time |
| Best for | New set-ups and businesses that collect email or phone | Existing set-ups already storing click IDs reliably |
Either way, create separate conversion actions for each stage. Google Ads has goal categories for qualified and converted leads, which helps keep CRM stages distinct from the original form fill. Clicks must fall inside the conversion action's window, which can't exceed 90 days, so long sales cycles need the earlier stages. Our Google Ads conversion tracking setup guide covers the form-level tag this builds on.
How does Meta's Conversions API for CRM use your sales stages?
It links each instant-form lead's ID to the stages it reaches in your CRM, and Meta then optimises delivery for "conversion leads" rather than raw leads. It's built for Meta's native lead ads.
Per Meta's developer documentation:
- Every instant-form lead has a numeric lead ID, 15–17 digits long, available from the lead webhook or export. Store it on the CRM record.
- Send an event for every stage change, starting with the first, with the lead ID, the stage name and a timestamp after the lead was created.
- Meta's fit criteria include uploading at least daily, a target stage reached within 28 days of the lead, and a stage conversion rate roughly between 1% and 40%.
One practical catch: keep the stage names you send stable. If your sales team renames "Qualified" to "Hot" halfway through a quarter, Meta sees a new stage with no history. Agree the names once, map your CRM statuses onto them in the connector, and relabel things internally as often as you like.
For leads that come through your website instead, the standard Meta Conversions API carries the stage events, matched on hashed contact details and browser identifiers rather than a lead ID.
Which stages should you send back: qualified, booked or sold?
Send all of them, but optimise for the deepest stage that still has enough weekly volume. Usually that's "qualified" at first.
| Stage | Typical volume | Signal quality | When to optimise for it |
|---|---|---|---|
| Lead received | High | Weak | Never on its own once stages are flowing |
| Qualified | Medium | Good | Most businesses, from the start |
| Booked or met | Lower | Strong | When bookings are steady each week |
| Won | Lowest | Strongest | With values, once volume supports it |
Define "qualified" in writing before anything goes live: in budget, in your service area, wants a service you offer, reachable. If each salesperson applies their own definition, the platforms learn noise. Be wary, too, of a stage that only one busy person can set: a "won" status the owner updates once a month teaches the platforms less than a slightly shallower stage updated every day. Once won deals are regular, send them with a value so Google's value-based bidding can separate a small job from a large contract.
What do you need in your CRM or spreadsheet before you start?
Identifiers, clean contact data, dated stages and a reliable way to upload. A spreadsheet can work at low volume; a CRM makes it sustainable.
- Click and lead IDs: GCLID (plus gbraid or wbraid where present) for Google; lead ID for Meta instant forms; the fbc cookie value for Meta website leads
- Contact data: email and phone in consistent formats, with phones in international format such as +61 or +91
- Stage fields: the stage name and the date and time each stage was reached, with a time zone
- Values: a quote or deal value where you have one
- A connector: a native CRM integration, an automation tool such as Zapier, or a scheduled script
- An owner: someone who checks upload diagnostics weekly and fixes rejected rows
Phone enquiries need the same treatment. If calls matter to you, our guide to call tracking for Google Ads shows how to tag and upload call outcomes too.
How long before the platforms optimise for better leads?
Expect around a month of set-up and validation, and another few weeks before results move. Meta's documentation suggests integration can take several weeks, and onboarding to fully optimised conversion-leads campaigns roughly three to four weeks after that.
A realistic rhythm:
- Weeks 1–2: capture IDs on every lead and confirm uploads match in each platform's diagnostics.
- Weeks 2–4: send stages as secondary or observation-only conversions and compare them with your CRM.
- Week 4 onwards: make the qualified stage the primary goal in Google, and switch Meta ad sets to conversion-leads optimisation.
- Months 2–3: judge success on cost per qualified lead and cost per sale, not cost per form fill.
Uploading late or irregularly slows all of this. Daily uploads beat a monthly batch.
How do you handle privacy and consent when sending customer data?
Hash identifiers, tell people in your privacy notice, collect consent where the law requires it and never upload sensitive details. Both platforms accept SHA-256 hashed email and phone, and most integrations hash before sending.
- Notice: say that you share contact details with advertising platforms to measure and improve ads.
- Consent: India's DPDP Act is built on notice and consent; in Australia, APP entities must handle personal information within the Australian Privacy Principles. Our guide to India's DPDP Act and Australia's Privacy Act covers both.
- Sensitive data: stage names travel with the data, so "IVF consultation booked" reveals health information. Use neutral names such as "stage 2".
- Access: limit who can export lead data, and remove old upload files once they've been processed.
This is general guidance, not legal advice; take advice if you handle health, financial or children's data.
Frequently asked questions
What is an offline conversion in Google Ads?
It's a conversion that happens away from your website, such as a qualified lead, a booked appointment or a signed contract, uploaded to Google Ads afterwards. Google matches it to the original click using a GCLID or hashed contact details.
Do I need a CRM to send offline conversions?
Not at the start. A disciplined spreadsheet with click IDs, contact details and stage dates can feed scheduled uploads. As volume grows, a CRM with a native integration is far more reliable.
Can Meta optimise for leads that became customers?
Yes. With the Conversions API for CRM, Meta receives stage updates for each instant-form lead and can optimise delivery for conversion leads, meaning people likely to reach your chosen stage. It needs daily uploads and a stage that occurs within 28 days.
How many offline conversions do I need for it to work?
Neither platform gives one universal minimum, so aim for a stage that happens every week, not occasionally. Meta's guidance looks for a stage conversion rate between about 1% and 40% of leads; a stage rarer than that gives too little signal.
Is it legal to upload customer emails and phone numbers to ad platforms?
It can be, when you hash the data, explain the sharing in your privacy notice and collect consent where the law requires it. Requirements differ between India, Australia, the UK and the USA, so check the rules for each market you advertise in.
Ready to teach your ads what a customer looks like?
We build lead generation with CRM feedback as standard: click IDs captured, stages defined with your team and uploads checked every week. Book a free call and we'll map which stages your sales process can send back.