Offline conversion tracking from your CRM: tell Google Ads which leads actually bought
In short
- Offline conversion tracking sends sales that close by phone or WhatsApp back to Google Ads, so bidding learns from real customers.
- Google calls the Data Manager API the primary route for offline conversions, and the Google Ads API no longer accepts new uploaders.
- Your CRM should store the gclid, email or phone, lead ID, timestamp with time zone, deal stage and deal value.
- Send a few meaningful stages, such as qualified and won, rather than every small step in your pipeline.
- Check the per-record error reports weekly, because a rejected record is a sale Google Ads never learns about.
Offline conversion tracking sends the sales that happen away from your website back to Google Ads, so it can learn which clicks became paying customers. Google has recently made the Data Manager API the main route for these uploads, and that connection now also handles phone call conversions and shows exactly which records were rejected. If your business closes deals on the phone or on WhatsApp rather than at a checkout, this tracking starts in your CRM.
What is offline conversion tracking?
Offline conversion tracking tells Google Ads what happened after the click, once the lead left your website. Without it, Google Ads only sees the form fill or the tap on the call button, and treats every lead as equally valuable.
When someone clicks your ad, Google adds a click ID, called the gclid, to the page address. Your form captures it and your CRM stores it with the lead. When that lead becomes a customer, the CRM reports back: this click became a won deal, worth this much, at this time. Google connects the sale to the campaign and keyword that started it.
Picture a private clinic running two campaigns. One brings many enquiries, mostly people asking about price. The other brings fewer, but more of them book treatments. If Google only sees form fills, it may push budget toward the first. With offline data, it can learn the difference.
What changed in how Google receives offline conversions?
Google now treats the Data Manager API as the main door for offline sales data. The Google Ads API no longer accepts new users for uploading offline conversions, including enhanced conversions for leads. Google calls the Data Manager API “the primary API for importing offline conversions.” Existing users can keep going while they move over.
Inactive old setups can fail. Uploads fail with the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when the Google Cloud project, or a legacy developer token, sent no offline conversion uploads in the period before the change. Legacy developer tokens have also been switched off.
Phone calls are included. The Data Manager API can now send call conversions to Google Ads, using a new call_info field on each event. Call conversions track when ads lead to calls and when those calls lead to valuable customer actions.
Errors are traceable. Each error count and warning count in a request’s diagnostics now includes a record_indices field, so you can see which records had problems.
Leads can be matched by your own ID. The lead_id and match_id fields can identify offline events sent to Google Ads, Floodlight and Google Analytics.
Setup got simpler. Google merged enhanced conversions for web and for leads into one on/off setting, and recommends the Data Manager screen inside Google Ads or direct CRM connections, neither of which needs code. If you upload by CSV file, through Data Manager connections, or only with the Google tag, you don’t need to rebuild anything.
The businesses that need to act are mainly those with a custom script that uploads sales through the Google Ads API.
Why is your CRM the only place that knows who paid?
Your ad account knows about clicks, your website knows about forms, and your phone knows about calls. Only the CRM sees the whole journey, from first enquiry to signed deal.
Take a real estate office. A lead clicks an ad, fills in a form, gets a call, visits two apartments and signs months later. None of that exists in Google Ads unless your CRM reports it. The same goes for a renovation company that quotes on WhatsApp.
This matters most for businesses that close most sales by phone or WhatsApp, which is common in Israel and many other markets. If your lead management already runs through one CRM, the missing piece is sending the outcome back.
What should your CRM save on every lead?
Your CRM should store six things on every lead, captured automatically wherever possible:
- Google click ID (gclid): taken from the page address into a hidden form field.
- Email address or phone number: enhanced conversions for leads can match a deal to an ad without a gclid, using a hashed email or phone.
- Lead ID: your own unique ID, which can travel in the lead_id field.
- Exact time with time zone: so nothing shifts by hours between systems.
- Deal stage: where the lead stands in your pipeline.
- Deal value: what the sale is worth, in your currency.
Hashing turns the email or phone into a code before it is sent, so contact details are not uploaded as plain text. Save phone numbers in one format with the country code, so a WhatsApp lead and a form lead from the same person look identical.
Our own team works from Tel Aviv, Lisbon, Bangkok and Tokyo, and we have learned that a timestamp without a time zone is an argument waiting to happen. Save it once, correctly, at the source.
Which deal stages should you send to Google Ads?
Send a few stages that clearly signal value, such as “qualified” and “won”. The first gives Google enough signals to learn quickly. The second tells it the truth about money.
A B2B service company might mark a lead qualified after a discovery call confirms budget and need, and won when the contract is signed. A beauty salon might treat a booked first appointment as qualified and the first paid visit as won.
Write a clear rule for each stage inside the CRM, so “qualified” means the same thing for every salesperson. Inconsistent stages teach Google inconsistent lessons.
How to set up offline conversion tracking from your CRM
Setting up offline conversion tracking is a short sequence of decisions. Most of the work is keeping the CRM data clean.
- Create a conversion action in Google Ads for each stage you plan to send.
- Capture the gclid on every form and landing page, and confirm it lands in the CRM.
- Turn on the enhanced conversions setting, so email and phone can be used when the gclid is missing.
- Choose your route: the Data Manager screen, a direct CRM connection, a CSV upload, or the Data Manager API for a custom CRM.
- Send stage changes automatically with the lead ID, time, value and identifiers.
- Let data build up before changing bidding, then decide whether to optimize toward the new actions.
If you are new to measurement, our conversion tracking guide covers the website side first.
How do you know if an old script still uses the old upload route?
Ask whoever built it a few direct questions. Many businesses had a developer or past agency set this up long ago, and nobody has checked it since.
- Does our integration upload through the Google Ads API or the Data Manager API?
- Whose Google Cloud project and developer token does it run under?
- When was the last successful upload?
- Have we seen the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE?
If a former agency built the script under its own project or a legacy token, it may have stopped quietly. A simple sign: your offline conversion columns in Google Ads went flat while sales continued.
How to read the new error reports every week
The new diagnostics show which records failed, so a weekly check becomes a short fix list. Each error and warning count comes with record_indices, the positions of the problem records in the upload.
Open the latest upload results and look at the counts. Use the record positions to find the affected leads in your CRM by lead ID. Fix the cause, such as a missing value, a broken time format or a phone number without a country code, and send the corrected records again.
A custom CRM can save the upload status on each lead, so the check is a filtered list instead of detective work. Every rejected record is a real sale Google Ads never learned about.
Real sales make better ads
Google Ads gets smarter when it learns from customers who paid, not from people who filled in a form. Google’s changes are a good moment to check your setup: one main route, phone calls included, clear reports on what failed. At Kaede Digital we build custom CRM systems that capture this data from forms, WhatsApp and calls, and send it back automatically. It pairs well with a clear Google Ads plan for small businesses.
FAQ
Do I need a gclid for offline conversion tracking?
Not always. Enhanced conversions for leads can match a CRM deal to an ad using a hashed email address or phone number. Saving both the gclid and contact details on every lead gives Google the best chance to match.
Do I have to rebuild my setup because of the Data Manager API change?
If you upload by CSV file, through Data Manager connections, or only with the Google tag, you don’t need to rebuild anything. If a custom script uploads through the Google Ads API, ask your developer which route it uses and whether it still works.
Can I report sales that closed on WhatsApp or by phone?
Yes. A deal closed in a conversation can be sent as an offline conversion, matched by gclid or by email and phone. The Data Manager API now also supports call conversions, which track when ads lead to calls and when those calls lead to valuable actions.
Which value should I send with a won deal?
Send the real deal value from your CRM, in your currency. For earlier stages such as qualified, keep the value consistent so Google compares like with like. Accurate values help Google tell a big customer from a small one.
Custom CRM










