Skip to content

Getting UTM parameters into Attio for campaign reporting

Attio can show which campaigns create leads and customers only if campaign details travel with each lead. This guide explains a four-step setup using UTM tagging, hidden form fields, cookie storage and CRM reporting, plus the checks that prevent messy or missing attribution.

1. Tag campaigns consistently

Tag every paid campaign before traffic arrives. Add UTM parameters to social, search and trade-publication campaigns so the originating source, medium and campaign can be recognised later. Keep naming consistent from the start: decide capitalisation and abbreviations centrally, because later cleanup is harder once several people or agencies have created variants.

2. Add hidden fields to lead forms

Add hidden fields to each lead form for Channel, Channel Drilldown 1, Channel Drildown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Most form builders let you drag in a hidden field type. Test a submission to confirm each field accepts a value and maps to the correct Attio field.

3. Let the code fill the fields at submission

Website code identifies the visit source, classifies it into a channel such as Paid Search, Paid Social or Organic Search, and stores that classification in a browser cookie. When a form is submitted, the code fills the hidden fields from the stored visit. Example: a Paid Search brand visit could produce Channel = Paid Search, Drilldown 1 = Google, Drilldown 2 = Brand Campaign, Drilldown 3 = Attio, with the first landing page and its group recorded alongside.

4. Pass the data into Attio and report

On submission, UTM values, channel classification and landing page details should arrive in Attio with name, email and phone. Build reports in Attio or a connected BI tool to compare lead volume, opportunity conversion and closed deals by channel and campaign. Cookie storage matters when a visitor lands on a campaign page but completes a form on a later page, where raw UTM parameters would otherwise be absent.

Why classification beats raw UTM capture alone

Raw UTM capture has three gaps. It misses organic search, organic social, referral and direct visits that carry no UTM parameters. It loses data when the form page differs from the landing page. It also fragments reporting when the same source is written as Facebook, facebook or fb. A classification layer that covers all traffic, stores the visit in a cookie, normalises variants into one channel and records landing page and group gives a fuller, cleaner picture.

Reports worth building first

Use the captured fields to answer budget questions. Leads by channel reveal whether paid spend matches where demand actually originates. Leads by Facebook network show which placements generate leads. Customers by Google Ads campaign separates campaigns that create buyers from those that only create visits. Revenue by keyword, when keyword is included in Google Ads UTM parameters, supports bid and SEO decisions. Before acting, check that drilldown values are normalised and that landing page groups are not too granular to interpret.

Four example Attio reports
ReportQuestion it answersFields needed
Leads by ChannelWhich channels generate leads?Channel
Leads by Facebook Ads NetworkWhich Facebook network generates leads?Channel Drilldown values
Customers by Google Ads campaignWhich campaigns generate customers?Channel Drilldown values, customer status
Revenue by KeywordWhich keywords generate revenue?Keyword in UTM parameters, revenue

Example reports described in source; validate field names in owner's Attio workspace.

Frequently asked questions

What are the four steps to capture UTM data in Attio?

Add UTM parameters to campaigns, place hidden fields on lead forms for channel, drilldowns, landing page and landing page group, let the attribution code store the visit details in a browser cookie, and pass those values into Attio with the lead record.

Why not capture raw UTM parameters alone?

Raw UTM capture only works when parameters are present on the form page and misses organic visits. Cookie-based capture preserves the original visit across pages and can classify organic search, organic social, referral and direct traffic as well as paid campaigns.

How does normalisation help reporting?

Inconsistent values such as Facebook, facebook and fb can split one source into several report rows. Normalising those values into a single channel, such as Paid Social, keeps reporting cleaner.

Which reports become possible in Attio?

Leads by channel, leads by Facebook ad network, customers by Google Ads campaign, and revenue by keyword when keyword is included in Google Ads UTM parameters.