Skip to content

Get UTM Parameters Into Pipedrive and Report on Every Lead Source

If you cannot tell which campaigns create leads, customers and revenue, budget decisions become guesswork. Passing campaign data into Pipedrive with each form submission lets you report by channel, campaign, network, keyword and landing page inside the CRM or a connected BI tool.

Four steps to capture UTM data in Pipedrive

Install a small tracking snippet in the website settings or header area. The exact placement depends on the builder in use, such as WordPress, Webflow or Squarespace, and builder-specific guidance should be followed for that platform.

Add hidden fields to each lead-capture form, including contact, demo-request and download forms. The fields to add are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Form tools commonly used for this include Contact Form 7, Gravity Forms and Wufoo.

When a visitor arrives, the snippet examines UTM parameters and HTTP referrer data, assigns a channel such as Paid Search, Organic Search or Paid Social, and stores that attribution in the browser. On form submission it fills the hidden fields automatically.

On submission, the channel and landing-page values travel to Pipedrive together with the lead's name, email, phone and other contact details. You can then use Pipedrive reporting or a connected BI tool to compare lead volume, opportunity conversion and Closed Won deals by source.

Field map and a worked example

A worked example shows how the fields should look. A visitor clicks a Google ad for a tax advisory service and submits a contact form. The captured values could be Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign and Channel Drilldown 3 = Tax Advisory Ad. The first landing page might be yourfirm.com/services/tax-advisory, with a landing page group of /services.

Use that structure as a checklist before launch: confirm every form has all six hidden fields, submit a test lead from a tagged link, check each field in Pipedrive, then submit a second test after navigating to a different page. If the second test retains the original channel, cross-page persistence is working.

Why categorised attribution beats raw UTM values alone

Raw UTM capture alone misses traffic that carries no UTM values. Categorising every visit also labels Organic Search, Organic Social, Direct and Referral leads, giving a complete picture instead of only paid clicks.

Browser storage also solves a common failure: a visitor lands on the homepage from an ad, browses to the contact page, and submits there. Without persistence, the original UTM values disappear on navigation. Storing attribution in the browser keeps the original source attached to the later submission.

Click IDs add another layer. Capturing GCLID, MSCLID and FBCLID with the form submission lets you return those identifiers to Google, Microsoft or Meta when the lead becomes a paying customer. That is offline conversion tracking, and it gives smart bidding systems customer and revenue signals instead of only form or thank-you-page events.

Landing page and landing page group data complete the picture. If a blog post leads to a form submission, you can see which article, service section or page group generated the lead.

Four reports to build once the data is in Pipedrive

Leads by Channel shows monthly lead volume per channel, making it easier to spot when organic search quietly outperforms the channels receiving most of the budget.

Leads by Meta Ads Network separates Facebook, Instagram and Messenger performance, so spend can shift toward the network actually producing leads.

Customers by Google Ads Campaign compares campaigns by paying customers rather than clicks, which is useful when brand, competitor and product-term searches convert at different rates.

Revenue by Keyword requires the keyword to be included in the UTM parameters, for example through a Google Ads tracking template. Revenue by keyword then informs bidding, SEO topic choices and ad copy wording.

Illustrative example: connecting campaigns to bookings and revenue

Consider a hypothetical events business that runs Google and Facebook campaigns. Its analytics can show how many visitors each campaign sends, but it cannot connect those campaigns to actual bookings. If the business captured attribution on its booking form and passed it into the CRM alongside contact details, the team could compare leads, bookings, revenue and return on investment by campaign. Referral traffic from venue websites might also emerge as a meaningful booking source, a pattern that paid-only UTM capture would miss entirely. That is the decision value of the setup: once source data sits beside the lead record, budget can follow bookings and revenue rather than visitor counts alone. Before relying on any trial offer or setup-time claim, check the current terms directly with the provider.

Frequently asked questions

Why categorise channels instead of storing raw UTM values alone?

Raw UTM values only arrive when a paid link carries them. A categorised channel model can also label visits from Organic Search, Organic Social, Direct and Referral, so every form submission carries a source label rather than only ad clicks.

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

Storing the attribution in the browser preserves the original source when the visitor browses to another page before submitting. That prevents loss when the first landing page is not the form page.

How do click IDs help after a lead enters Pipedrive?

Capture identifiers such as GCLID, MSCLID and FBCLID with the submission, keep them in Pipedrive, and return them to the relevant platform when the lead becomes a customer. That supports offline conversion tracking based on customers and revenue rather than only form completions.