Track Google Ads campaigns in Agile CRM
You can connect Google Ads activity to leads, opportunities, customers, and revenue in Agile CRM by tagging ads consistently, capturing attribution through hidden form fields, and reporting on the resulting CRM records. This guide explains the four-step setup, the field mapping, and the reports to build after data starts flowing.
Why campaign context matters in the CRM
Without campaign context in the CRM, a lead record shows who contacted you but not which ad, ad group, or campaign produced the enquiry. That gap makes it hard to judge whether spend is creating valuable demand. Once attribution fields travel with the lead, Agile CRM can group records by campaign and show which activity leads to opportunities, customers, and revenue. A website attribution script can identify the visit origin, classify it into channels such as paid search, paid social, or organic search, store that classification in a browser cookie, and submit it with the form data.
Step 1: Tag every ad with consistent UTM parameters
Start by appending UTM parameters to the destination URL for every Google ad. These parameters are simply extra URL text that identifies medium, source, campaign, ad group, and ad. A consistent convention prevents fragmented reporting later. For Google Ads, set utm_medium to paidsearch, utm_source to google, utm_campaign to the campaign name, utm_term to the ad group name, and utm_content to the specific ad. A UTM builder can help assemble the final URL, but consistency matters more than the tool used.
Step 2: Add hidden attribution fields to lead forms
Next, add hidden fields to each lead-capture form. Visitors cannot see these fields, yet the form can still submit their values. Add Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Most form builders used with Agile CRM workflows support a hidden-field type that can be dragged into the form. Use the form builder's own instructions to confirm field names and submission behaviour before going live.
Step 3: Populate the hidden fields from the visit
When a visitor submits a form, the attribution tool fills the hidden fields from the stored visit data. In a paid-search example, Channel becomes Paid search, Drilldown 1 becomes Google, Drilldown 2 becomes the campaign name, and Drilldown 3 becomes the ad name. The tool also records the landing page and its group, such as a features page and the features section. This mapping is the key check: if the CRM values do not match the intended UTM convention, fix tagging or field mapping before building reports.
Step 4: Report leads, customers, and revenue in Agile CRM
On submission, Agile CRM receives the contact details together with channel, drilldown, and landing-page values. From there, use native CRM reporting for standard views or send the data to a business-intelligence tool for more advanced analysis. Build three core reports: leads by campaign, ad group, or ad; customers by the same breakdown; and revenue by campaign, ad group, or ad. Comparing the three reveals whether a campaign creates enquiries only, converts into customers, or produces enough revenue to justify its cost. An illustrative revenue chart in the original material showed a monthly paid-social figure, but treat any such number as dated example evidence rather than a current benchmark.
Why normalised attribution beats raw UTM capture
Capturing raw UTM values alone has three common weaknesses. First, it may cover only tagged paid traffic, while channel classification can also include referral, direct, organic search, and organic social visits. Second, raw parameters disappear if the visitor moves from the landing page to a separate form page; cookie storage preserves the attribution across navigation. Third, inconsistent tagging creates messy groups, such as Google.com, google, and adwords appearing as separate sources. Normalising values into a single paid-search channel avoids manual stitching. Landing-page capture adds another useful dimension: you can evaluate a whole section, such as a blog, and also drill into individual pages.
Pre-launch checklist
Before launch, test one paid-search visit end to end: confirm the final URL carries all five UTM parameters, submit a test form, and check that Agile CRM receives the expected channel, drilldowns, landing page, and landing-page group. Then submit a test from a different entry channel and from a form on a different page to confirm persistence and normalisation. Once those checks pass, build the leads, customers, and revenue reports and review them over time so campaign changes can be compared with downstream results.
| UTM parameter | Value to use | What it identifies |
|---|---|---|
| utm_medium | paidsearch | Paid-search channel |
| utm_source | Traffic source | |
| utm_campaign | Campaign name | Google Ads campaign |
| utm_term | Ad group name | Ad group |
| utm_content | Specific ad | Individual ad |
Recommended Google Ads tagging convention from the original guide.
| Hidden field | Example value | Purpose |
|---|---|---|
| Channel | Paid search | Broad channel classification |
| Channel Drilldown 1 | Source detail | |
| Channel Drilldown 2 | Brand campaign | Campaign detail |
| Channel Drilldown 3 | Free account ad | Ad detail |
| Landing Page | Landing-page URL | First page visited |
| Landing Page Group | First path section | Site section grouping |
Example paid-search values; actual values come from the visit and UTM parameters.
| Report | Question it answers |
|---|---|
| Leads by campaign, ad group, or ad | Which paid activity creates enquiries? |
| Customers by campaign, ad group, or ad | Which activity creates buyers, not just leads? |
| Revenue by campaign, ad group, or ad | Which activity produces enough revenue to justify spend? |
Core reporting views enabled once attribution data reaches Agile CRM.
Frequently asked questions
What is the basic workflow for tracking Google Ads in Agile CRM?
Add consistent UTM parameters to each ad, include hidden channel and landing-page fields on your lead forms, let an attribution tool populate those fields from the visit, and submit the lead to Agile CRM. The CRM record then carries the campaign context alongside contact details for reporting.
Which UTM values should Google Ads use?
Use utm_medium for paid search, utm_source for Google, utm_campaign for the campaign name, utm_term for the ad group, and utm_content for the specific ad. Keeping the same convention across campaigns makes later grouping reliable.
Which hidden fields are needed on the form?
Add Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group as hidden fields. Visitors do not see them, but the form can submit their values with the lead.
Why can raw UTM parameters be lost before form submission?
Raw UTM capture can fail when the form is on a different page from the landing page, because the parameters may no longer be in the URL. Storing the attribution in a browser cookie allows the values to be submitted from the later form page.
What reports become possible after the data reaches Agile CRM?
Compare leads, customers, and revenue by campaign, ad group, or ad. A campaign generating many leads but few customers may need different targeting or follow-up, while revenue by campaign helps assess return on ad spend.
Can the same setup cover non-Google Ads traffic and landing pages?
Yes. Channel grouping can also cover referral, direct, organic search, and organic social visits, so reporting is not limited to paid search. Landing-page and landing-page-group fields additionally show which site sections produce leads, customers, and revenue.