Track Google Ads campaigns in Nimble CRM
You can see which Google Ads campaigns produce leads, opportunities and customers by carrying campaign identifiers from the ad click through the lead form into Nimble CRM. The setup below connects UTM parameters, hidden form fields and CRM reporting without asking visitors to enter campaign information.
Why campaign-level CRM reporting matters
Click data alone does not tell you whether a campaign created a qualified lead or a paying customer. When campaign details travel with the form submission, each Nimble CRM record can be grouped by the campaign, ad group and ad that originated it. That makes it possible to compare spend against leads, customers and revenue, and to stop or expand campaigns based on downstream results rather than clicks alone.
How the attribution flow works
A website code snippet identifies the visitor's channel and stores that information in a browser cookie. When the visitor submits a form, the stored channel details are added to the submitted name, email, company and other form values. In Nimble CRM, a paid-search lead can therefore show the channel alongside campaign, ad group and landing-page details instead of appearing as an unattributed enquiry.
Step 1: Tag every ad consistently
Append UTM parameters to the destination URL for every Google Ad. These are short text values added after the page address. Pick one naming convention and apply it to every campaign: use paid search as the medium, Google as the source, the campaign name as the campaign, the ad group as the term, and the specific ad as the content. A free UTM builder can help assemble the URL correctly.
Step 2: Add hidden fields to lead forms
Add six hidden fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Hidden fields are invisible to visitors, so they do not add friction to the form. Many form builders provide a hidden-field type that can be dragged into the form; follow the builder-specific instructions for your tool.
Step 3: Let the code populate the fields
Once the fields exist, the attribution code watches incoming visits and fills the hidden fields at submission using the UTM values from the original click. For a brand campaign example, Channel becomes Paid search, Drilldown 1 becomes Google, Drilldown 2 becomes Brand campaign, and Drilldown 3 becomes Free account ad. The first landing page and its group, such as a features page and the features section, are captured as well. Because the data is held in a cookie, it survives navigation to a different page before the form is completed.
Step 4: Send the data into Nimble CRM and verify it
On submission, the campaign and landing-page values are sent into Nimble CRM together with the lead's contact details. From there, use Nimble CRM's native reporting, or export the fields to a BI tool such as Tableau or Looker for more advanced analysis. Before building reports, check that a test submission created a record with every hidden field populated.
Reports to build once data is flowing
Three reports answer most budget questions. Leads by campaign, ad group or ad shows volume and trend over time, so you can see whether optimisation changes moved lead generation. Customers by campaign, ad group or ad shows which campaigns convert into buyers; a campaign with many leads but few customers may not be worth continuing. Revenue by campaign, ad group or ad connects attributed revenue to ad spend, giving a clearer view of return on investment. Use the same campaign breakdown across all three reports so the numbers are directly comparable.
Why classified channel data beats raw UTM values
Raw UTM capture has three common weaknesses. First, it only covers traffic that carries UTM parameters, while channel classification also covers organic search, organic social, referral and direct visits, giving a complete picture of lead origin. Second, raw parameters are lost if the form sits on a different page from the landing page; cookie storage prevents that loss. Third, inconsistent tagging such as Google.com, google and adwords fragments one source into several; channel classification normalises those variants. Landing-page capture adds a further dimension, showing which site sections and individual pages generate leads, customers and revenue.
Pre-launch checklist
Work through this checklist before trusting your reports: every ad carries the full UTM set; medium, source, campaign, term and content use one convention; all six hidden fields exist on every lead form; a test lead from a tagged ad arrives in Nimble CRM with channel, drilldowns and landing page filled; a test lead that navigates to a second page before submitting still carries the original campaign; and leads, customers and revenue reports use identical campaign groupings. Re-check after any form rebuild, because hidden fields are easy to drop during redesigns.
| UTM parameter | Value to use | What it identifies |
|---|---|---|
| UTM Medium | Paid search | Channel type |
| UTM Source | Traffic source | |
| UTM Campaign | Campaign name | Campaign |
| UTM Term | Ad group name | Ad group |
| UTM Content | Specific ad | Individual ad |
Convention recommended in source; apply consistently across all campaigns.
| Hidden field | Purpose |
|---|---|
| Channel | Broad channel such as paid search |
| Channel Drilldown 1 | Source level, such as Google |
| Channel Drilldown 2 | Campaign level |
| Channel Drilldown 3 | Ad level |
| Landing Page | First page the visitor arrived on |
| Landing Page Group | Section of that landing page |
Field names as listed in source; confirm exact labels in your form builder and CRM.
| Report | Question it answers |
|---|---|
| Leads by campaign, ad group or ad | Which campaigns generate enquiries, and how does that change over time? |
| Customers by campaign, ad group or ad | Which campaigns produce buyers rather than only leads? |
| Revenue by campaign, ad group or ad | Which campaigns return revenue above their ad spend? |
Build all three on the same campaign breakdown for comparability.
Frequently asked questions
How do I get Google Ads campaign data into Nimble CRM?
Add consistent UTM parameters to each ad, add hidden fields to lead forms, let the attribution code populate those fields from the visitor's stored channel data, and pass the completed form data into Nimble CRM. Then report on the stored campaign fields.
Which hidden fields are needed on the form?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Visitors do not see these fields, but form submissions can carry their values into the CRM.
What UTM convention should I use for Google Ads?
Use Medium for paid search, Source for Google, Campaign for the campaign name, Term for the ad group, and Content for the specific ad. Consistency matters more than the exact labels, because inconsistent values split one campaign into several apparent sources.
What if a visitor completes the form on a different page from the landing page?
Yes. The attribution data is stored in a browser cookie, so a visitor who lands on one page and completes a form on another page can still be matched back to the original campaign.
Which reports are most useful once the data is in Nimble CRM?
Build reports for leads by campaign, ad group or ad; customers by campaign, ad group or ad; and revenue by campaign, ad group or ad. Comparing leads with customers helps separate campaigns that create interest from campaigns that create buyers.