How to get Google Analytics data into Pipedrive
If your CRM only stores a name and an email, you cannot tell which campaigns produced the deal. This guide shows how to attach Google Analytics-style channel and landing page information to each Pipedrive lead, so reports can show what generated leads, opportunities, customers and revenue.
Why channel and landing page data belong in the CRM
Google Analytics tells you how many sessions arrived from a channel. It does not tell you which of those sessions became a paying customer. Pipedrive knows the customer but not the journey that produced them. Joining the two views closes that gap.
Two pieces of information do most of the work:
- Channel — the route a visitor took to reach the site, such as Paid Search, Organic Search, Paid Social or Referral.
- Landing page — the first page the visitor saw, such as a features page, a blog post or an ebook page.
Once both are stored on the lead record, you can compare channels on lead volume, conversion rate and closed-won revenue, and you can see whether a content section such as the blog is pulling its weight.
How the capture mechanism works
A small script on the site inspects the same signals Google Analytics uses to classify a visit. It assigns the visitor to a channel and records the first landing page. That information is held in the visitor's browser cookie.
When the visitor submits a form, the script writes the values into hidden fields you have added to that form. The form submission then carries the channel and landing page data into Pipedrive alongside the name, email and phone number.
This means the CRM record is created with attribution already attached — no manual tagging after the fact and no matching of separate exports.
Four setup steps
Step 1 — Add the hidden fields to your lead forms. The six fields are listed in the field map below. Form builders that support a hidden field type let you drag one in; the linked help resources cover the step-by-step for common builders.
Step 2 — Let the script populate the fields. After the fields exist, the script fills them on each form submission based on how that visitor arrived.
Step 3 — Confirm the values reach Pipedrive. On submission, the channel and landing page values travel with the lead's name, email and phone into the CRM.
Step 4 — Build reports. Use Pipedrive's reporting or a separate analytics tool to group leads, opportunities and revenue by channel and landing page.
Field map: what each hidden field records
Use this checklist to confirm every field exists on every lead form before launch.
The exact spelling of each field matters: the script writes to the field name, so a typo such as a missing letter will leave the value blank in Pipedrive.
Worked example: a Paid Search visit
Suppose a company runs a brand campaign in Google Ads and a visitor clicks an ad, then fills in a form. Depending on the UTM parameters on that ad, the hidden fields would populate roughly like this:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand Campaign
- Channel Drilldown 3 = the brand name used in the ad
- Landing Page Group = /Features
- Landing Page = the specific features URL the visitor first saw
The lead arrives in Pipedrive with all six values attached. Later, when the deal closes, the revenue can be grouped by Channel Drilldown 2 to show how the brand campaign performed against other campaigns.
Three different failures and how to tell them apart
When attribution data is missing from Pipedrive, the cause is usually one of three things. Check them in this order.
- The field is missing or misspelled on the form. The lead arrives but the channel column is empty. Compare the field names on the form against the field map above.
- The visit had no usable UTM parameters. The field exists but the drilldown values are blank or generic. This is a tagging problem on the ad or link, not a form problem.
- The form does not pass hidden fields into Pipedrive. The field is present and populated on the page, but the CRM record shows nothing. This points to the form-to-CRM connection rather than the capture script.
Testing one submission per channel with a known UTM string is the quickest way to isolate which of the three is happening.
Four reports worth building
Each of these views should drive a specific decision, not just display a number.
- Leads by Channel. Read it as a spend-versus-supply check: if a channel that receives a large share of budget sits near the bottom of the monthly lead count, that mismatch is the conversation to have. The report is a starting signal, not proof of poor performance — pair it with conversion data before moving money.
- Opportunities by Google Ads campaign. Use it to rank campaigns by sales-accepted opportunities rather than raw clicks. A campaign that produces many leads but few opportunities is a candidate to pause or retarget; one that produces fewer but better-qualified opportunities earns more budget.
- Customers by Facebook Ads network. Facebook placements can appear across Facebook, Instagram, Messenger and WhatsApp. Compare closed customers per network to see whether one placement is carrying the account, then shift budget toward it.
- Revenue from Organic Search by search engine. Split SEO revenue by Google, Bing and DuckDuckGo, then set it beside Paid Search and Organic Social revenue to judge how much of total revenue SEO actually contributes before committing more to it.
Each report is only as good as the field values underneath it, so keep the field map checklist in the launch process for every new form.
Commercial terms
The following terms are placeholders for the site owner to confirm before publication:
- Trial length: {{OWNER_TRIAL_LENGTH}}
- Starting price and plan structure: {{OWNER_PRICING}}
- Support response commitments: {{OWNER_SUPPORT_TERMS}}
- Any guarantee or refund policy: {{OWNER_GUARANTEE_TERMS}}
No trial, price or guarantee should be published until these variables are filled with verified owner facts.
| Hidden field | What it records |
|---|---|
| Channel | The broad route, e.g. Paid Search, Organic Search, Paid Social, Referral |
| Channel Drilldown 1 | First level of detail within the channel, e.g. the network or source |
| Channel Drilldown 2 | Second level, e.g. the campaign |
| Channel Drilldown 3 | Third level, e.g. keyword, ad group or brand term |
| Landing Page | The first page the visitor saw, e.g. dropbox.com/features/cloud-storage |
| Landing Page Group | The category of that page, e.g. /Features or Blog |
Frequently asked questions
Does this replace Google Analytics?
No. Google Analytics remains the place to analyse sessions and behaviour. The capture mechanism adds a per-lead record of channel and first landing page inside Pipedrive, so CRM outcomes can be grouped by those dimensions.
Which form builders can carry the hidden fields?
Any builder that supports a hidden field type can carry them. Gravity Forms and Jotform are two examples where a hidden field can be dragged into the form; the linked help resources cover the step-by-step for common builders.
What happens if a visitor arrives without UTM parameters?
The channel may still be classified from referrer or other signals, but the drilldown values will be less specific. Blank drilldowns usually indicate a tagging gap on the link or ad rather than a problem with the form.
Can I report on revenue, not just lead counts?
Yes. Because the channel and landing page values sit on the lead record, closed-won revenue can be grouped by channel, campaign or landing page group in Pipedrive reporting or in a separate analytics tool.