How to Track Google Ads Campaigns in Your CRM
If you can see clicks and sessions in an ad platform but cannot tell which campaigns produce leads and customers, the missing link is usually the CRM record. This guide shows a practical way to carry Google Ads context from the first click through to the lead or contact record, so you can compare channels, campaigns and keywords on business outcomes rather than clicks alone.
Four steps to connect Google Ads with your CRM
The setup has four moving parts: tag the ad URLs, prepare the form to receive the data, let the capture tool fill the fields, and make sure the form submission reaches the CRM. Each step has a clear job, and a gap in any one of them will leave attribution holes.
Before you begin, decide which form tool you will use. If your CRM has a built-in form builder, the data path is shorter. If you use a separate form builder, plan how submissions currently travel to the CRM — either a native integration or a third-party connector. The rest of the setup should follow that existing path rather than creating a second one.
Step 1: Tag your Google Ads URLs
UTM parameters are text appended to the destination URL. They tell your capture tool which campaign, ad group and ad produced the visit. A consistent convention matters more than the exact words you choose, because inconsistent capitalisation and naming will fragment your reports later.
A sensible starting convention for Google Ads is:
- UTM Medium: Paid search
- UTM Source: Google
- UTM Campaign: the Google Ads campaign name
- UTM Term: the ad group name
- UTM Content: the specific ad
Apply the same convention across every ad. If one campaign uses google and another uses Google, raw UTM capture will treat them as separate sources. A capture tool that normalises these values can still assign both to Paid Search, but clean tagging reduces the cleanup work.
Use the source help video for the tagging workflow if you need a walkthrough.
Step 3: Let the capture tool fill the fields
Once the fields exist, the capture tool reads the visitor's source and writes values into the hidden fields at submission time. The tool you choose must be able to remember the original source even when the visitor moves to another page before completing the form — that is a requirement to check against your tool's documented behaviour, not a property of every capture method.
A worked example makes the mapping clearer. Suppose a visitor clicks a Google Ad for Olmo Software, lands on the site, browses to another page and then submits a "Request A Demo" form. Depending on the UTM tags used, the record could contain:
- Channel = Paid search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand campaign
- Channel Drilldown 3 = Olmo Software
- Landing Page = the first page the visitor saw
- Landing Page Group = the section of the site that page belongs to
This is the key difference from capturing only the URL of the form page. The form page may be a generic contact page with no campaign information in its address.
Step 4: Send the completed form into your CRM
When the form is submitted, the hidden-field values travel with the rest of the lead data. If you use the CRM's own form builder, the record usually appears on the lead or contact automatically. If you use a separate form builder, send the submission through the same integration you already use for leads — a native connector or a third-party automation tool.
Check one test submission end to end. Confirm that the hidden fields are present on the CRM record, not just in the form builder's submission log. A field that exists in the form but is not mapped to a CRM property will not appear in reports.
Why a dedicated capture layer can beat raw UTM fields
Capturing raw UTM strings directly into the CRM works only when the parameters are present on the page where the form is completed. That condition often fails: a visitor may land on an ad page, navigate elsewhere, and convert on a different page. A capture tool that stores the source in a cookie can pass the original values through regardless of the conversion page, so check your tool's documentation for this behaviour before you rely on it.
A second advantage is cleaner grouping. Raw values such as Google, google and adwords can appear as three separate sources. A capture tool that recognises these variants can assign them to one channel, such as Paid Search, so confirm the normalisation behaviour of whichever tool you adopt.
A third advantage is coverage beyond Google Ads. A capture layer may also record Paid Social, Organic Search, Organic Social and Direct traffic, so channel reports show the full picture rather than only paid search. Confirm which channels your tool captures before you depend on it.
Finally, landing-page data adds a content dimension. Where a tool captures it, you can see which sections of the site and which individual pages produce leads and customers, not just which campaign brought the visit.
Three reports worth building once the data is in the CRM
The value of the setup appears in the reports you can run against CRM records. These three cover different decisions.
Leads by channel. Compare Google Ads with Organic Search, Paid Social and other channels. Use it to decide whether paid search deserves more budget or whether another channel is producing more leads for the same effort.
Customers by campaign. Group customers by the Google Ads campaign that first brought them in. This shows which campaigns produce closed business, not just form fills, and helps you decide where to keep spending.
Revenue by keyword. Group revenue by the keyword or ad group term attached to the lead. This shows which keywords are commercially strongest and where a bid increase is more likely to pay for itself.
These reports depend on the CRM record carrying the campaign fields reliably. If a field is missing on a large share of records, fix the capture path before drawing conclusions from the report.
Setup checklist and failure distinctions
Use this checklist before trusting the reports:
- Every Google Ads destination URL carries the same UTM convention.
- The form contains all six hidden fields.
- The capture tool is loaded on the site and can write to those fields.
- A test submission shows the hidden values on the CRM record.
- The CRM report groups by the hidden fields, not by free-text notes.
Two failures look similar but have different fixes. If the campaign fields are blank on every record, the capture tool or the hidden-field mapping is missing. If the fields are populated but the channel report shows many small source rows, the UTM naming is inconsistent and needs normalising. Check which pattern you see before changing the setup.
Frequently asked questions
Do I have to use UTM parameters for Google Ads tracking?
UTM parameters are the mechanism that carries campaign, ad group and ad information into the form fields. Without them, the capture tool has no campaign labels to pass through. Google Ads' own auto-tagging can support platform-side reporting, but it does not populate the CRM hidden fields described here.
Why does the form page URL not show the campaign?
The form page is often a generic contact or demo page reached after the visitor has moved away from the ad landing page. The campaign parameters were on the landing URL, not the form URL. A capture tool that stores the original source in a cookie can pass the values through to the later form submission; check that your tool does this.
Can I use my CRM's built-in form instead of a separate form builder?
Yes. If the CRM's form builder supports hidden fields, add the six fields there and the values should flow onto the lead or contact record. If it does not support hidden fields, use a form builder that does and send submissions to the CRM through your existing integration.
What happens if my UTM source values are inconsistent?
Raw capture will treat Google, google and adwords as separate sources, which fragments the channel report. A capture tool that recognises these variants can group them under one channel; the original article attributes that normalisation to its own product, so confirm your tool's behaviour. Consistent tagging reduces the problem at the source.