How to Send CRM Data to Google Ads: Offline Conversion Upload Guide
Your CRM knows when deals close. Google Ads doesn't. Here is how to bridge that gap and get your CRM revenue data into Google Ads automatically.
Key Takeaways
Google Ads can receive offline conversion data from any CRM via the UploadClickConversions API.
The data needed: a GCLID (captured when the contact first clicked your ad) plus a conversion event and value.
Most CRMs can fire webhooks when deals close — this is the trigger point for the upload.
The GCLID must be captured and stored against the contact email before the deal closes.
No developer is required if you use a tool that handles GCLID capture, matching, and upload.
Gap 1: CRM doesn't know about ad clicks
Your CRM stores contacts and deals. It doesn't know which Google ad each contact clicked. That click data lives in Google Ads. Bridging the two requires storing the GCLID at contact creation time.
Gap 2: No trigger for 'deal closed' upload
Even if your CRM has the GCLID, there's no automatic mechanism to send it to Google Ads when a deal closes. Someone has to do it manually — or a custom integration has to be built.
Gap 3: Upload format is strict
Google Ads' UploadClickConversions API requires: a valid GCLID, a conversion action name matching exactly, a UTC timestamp in the right format, and an optional value in the right currency code. One mistake and the upload fails silently.
Gap 4: No visibility into failures
Manual CSV uploads and custom integrations often fail silently. Conversions are accepted but discarded. You find out weeks later when you audit campaign performance and nothing adds up.
Manual upload vs. ConversionLoop
Why the manual process breaks at scale — and what changes with automation
How to do it manually (and why it breaks)
Manual CRM-to-Google Ads sync requires exporting contacts with GCLIDs from your CRM, filtering by closed date, formatting as a CSV, and uploading in Google Ads. At low volume this works. At scale it is unreliable — the GCLID export misses contacts without it, formatting breaks, and the 90-day window gets missed.
The automated approach
ConversionLoop acts as the bridge. Your CRM fires a webhook when a deal closes. ConversionLoop receives it, looks up the GCLID for that contact's email, formats the conversion, and uploads to Google Ads via API. Runs in under 60 seconds.
ConversionLoop handles GCLID capture, upload formatting, and delivery automatically. Set it up once.
Start free trialVerifying CRM data is reaching Google Ads
In Google Ads, go to Conversions and open your import conversion action. The Diagnostics tab shows every import attempt, the GCLID matched, the conversion time, and any errors. If conversions are uploading, you'll see recent entries within hours of a deal closing in your CRM.
Frequently asked questions
If the contact never clicked a Google ad (or the GCLID was not captured), there is nothing to upload. ConversionLoop logs these as unmatched and shows you the rate. If your match rate is low, the most common cause is cl.js not being on all your landing pages.
Yes. You can upload different conversion actions at different pipeline stages — one at Proposal Sent, one at Contract Signed, one at Closed Won. Each maps to a different Google Ads conversion action.
Never debug offline conversions again
Automated GCLID capture, real-time upload, and full error diagnostics. Every conversion, every time.
Start free — 14 days on usNo credit card required · No developer needed · Cancel anytime