Track leads and customers from SEO in Pipedrive
Organic search traffic is easy to count and hard to value. A visitor arriving from Google tells you little until you know whether that person became a lead, whether the lead became a customer, and which page brought them in. This guide shows a practical setup for carrying organic search context into Pipedrive so those questions have answers.
Four steps to connect organic search data to Pipedrive
The setup has four moving parts: a tracking snippet on your site, hidden fields on your lead forms, a form builder that captures those fields, and a route into Pipedrive. Each part has a job, and a break in any one of them shows up as blank or misleading data later.
Step 1 — Install the tracking snippet and add hidden fields. The snippet runs on your website and receives a small set of hidden fields on each lead capture form. The fields are: Channel, Channel Drilldown 1, Channel Drilldown 2, and Channel Drilldown 3. Most form builders let you add a hidden field type by drag-and-drop or by hiding a standard field in the settings.
Step 2 — Let the snippet classify the visit. When someone lands on your site, the snippet inspects referral information in the same spirit as web analytics tools. It sorts the visit into a channel such as Organic Search, Paid Search or Paid Social, and keeps that classification in the visitor's browser.
Step 3 — Capture the data at form submission. When the visitor completes a form, the snippet writes the channel details into the hidden fields. The form builder then stores those values alongside the lead's name, email and other answers.
Step 4 — Send the record to Pipedrive. The completed form can reach Pipedrive through a native integration offered by the form builder, or through a connector such as Zapier. Once the record is in Pipedrive, reporting can begin.
What each hidden field records
The four hidden fields are not interchangeable. Channel is the broad category. The three drilldowns narrow it down in sequence. A useful way to check your setup is to confirm that a single test lead shows a value in Channel and at least one drilldown before you trust any report.
Landing page data is captured separately. Landing Page holds the full URL, and Landing Page Group holds the section of the site, such as /blog. Together they show which content attracted the lead, not just which channel delivered it.
A worked example: one organic lead from an accounting firm
Imagine an accounting firm in Sydney publishes a blog post about choosing an accountant. A reader finds it through a Google search and submits a contact form.
The lead record would carry Channel = Organic Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = google.com, and Channel Drilldown 3 = accounting firm in Sydney when the search term is available. The landing page would be recorded as the blog post URL, and the landing page group as /blog.
One correction is worth flagging for anyone comparing this walkthrough with the original write-up: the source example labelled this organic Google visit as Channel = Paid Search, which contradicts its own description of the visit and its channel definitions. The value shown here is Organic Search, because that is what the scenario describes. If your own test lead shows Paid Search for a plain Google search click, treat it as a tracking fault to investigate rather than a valid result.
That single record answers two different questions at once. The channel fields explain how the person arrived. The landing page fields explain which piece of content did the work. When the same pattern repeats across many leads, the firm can see whether blog content or service pages are producing enquiries.
Three reports worth building once the data is flowing
Pipedrive's built-in reporting can handle the basics. If you need more advanced charts, tools such as Tableau, Looker Studio or Microsoft Power BI can connect to Pipedrive.
Leads by Channel. This report counts new leads each month and splits them by channel. It gives a high-level view of whether organic search is producing more leads over time, and it allows a direct comparison with paid search. If organic search is consistently outperforming paid search, that is a signal worth discussing when budgets are reviewed.
Customers from Organic Search by Landing Page Group. This report counts new customers each month, limited to organic search, and groups them by landing page group such as Home, Blog or Services. It shows which sections of the site attract people who actually buy.
Revenue from Organic Search by Landing Page. This report shows new customers and revenue for each piece of content. It is the closest view of which pages earn their keep, and it supports decisions about what to publish next.
A pre-launch checklist for trustworthy SEO reporting
Before relying on any of the reports above, confirm the following:
- A test lead submitted through each lead form shows a value in Channel and at least one drilldown.
- The landing page URL and landing page group are populated on the same test lead.
- The form-to-Pipedrive route (native integration or connector) maps every hidden field to a Pipedrive field, not just the name and email.
- Deal value is recorded on closed-won deals, otherwise revenue reports will understate results.
- Reports are filtered to Organic Search so paid and social traffic do not dilute the picture.
A blank Channel usually means the snippet is not firing or the hidden fields are missing from the form. A populated Channel with missing revenue usually means deal values are not being entered, which is a sales-process issue rather than a tracking issue.
Native integration or connector: how to choose
Some form builders connect to Pipedrive directly. Others need a connector such as Zapier. The choice affects setup effort and the number of fields you can map, so check two things before committing: whether every hidden field can be mapped to a Pipedrive field, and whether the connection preserves the field values exactly as submitted. A connector that drops the drilldown fields will leave you with channel-level reporting only.
| Hidden field | What it holds | Example from an organic Google visit |
|---|---|---|
| Channel | Broad traffic category | Organic Search |
| Channel Drilldown 1 | Source or platform | |
| Channel Drilldown 2 | Domain the visitor came from | google.com (or google.com.au, google.co.uk) |
| Channel Drilldown 3 | Search term, when available | accounting firm in Sydney |
Frequently asked questions
What is the difference between Channel and Channel Drilldown?
Channel is the broad category, such as Organic Search or Paid Search. The three drilldowns narrow it down in order: the platform, the domain, and the search term when it is available.
Why is the search term sometimes missing?
Search engines do not always pass the query through. When the keyword is unavailable, Channel Drilldown 3 will be blank even though the rest of the channel data is present.
Can I use Pipedrive's own reports, or do I need a separate BI tool?
Pipedrive's built-in reporting covers the three reports described here. Tableau, Looker Studio and Microsoft Power BI are options if you want more advanced charts or dashboards.
How do I know the tracking is working?
Submit a test lead through each form and check that Channel, at least one drilldown, Landing Page and Landing Page Group all appear on the resulting Pipedrive record.