Skip to content

How to track Google Ads campaigns in Copper CRM

If you can see which Google Ads campaigns produced a lead, an opportunity and a paying customer inside Copper CRM, budget decisions stop being guesswork. This guide walks through the setup that makes that possible: consistent UTM tags on your ads, matching hidden fields on your lead forms, and a tracking layer that carries the channel and landing page data into Copper CRM with each submission. It closes with the three reports worth building first and the trade-offs between raw UTM capture and a normalizing layer.

Why campaign-level data belongs in the CRM

Ad platforms report clicks and conversions, but the CRM is where a lead becomes an opportunity and then a customer. When the originating campaign travels with the record, you can compare campaigns on outcomes rather than clicks: which ones fill the pipeline, which ones close, and which ones generate revenue that justifies their cost. Without that link, you can only guess which campaigns to keep and which to cut. The setup described here sends campaign, ad group, ad and landing page context into Copper CRM alongside the lead's name, email and company details, so reporting can be built natively or exported to a BI tool such as Looker or Tableau for deeper analysis.

What the tracking layer actually does

Attribution Analytics is a small script placed on your website. On each visit it inspects technical signals about how the visitor arrived and groups them into channels such as paid search, paid social and organic search. That channel information is written to a cookie in the visitor's browser. When the visitor submits a lead form, the stored values are passed into Copper CRM together with whatever the form itself collected. A lead arriving from a Google Ads campaign therefore carries a channel of paid search plus campaign, ad group and landing page details.

Step 1: Tag every Google Ads URL

Add UTM parameters to the final URL of each ad. They are simply extra text appended to the destination address, and they are what tells the tracking layer which campaign, ad group and ad produced the click. The recommended convention for Google Ads is:

Recommended UTM values for Google Ads

Use these pairings consistently across every ad so reports stay comparable:

  • UTM Medium = Paid search
  • UTM Source = Google
  • UTM Campaign = the name of your Google Ads campaign
  • UTM Term = the name of the ad group the ad belongs to
  • UTM Content = the specific ad

You can build these by hand or with a free online UTM builder. The convention matters more than the tool: pick one spelling per value and reuse it.

Step 2: Add hidden fields to your lead forms

Hidden fields are invisible to visitors but available to the tracking script, which fills them in behind the scenes. Create the following fields in your form builder:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

Most form builders let you drag a hidden field type into the form. Builder-specific instructions are available in the help documentation linked below.

Step 3: Let the script fill the hidden fields

Once the fields exist, the script watches where visitors come from and populates the hidden fields from your UTM values at submission time. A worked example makes the mapping concrete. Suppose a visitor reaches your site from a brand campaign in paid search. The fields would resolve as follows:

Worked example: one click, six field values

Take a visitor who clicked a brand-campaign ad in paid search. The hidden fields resolve like this:

  • Channel = Paid search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Brand campaign
  • Channel Drilldown 3 = Free account ad
  • Landing Page = the first page they landed on
  • Landing Page Group = the first path segment of that page

Beyond the UTM values, the script also records the visitor's landing page and its first group, so you can report on sections of your site as well as individual pages.

Step 4: Confirm the data reaches Copper CRM

On every form submission, the Google Ads data, the landing page data and the lead's own contact details are sent into Copper CRM. From there you can report with Copper's native tools or push the records into a BI tool such as Looker or Tableau for more advanced analysis. Before trusting any report, submit a test lead from a tagged ad URL and confirm that all six hidden fields arrive populated on the record.

Three reports to build first

With the data flowing, these reports give you the clearest read on performance:

  1. Leads by campaign, ad group or ad — monthly lead counts grouped by originating campaign. Viewed across several months, it shows both the split per month and how volume shifts, which helps you judge whether optimizations actually moved the needle.
  2. Customers by campaign, ad group or ad — new customers per month by originating channel. Set beside the leads chart, it exposes campaigns that produce leads which never convert, a signal that continued spend there may not pay off.
  3. Revenue by campaign, ad group or ad — monthly revenue attributed to the channel a customer came from. This is the report that supports ROI calculations.

Read them as a set. A campaign that looks strong on leads but weak on customers and revenue is a different problem from one that is weak everywhere.

Reading the revenue report as an ROI check

The illustrative revenue chart in the original walkthrough showed $236,156 in new revenue attributed to paid social ads in March. Treat that figure as an example of the arithmetic, not a benchmark: if spend on those ads was below the attributed revenue, the campaign returned a positive ROI and is a candidate to continue. The same subtraction, run per campaign, turns the revenue report into a budget decision.

Raw UTM capture versus a normalizing layer

Other systems can capture UTM parameters and pass them to Copper CRM. Four differences are worth weighing before you choose.

It captures traffic beyond Google Ads

A UTM-only setup records tagged campaigns. A channel-aware layer also classifies visitors arriving from organic social, organic search and direct traffic, so CRM reports can show the source of all leads rather than only the paid ones. That matters when organic search, not paid search, supplies most of your pipeline: without the comparison you cannot judge where budget is best spent.

It remembers the source across pages

