Send CRM outcomes back to Google Ads as offline conversions
Google Ads can learn from more than a thank-you page. When a CRM milestone shows that a lead was genuinely valuable, sending that outcome back with the original click identifier lets bidding focus on the behaviour that produced qualified pipeline rather than every form submission.
Choose a conversion point that can actually teach the system
Waiting for a closed sale sounds precise, yet it can starve automated bidding of usable feedback. Google guidance cited in the source material points to roughly 50 conversions a month for strategies such as Maximise Conversions, Maximise Conversion Value and Target CPA. A second constraint is the 90-day conversion window: a lead whose journey from click to customer exceeds that period may be too late to influence the original campaign.
Conversion-point checklist
Use this decision check before building the automation:
1. Capture the click identifier on the lead
The GCLID is the click identifier Google appends to a landing URL after an ad click. It is the link between the CRM record and the paid click, so it must be stored on the lead before any later milestone can be reported. A website capture tool can retain the identifier and UTM values when the visitor arrives, then pass them with the form submission into the CRM. The exact capture product is an implementation choice; the required outcome is a populated GCLID field on each eligible lead.
2. Create the offline conversion action
In Google Ads, open Goals, then Conversions, and add a new conversion of the Offline type. Choose the category closest to the CRM milestone, such as Qualified Lead or Converted Lead. For the data source, choose to add it later because the automation will be connected in the next step.
3. Automate the upload from the CRM
Build an automation in Zapier with the CRM milestone as the trigger. Examples include creating a deal, marking a contact qualified, or another agreed event. Supported CRM triggers may include HubSpot, Salesforce, Pipedrive, Zoho CRM and Close CRM, or a spreadsheet.
Field map for the automation
Map the automation as follows: select the destination Google Ads account; set Conversion User Identification Source to Google Click ID (GCLID); map the CRM GCLID field; select the offline conversion created in Google Ads; and supply a timestamp from the CRM event or the current time. Test the automation before switching it on.
Test the full path before trusting it
Confirm auto-tagging is enabled, then use a real search click in an incognito window. Ad Preview will not produce a genuine GCLID. Submit a form and verify the identifier appears in the CRM. Next, trigger the chosen CRM milestone and check Zap History for a successful run. Finally, open Tools and Settings, Conversions, and Uploads in Google Ads; a new upload may show as Processed within about three hours. If the run fails, inspect the log first for a blank CRM field or an incorrect field mapping.
Improve reliability and bidding signals
Add a filter so only records with a non-blank GCLID are sent. This avoids unnecessary rejected uploads and noisy error logs. Where possible, include conversion value: use actual revenue for a customer, expected deal value for an open deal, or an expected value calculated from average deal size multiplied by close rate. For example, a $1,000 average deal at a 25% close rate gives an expected value of $250 per deal. Value data can support value-based bidding, including Target ROAS. Email or phone may also be sent to improve matching, but that shares personal information with Google, so privacy and legal review should come first.
| Check | Pass condition |
|---|---|
| Volume | The milestone happens at least 50 times per month. |
| Timing | It normally occurs within 90 days of the ad click. |
| Quality | It represents a meaningfully qualified outcome, not every form fill. |
| Identifier | The CRM record contains a non-blank GCLID. |
Use the same milestone consistently for the upload and bidding feedback.
| Automation field | Value to map |
|---|---|
| Trigger | CRM milestone, such as deal created or lead qualified |
| Destination account | The Google Ads account receiving the conversion |
| Identification source | Google Click ID (GCLID) |
| Identifier value | CRM field populated at lead capture |
| Conversion action | Offline conversion created in Google Ads |
| Timestamp | CRM event date or current date and time |
| Optional value | Revenue, expected deal value, or calculated expected value |
Field names are descriptive labels for this workflow, not a claim about a protected schema.
Frequently asked questions
Should the offline conversion be sent when a deal closes?
Use an earlier CRM milestone, such as a qualified lead or a created deal, if closed customers are too infrequent or too slow. The milestone should occur at least 50 times a month and within 90 days of the ad click.
Can I test GCLID capture with Ad Preview?
A real search-result click is required. The Ad Preview tool does not create a genuine click and therefore does not generate a GCLID.
What happens if a CRM record has no GCLID?
Google Ads will reject uploads without a GCLID. Filtering blank values keeps automation logs cleaner and makes genuine failures easier to spot.