Skip to content

Capture UTM Parameters in Pardot

Website analytics can show visits by campaign, but that does not automatically show which campaigns produced leads, opportunities, customers, or revenue. Capturing attribution data at form submission closes that gap: when a visitor converts, Pardot receives the channel and landing-page context alongside the contact record.

Four-step setup

Start with tagging. Every active paid and bespoke campaign needs consistent UTM parameters so the arrival can be recognised later. That includes search ads, social ads on platforms such as Facebook, LinkedIn, Instagram, and Twitter, and offline or sponsored placements that drive traffic to the site.

Next, add hidden fields to the lead-capture form. Hidden fields sit on the form but are not shown to visitors. Use these fields:

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

The same approach works with Pardot's form builder and with other form tools, provided the hidden fields are present and named consistently.

How the handoff works

A small site snippet reads arrival information when a visitor lands, determines the source channel, and stores it in a browser cookie. When a form is submitted, the snippet writes the stored values into the hidden fields, and Pardot receives them with the submission.

Worked example: a visitor clicks a paid-search ad for a brand campaign, lands on an email-features page, and then completes a demo-request form. The submitted record can carry:

  • Channel: Paid Search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Brand Campaign
  • Channel Drilldown 3: Pardot
  • Landing Page: www.pardot.com/features/email
  • Landing Page Group: Features

Once in Pardot, the data can sit beside the contact record, appear in lead-notification emails, flow to a CRM such as Salesforce, or be exported to a spreadsheet for reporting in tools such as Google Data Studio or Microsoft Power BI.

Why this beats raw UTM capture alone

Capturing only raw UTM values covers paid campaigns and only when the form is completed on the landing page. A cookie-based approach improves on that in four ways.

It covers all traffic, including Organic Search, Organic Social, Direct, and Referral, so every lead carries a channel rather than only tagged paid traffic. It remembers the data across pages, so moving from a landing page to a separate form page does not lose attribution. It cleans inconsistent tagging, for example by grouping variants of a search source into Paid Search instead of treating each spelling as a separate source. It also captures landing-page and landing-page-group data, allowing reports by individual page and by content section.

Reports and pre-launch checklist

Use the captured fields to answer budget and content questions directly:

  • Leads by Channel: compare monthly lead volume across channels to spot where growth is actually coming from and whether spend matches performance.
  • Leads by Facebook Ads Network: split Facebook-family results by network to shift budget toward the network producing leads at a lower cost.
  • Customers by Google Ads Campaign: compare campaigns by paying customers, not just clicks or leads, and focus optimisation on the campaigns that convert to revenue.
  • Revenue by Keyword: when keyword is included in Google Ads UTM parameters via tracking templates, compare keywords by revenue to guide bidding, SEO priorities, and site messaging.

Checklist before reporting: confirm every active campaign is tagged, every conversion form has all six hidden fields, the snippet is installed on all landing pages, and channel values are normalised so variants do not fragment reports.

Wrap up

With tagging, hidden fields, and cookie storage in place, Pardot can attribute leads to the campaigns and content that produced them, including organic channels and specific landing pages. If you are evaluating a tool for this job, check its current trial terms and pricing directly before committing, since those details vary by provider and plan.

Frequently asked questions

What is the basic setup for capturing UTM data in Pardot?

Add UTM parameters to every active campaign first, including social and search ads and bespoke placements such as newsletter sponsorships and trade-publication banners. Then add hidden fields to each lead form, install the attribution snippet on the site, and let it store arrival data in a browser cookie until a form is submitted. On submission, the stored values populate the hidden fields and travel with the lead into Pardot.

Does the data survive if the form is on a different page from the landing page?

Yes. Because arrival data is stored in a cookie rather than read only from the landing-page URL, a visitor can move from a campaign landing page to a quote or demo form on another page and still pass the original attribution data through.

Why normalise UTM values instead of storing them raw?

Raw values can fragment reporting when the same source is written in different forms, such as different capitalisations or domain variants. Normalising those variants into a consistent channel, such as Paid Search, keeps campaign reporting from splitting one source into several.

What extra data comes with the channel fields?

It also records the landing page and its group, so you can compare individual pages and broader content sections. That makes it possible to see whether a blog, a features section, or a single article is producing leads, opportunities, customers, or revenue.