Insight · MeasurementMOFU
Feed your sales data back to Google and Meta
The short answer
If your campaigns optimise for form fills, Google and Meta will find you more people who fill in forms — including the ones who never answer the phone. To find more customers, the platforms need to know which leads became customers. That's what offline conversions do: they send outcomes from your CRM back to the ad platforms.
Why form-fill optimisation goes wrong
Automated bidding learns from the conversions you report. If every form fill counts the same, the system can't tell a serious buyer from a student filling in forms for fun, or a competitor checking prices. It often drifts towards the cheapest form fills, and cost per lead falls while sales fall too. Our piece on real estate lead quality shows how this plays out.
How it works on Google
Google offers two main routes (Google Ads Help):
- Offline conversion imports — your form captures the Google click ID (gclid); when the lead qualifies or buys, you upload that click ID with the conversion name, time and value. Google supports conversions within the conversion window you set.
- Enhanced conversions for leads — instead of click IDs, the Google tag captures hashed email or phone at the form, and you later upload the outcome with the same hashed details (Google Ads Help). This is often easier to maintain.
How it works on Meta
Meta's Conversions API lets you send events from your server or CRM directly to Meta, including lead-stage events such as "qualified lead" or "purchase" (Meta Business Help Centre). Matching uses identifiers such as hashed email and phone, and Meta shows an event match quality score to tell you how well events are matched. When you also send the same events from the pixel, use an event ID so Meta can deduplicate.
Choose the stages to send
| Stage | Example definition | Why send it |
|---|---|---|
| Lead | Form submitted or call answered | Volume signal for learning |
| Qualified lead | Budget, timeline and need confirmed by sales | Teaches the platform what a good lead looks like |
| Opportunity or visit | Site visit, demo or consultation booked | Closer to revenue, still frequent enough |
| Sale | Deal won, with value | The real goal; often too rare to optimise on alone |
Most accounts optimise on the deepest stage that still happens often enough to learn from — frequently "qualified lead" or "visit" — and report on sales. Agreeing the definitions with the sales team matters as much as the tech; see lead scoring and SQL.
Setting it up
- Capture identifiers at the form. Store gclid, fbclid and UTM values in hidden fields, along with email and phone (with consent).
- Keep them in the CRM against each lead, so they survive until the outcome is known.
- Define the stages and the values for each, with sales.
- Connect the CRM to Google Ads and Meta — by native integration, a connector or scheduled uploads.
- Upload regularly — daily is ideal, weekly is the minimum — and monitor match rates.
- Switch optimisation to the qualified stage once enough volume is flowing, and watch cost per sale.
Privacy and consent
Offline conversions use personal data, so they sit squarely within India's DPDP framework. Tell people in your notice that you use their details to measure and improve advertising, collect consent, hash identifiers before sending, send only what's needed and remove people who withdraw consent. See the DPDP Rules for marketers.
Mistakes to avoid
- Forms that drop click IDs or UTMs on the way to the CRM
- Uploading only won deals, so there's too little data to learn from
- No agreed definition of a qualified lead
- Duplicate events from pixel and server without deduplication
- Switching bidding before enough qualified conversions are flowing
A worked example (illustrative)
A Mumbai real-estate developer runs Google Search and Meta lead campaigns. Before the change, both optimise for form fills; cost per lead looks good, but the sales team says few leads pick up. The developer adds hidden gclid and fbclid fields to the forms, records them in the CRM, and sends two events back: "qualified" (budget and timeline confirmed on the first call) and "site visit". After a few weeks of uploads, campaigns are switched to optimise for qualified leads. Cost per raw lead rises, but cost per site visit falls because the platforms now look for people who resemble those who visited. The exact numbers will differ by project; the pattern is common.
Choosing values for each stage
Assigning values helps value-based bidding. A simple approach: start from the value of a sale (gross margin, not revenue, if you can), multiply by the historical probability that each stage leads to a sale, and use that as the stage value. If 1 in 20 qualified leads becomes a sale worth ₹2 lakh in margin, a qualified lead is worth about ₹10,000 for bidding purposes. Revisit the values every quarter as conversion rates change.
Monitoring after launch
- Upload success and match rates in Google Ads and Events Manager
- Meta event match quality for server events
- Counts in the platforms versus counts in the CRM, by week
- Time between lead and upload — shorter is better
- Cost per qualified lead and per sale, alongside cost per lead
Frequently asked questions
Do we need a CRM for offline conversions?
You need somewhere that records each lead's outcome with its identifiers — usually a CRM, sometimes a well-kept spreadsheet that's uploaded on a schedule.
What's the difference between offline conversion imports and enhanced conversions for leads?
Offline imports match on Google's click ID; enhanced conversions for leads match on hashed contact details captured at the form. Many accounts use enhanced conversions for leads because it's simpler to maintain.
How quickly should we upload conversions?
As often as practical — daily if possible. Delayed uploads slow learning, and very old conversions may fall outside the conversion window.
Will this lower our cost per lead?
Often cost per raw lead rises while cost per qualified lead and per sale falls. That's the point.
Can we do this for phone-call leads?
Yes. Call-tracking tools can capture identifiers and pass outcomes back, and calls can be imported as conversions once qualified. Our marketing analytics team sets this up.
Can we import conversions from WhatsApp leads?
Yes, if the WhatsApp conversation is linked to an ad click or the lead's contact details are captured, and the outcome is recorded in your CRM. Click-to-WhatsApp campaigns can be connected this way.
What is event match quality?
A Meta score showing how well the customer information sent with server events matches Meta accounts. Better matching means more of your conversions are attributed and used for optimisation.
Keep reading
Services behind this
Terms used on this page
Free growth audit
Find out where your budget is leaking.
Send us your ad account, analytics or site. Within 72 hours you get a written audit: tracking gaps, wasted spend, and the three moves we'd make first. No pitch deck.