Here is a pattern we see repeatedly. A campaign is running well. Leads are up, cost per lead is down, the monthly report looks excellent. Sales are flat or falling, and nobody can explain the contradiction.
The explanation is usually that the advertising platform is doing exactly what it was told. You defined success as a form submission, so its bidding went and found the people most likely to submit forms. Those are not the same people as the ones most likely to buy, and over a few months the gap widens.
Closing that loop means telling the platform which leads became customers. It is less work than the documentation suggests and it changes what the system optimises towards.
Why the feedback matters more than the reporting
Worth separating two things people conflate.
Connecting your analytics to your CRM is a reporting exercise. It tells you which channel produced revenue. We covered that separately, and it is valuable for deciding where to spend.
Offline conversion import is a training exercise. It sends the outcome back to the platform so its automated bidding can learn what a buyer looks like. The reporting benefit is secondary.
That distinction decides how you prioritise. If you do not use automated bidding, the import is mostly reporting and the simpler route may be enough. If you do, the import is changing the thing that spends your money.
What has to be captured, and when
The platform needs to recognise the lead it sent you. There are two ways to give it that.
The click identifier. When somebody arrives from an ad, the platform appends an identifier to your landing page URL. Capture it on arrival, store it in a cookie, put it in a hidden form field, and save it on the lead record in your CRM. When that lead closes, you send the identifier back with the outcome and the platform matches it.
Hashed contact details. Where no click identifier exists, some platforms will match on an irreversibly hashed email address or phone number. Useful for leads that arrived by phone or through a route that lost the identifier, and it depends on you holding the contact details and having a lawful basis to use them this way.
Capture both where you can. The identifier is more precise and the hashed details cover the gaps.
The same discipline applies as for source capture generally: store it once on arrival, protect it from being overwritten, and confirm it survives the moment a lead becomes an opportunity, which is where custom fields most often disappear.
What you send back
Three things per conversion. Which lead, what happened, and when.
Which lead is the identifier or the hashed details. What happened is a conversion name you define, which does not have to be a closed sale. When is the timestamp of the outcome, and it has to fall within the platform’s matching window, which is why a quarterly upload catches nothing in a long sales cycle.
Then, where the platform supports it, a value. Send the real deal value rather than an average, because the entire point is to let the system distinguish a large customer from a small one.
Use pipeline stages, not just closed deals
The refinement that makes this work in businesses with long cycles.
If your sales cycle is four months, waiting for closed deals means the platform receives feedback four months late, on a small number of events, with the campaign long since changed.
Instead define several conversion events along the pipeline and give each a value reflecting its likelihood of closing. A qualified lead is worth something. A demo attended is worth more. A proposal sent, more again. A closed deal carries the actual revenue.
The platform now receives signal within days rather than months, and the values teach it which leads progress rather than merely which ones arrive. The capability framing for this is in beyond lead volume.
Be honest about volume
The constraint nobody mentions when selling this.
Automated bidding learns from examples. With a handful of conversions a month, there are not enough examples for anything to be learned, and the system will behave erratically rather than intelligently.
If you close five deals a month, offline import will improve your reporting and will not meaningfully train your bidding. That is still worth doing, and you should know which benefit you are getting so you are not disappointed.
Using pipeline stages helps here too, because it multiplies the number of events the system sees.
Phone calls, which is most of India
A large share of Indian enquiries arrive by phone, and those leads frequently carry no identifier at all.
Three routes. Dynamic number insertion, where a different number is shown by source so the number dialled identifies the channel. Hashed contact matching, using the phone number the caller gave you. Or asking on the call and recording it from a fixed list of options.
The third is crude and it works. A field with eight options, filled in on every call, gives you source attribution for the channel that analytics cannot see at all. Free text does not work, because you end up with forty spellings of the same answer.
Doing it without engineering
Most businesses do not need an integration.
Export closed deals from your CRM with the identifier, the conversion name, the timestamp and the value. Upload that file to the platform on a schedule. Weekly is usually frequent enough; monthly is too slow for anything but a long cycle.
If your CRM and the platform are both connected to an automation tool, a scheduled workflow does the same thing without anyone remembering. Either is fine. What is not fine is doing it once, seeing it work, and never doing it again, which is the most common outcome.
Put it in somebody’s calendar with a named owner, the same as every other recurring measurement task.
Privacy, handled properly
You are sending customer data to an advertising platform, which is a processing purpose that needs a basis and should be stated.
Three practical points. Hash contact details before sending, using the method the platform specifies, so you are not transmitting the values themselves. Make sure your notice covers this purpose, because advertising measurement is not implied by a consent given for delivery updates. And exclude anybody who has declined or withdrawn.
Under India’s framework, purposes are specific. Treat this as its own purpose rather than assuming it is covered by a general marketing consent, and check the position with your adviser.
Where it breaks
Five failures account for most broken implementations.
The identifier was never captured. The hidden field was added to three forms and not the fourth.
It was lost at lead conversion. The CRM copies standard fields and not your custom ones. Test the full path with a real lead before trusting anything.
The upload is too late. Outside the matching window, the platform discards it silently.
Timestamps are wrong. A timezone mismatch between your export and the platform’s expectation puts conversions on the wrong day or outside the window.
Duplicate uploads. Uploading the same deals twice inflates conversions and teaches the system the wrong thing. Track what has been sent.
What to watch after you turn it on
Expect reported conversions to fall, because you have replaced form fills with something rarer. That is the intended effect and somebody should be told in advance.
Watch cost per sale rather than cost per lead. Watch the lead-to-customer rate by campaign, which frequently reverses the ranking you had. And give automated bidding several weeks to adjust before judging it, because changing the optimisation target resets what it had learned.
Judge the whole thing on the model in calculating SEO and GEO ROI, and keep in mind the limits set out in full-funnel attribution for B2B. None of this recovers the research that happened inside an assistant, which generated no click to feed back.
A sensible order of work
- Add fields to your CRM for the click identifier and the conversion timestamp.
- Capture the identifier on arrival and put it in every lead form, without exception.
- Test a real lead through to a closed deal and confirm nothing is lost.
- Define your conversion events, including pipeline stages, with values.
- Confirm your consent basis covers this purpose.
- Export and upload weekly, with a named owner.
- Add hashed contact matching for phone leads with no identifier.
- Switch bidding to optimise on the new events and leave it alone for several weeks.
If you want this set up on your own CRM and ad accounts, get in touch.