Skip to content

How to Track Google Ads Campaigns in Attio

Google Ads tells you what you spent and how many clicks you bought. It does not tell you which of those clicks became a named lead in your CRM, or which campaign produced a paying customer. Closing that gap means carrying campaign information from the ad click all the way to the Attio record. This guide walks through the four setup steps, maps each UTM parameter to the form field it fills, and shows three reports worth building once the data arrives.

Why click-level ad data is not enough

Web analytics tools are good at counting visits. They are much weaker at answering how many leads and customers a campaign produced, because that answer lives in your CRM, not in a session report. The fix is to attach attribution details to each lead record at the moment a form is submitted, so Attio holds the campaign context alongside the person's name, email and company. Once that link exists, campaign performance becomes a query you can run rather than a guess you have to make.

Step 1: Tag every Google Ads destination with UTM parameters

Every ad needs UTM parameters on its final URL. The exact values are your choice, but a consistent scheme is what makes reporting possible later. A workable default:

  • utm_medium: paid search
  • utm_source: Google
  • utm_campaign: the Google Ads campaign name
  • utm_term: the ad group the ad belongs to
  • utm_content: the specific ad or keyword

Google Ads tracking templates make this a one-time configuration rather than a per-ad chore. Decide the scheme before you scale campaigns; retrofitting tags onto hundreds of ads is far more painful than tagging them at launch.

Step 2: Add hidden fields to your lead forms

Your lead capture forms — contact, quote request, demo request, anything that produces a record — need hidden fields that can receive the attribution values. The fields to add are:

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

How you add them depends on the form builder. Gravity Forms, Typeform and Jotform each have their own procedure, and generic hidden-field instructions cover the rest.

Step 3: Let the attribution layer fill those fields

With tagging and fields in place, the attribution script reads where the visitor came from and writes the corresponding values into the hidden fields. The values are derived from your UTM parameters, so the tagging scheme from step 1 determines what appears here.

A worked example: a visitor clicks a brand campaign ad, lands on the site and submits a form. The hidden fields populate roughly as follows — Channel becomes Paid search, Channel Drilldown 1 becomes Google, Channel Drilldown 2 becomes the campaign name (for example, Brand campaign), and Channel Drilldown 3 becomes the ad or keyword (for example, Free account ad). Separately, the visitor's first landing page (such as a features page URL) and its page group (such as features) are recorded too.

Step 4: Confirm the data reaches Attio

On submission, the attribution values travel into Attio together with everything else the visitor typed — name, email, company and any custom questions. From that point the campaign context is a property of the record, not a session detail.

Before you trust any report, submit a test form from a tagged URL and open the resulting record. Check that Channel, the three drilldowns and the landing page fields are populated with the values you expect. If they are blank, the problem is almost always upstream: missing tags, fields that were added but not mapped, or a form that never received the script.

What the attribution layer actually does

The script sits on your site and inspects the same signals analytics software uses to determine a visitor's origin. It sorts each visitor into a channel — paid search, paid social, organic search and so on — and stores that classification in a cookie in the browser. When the visitor later submits a lead form, the stored channel information is passed into Attio alongside the rest of the form data.

That cookie step matters: it is what allows attribution to survive a multi-page journey rather than depending on the form sitting on the landing page.

Why this beats capturing raw UTM strings

Sending raw UTM values straight into Attio is possible, and it is the obvious first approach. It also creates four recurring problems that a normalized attribution layer avoids.

  1. Coverage. Raw tagging only describes the traffic you tagged. A channel-level classification captures organic search, organic social, paid social and other sources too, so you can compare Google Ads against everything else rather than seeing only the paid slice.
  1. Persistence. Some simple capture methods only work when the form is completed on the same page the visitor landed on. Consider a visitor who arrives on a pricing page, navigates to a demo page and submits the request there. A same-page method would record nothing; a cookie-based approach carries the original values across the navigation.
  1. Consistency. Raw strings preserve whatever the person who built the URL typed. Suppose one batch of campaigns was tagged with a source of GoogleAds, a later batch with google-ads and an older set with adwords. Raw capture reports three separate sources. Normalization that accounts for capitalization and similar inconsistencies collapses them into one Paid Search channel.
  1. Landing page context. Beyond channel, the first landing page and its page group are captured, so you can report on which sections of the site — a blog, a features directory — produce leads, and drill into individual pages.