Raw UTM capture generally depends on the parameter still being present in the URL at the moment the form is submitted. That dependency breaks as soon as the conversion path crosses more than one URL: a visitor clicks an ad, lands on a campaign page, reads it, then follows a link to a separate request form. The query string does not follow them, so the source is gone by the time the form loads. Storing the values in a browser cookie separates capture from submission, which means the original source remains available regardless of how many pages the visitor viewed before converting.

It keeps source values consistent

Raw UTM data tends to drift into multiple spellings over time. One source might be recorded as a capitalized domain, another as a lowercase bare word, and another under an older platform name, and each spelling arrives in Copper CRM as a distinct source value. Until those spellings are merged, a lead count by source is unreliable. A normalizing layer recognizes capitalization and similar inconsistencies and assigns the lead to the correct channel, so the source dimension stays reportable without manual cleanup.

It records landing page and page group

Knowing which sections of your site generate leads and customers is useful in its own right — a blog, for instance, or a set of in-depth content pieces. Because the landing page and its first path segment are captured, you can report on a whole section and still drill into an individual page.

Pre-launch checklist

Work through this before you rely on the numbers:

  • Every active ad has a final URL carrying all five UTM parameters.
  • UTM Medium reads Paid search and UTM Source reads Google on every ad, spelled identically.
  • Campaign, term and content values match the actual campaign, ad group and ad names.
  • All six hidden fields exist on every lead form, not just the main one.
  • A test submission from a tagged ad URL arrives in Copper CRM with every hidden field populated.
  • A test submission that passes through an intermediate page before the form still carries the original source.
  • Reports group by campaign and can be filtered to a date range long enough to compare months.

Two failure modes and how to tell them apart

When attribution looks wrong, the cause is usually one of two things, and they need different fixes.

No source recorded at all. The hidden fields are missing from the form, or the script is not present on the page where the form is submitted. Check the form markup first, then the site-wide installation.

Source recorded but fragmented. Leads are arriving with source values, but the same campaign appears under several spellings. This is a tagging discipline problem: standardize the UTM values on your ads and the fragmentation stops accumulating.

A third, subtler case: the source is recorded but attached to the wrong page. That points to a form that submits on a different URL than the landing page without cookie-based memory — the scenario the cookie approach is designed to solve.

Where this leaves you

Tagging ads consistently, adding the six hidden fields and confirming the data lands in Copper CRM gives you a campaign-to-revenue trail you can report on. The payoff is comparative: campaigns judged on customers and revenue, not just lead volume, and a full picture of lead sources rather than only the paid ones.

UTM value to hidden field mapping
UTM parameterRecommended Google Ads valueHidden field populated
UTM MediumPaid searchChannel
UTM SourceGoogleChannel Drilldown 1
UTM CampaignName of your Google Ads campaignChannel Drilldown 2
UTM TermName of the ad groupChannel Drilldown 3
UTM ContentThe specific ad(feeds ad-level reporting)
— (captured automatically)Visitor's landing page URLLanding Page
— (captured automatically)First path segment of the landing pageLanding Page Group

The mapping of UTM Content to ad-level reporting reflects the source's stated convention that UTM Content identifies the specific ad; the source does not name a separate hidden field for it. Landing Page and Landing Page Group are captured from the visit, not from UTM values.

What each example report answers
ReportGroupingQuestion it answersWatch for
Leads by campaign, ad group or adOriginating Google Ads campaignHow many leads per month came from each campaign, and how that changed over timeVolume shifts after optimizations may reflect seasonality as well as changes you made
Customers by campaign, ad group or adChannel the customer arrived fromWhich campaigns produce customers, not just leadsCampaigns with leads but no customers — a signal continued spend may not pay off
Revenue by campaign, ad group or adChannel the customer came fromMonthly revenue attributed to each source, for ROI calculationCompare against actual ad spend before concluding ROI is positive

These are the three report types described in the original walkthrough, published 22 August 2022. The revenue figure cited there ($236,156 from paid social ads in March) is an illustrative example from that article, not a current benchmark or a verified result.

Frequently asked questions

Do I have to use UTM parameters, or can the tool work out the campaign on its own?

Tagging is required. The hidden fields are populated from the UTM values on your ad URLs, so an untagged ad has nothing to pass through. The recommended convention is Paid search for medium, Google for source, and your campaign, ad group and ad names for campaign, term and content.

What happens if a visitor lands on one page but submits the form on another?

With cookie-based storage the original source survives the journey, so the campaign is still recorded. Raw UTM capture that reads only the submission page would lose it at the page change.

Why do the same Google Ads leads show up under several different sources?

Inconsistent tagging. Values like a capitalized domain form, a lowercase bare word and an older platform name are treated as separate sources when stored raw. A normalizing layer reconciles them; otherwise you merge them by hand before counting leads.

Can I report on a whole section of my site, such as the blog, rather than single pages?

Yes. The landing page and its first path segment are both captured, so you can report at section level and still drill down to an individual page.

Where do the reports get built?

Inside Copper CRM using its native reporting, or by sending the records to a BI tool such as Looker or Tableau when you need more advanced analysis.