Field map: from UTM parameter to Attio record

Use this map when configuring forms and when auditing why a record looks wrong. The left column is what you set on the ad URL; the middle column is the hidden form field that receives it; the right column is what a correctly configured record should show for a paid search click.

Three reports worth building

Once records carry channel and campaign data, three report shapes cover most of the questions a marketing team asks.

Leads by channel answers "where do our leads come from overall?" Because every lead is classified, not just the tagged ones, you can compare Google Ads against organic search or paid social and see relative volume. If another channel is producing more leads at a comparable cost, that is a signal about budget allocation.

Customers by campaign answers "which Google Ads campaigns actually produce customers?" Broken out by month, it separates campaigns that generate interest from campaigns that generate revenue, and shows where additional investment is justified.

Revenue by keyword answers "which search terms pay for themselves?" It attributes revenue to the keyword level, which is the granularity you need when deciding where to raise bids to gain impression share.

Start with leads by channel to validate that classification is working, then add the campaign and keyword views as record volume grows.

Pre-launch checklist

Run through this before relying on any report:

  • Every active campaign uses the same UTM scheme, with no mixed conventions left over from previous managers or agencies.
  • All lead forms — not just the main contact form — carry the six hidden fields.
  • The attribution script is present on every page a visitor might land on, not only the pages you advertise.
  • A test submission from a tagged URL produces a record with Channel, all three drilldowns and landing page values filled.
  • A second test that lands on one page and submits on another still carries the original attribution.
  • Source values that differ only by capitalization or naming (Google.com, google, adwords) resolve to a single channel in reporting.

When attribution looks wrong

Two failures look similar but have different causes. If a record has no channel at all, the data never arrived: check that the URL was tagged, that the form has the hidden fields, and that the script loaded. If a record has a channel but the campaign or keyword is missing or split across several values, the data arrived but the tagging was inconsistent — the same campaign recorded under different spellings, or a drilldown level left untagged on some ads. Fixing the first is a configuration issue; fixing the second is a cleanup of your UTM conventions, and it is worth doing before the record count makes the mess expensive to untangle.

UTM parameter to Attio hidden field map
UTM parameterHidden form fieldExample value on a paid search click
utm_mediumChannelPaid search
utm_sourceChannel Drilldown 1Google
utm_campaignChannel Drilldown 2Brand campaign
utm_term / utm_contentChannel Drilldown 3Free account ad
(first page visited)Landing Pageattio.com/features/contact-management
(first page section)Landing Page Groupfeatures

Example values reflect the source's illustrative scenario, not a required naming convention. Your own UTM values determine what appears in each field.

Which report answers which question
ReportQuestion it answersGranularity
Leads by channelWhere do all our leads come from, and how does Google Ads compare?Channel
Customers by campaignWhich Google Ads campaigns produce customers each month?Campaign
Revenue by keywordWhich keywords generate revenue worth bidding more on?Keyword

Report shapes describe what the captured fields make possible; exact chart configuration depends on your Attio workspace setup.

Frequently asked questions

Do I have to use the suggested UTM values?

No. The medium, source, campaign, term and content values are your choice. What matters is consistency across campaigns, because the values you set determine how records group in reporting.

Why did a lead record arrive in Attio with no channel?

Usually one of three things: the ad URL was not tagged, the form is missing the hidden fields, or the attribution script did not load on the landing page. Test a submission from a tagged URL to isolate which.

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

With cookie-based attribution the original values persist, so the record still carries the campaign that brought the visitor in. Simple same-page capture methods lose the data in this scenario.

Our source values are inconsistent — Google.com, google, adwords. Will that break reporting?

Raw capture would treat them as three sources. Normalization that accounts for capitalization and naming variants groups them into a single Paid Search channel, which is why cleaning up conventions still matters even with normalization in place.

Can I report on landing pages as well as campaigns?

Yes. The first landing page and its page group are captured alongside channel data, so you can compare lead volume by site section and drill into individual pages.