Track Affiliate Leads and Customers in Pipedrive
If you run an affiliate program, the question that matters is not only how much traffic affiliates send, but which affiliates produce leads, customers, and revenue. This guide explains a practical setup for carrying affiliate source data from a tagged link into Pipedrive, then turning that data into reports you can act on.
How the setup fits together
The workflow has four moving parts: a tagged affiliate link, hidden fields on your forms, a browser-side tool that writes the affiliate details into those fields, and a connection that sends the completed form submission to Pipedrive. Each part has a distinct job, and knowing which part failed makes troubleshooting much faster.
A useful way to think about it is as a relay. The UTM parameters travel with the visitor's first click. The hidden fields give that information somewhere to land when a form is submitted. The capture tool keeps the values available while the visitor browses. The CRM connection carries the finished record into Pipedrive. If affiliate data is missing at the end, check the relay in that order.
Step 1: Put UTM parameters on affiliate links
Start with the links you hand to affiliates. Add UTM parameters so the click carries a recognizable source, medium, and campaign value. A consistent structure is more important than a clever one, because the values you choose here become the labels you filter and group by later.
A recommended structure is:
- utm_medium = affiliates
- utm_source = the affiliate type, such as bloggers, podcasters, or YouTubers
- utm_campaign = the specific affiliate's name
For example, a link to a Pipedrive integration page could carry utm_medium=affiliates, utm_source=bloggers, and utm_campaign=john-smith. The exact destination is less important than keeping the naming pattern stable across every affiliate.
If building these links by hand becomes tedious, affiliate management platforms such as Trackdesk or Rewardful can insert UTM parameters automatically. A UTM builder with an affiliate template is another option for keeping the structure consistent.
Step 3: Let the capture tool fill the hidden fields
When a visitor arrives through a tagged affiliate link, the capture tool stores the UTM values in the browser. That persistence matters: the visitor can move between pages, or leave and return later, and the affiliate details are still available when they finally submit a form.
At submission, the tool writes the affiliate details into the hidden fields. This is the point where the link data becomes form data. If the hidden fields are present but empty, the likely issue is upstream: the link may be missing parameters, or the capture step may not be running on that page.
Step 4: Send the completed form data to Pipedrive
When the form is submitted, your form tool collects the hidden-field values along with the visitor's name and email address. From there, the record can reach Pipedrive through a direct integration offered by the form tool, or through a connection service such as Zapier or Make.
The important check is that the hidden fields are mapped to the corresponding Pipedrive fields. If the form submission contains the affiliate values but the Pipedrive record does not, the problem is usually in the field mapping rather than in the link or the form.
What affiliate data arrives in Pipedrive
The capture tool is built around UTM parameters, so whatever you put into those parameters is what can be carried into Pipedrive. With the recommended structure, a blogger affiliate named John Smith produces:
- Channel = Affiliates
- Channel Drilldown 1 = Bloggers
- Channel Drilldown 2 = John Smith
The same approach also captures non-affiliate sources. For an organic Google search, the values could be:
- Channel = Organic Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = the Google domain the visitor came from
- Channel Drilldown 3 = the search keyword, when it is available
That breadth is useful because it lets you compare affiliate performance with paid search, paid social, and other channels in the same reporting structure.
A field map for planning forms and reports
Use this checklist to connect each hidden field to the report it enables:
If a report needs a dimension that is not in this map, add the corresponding UTM parameter and hidden field before you start collecting data. Retrofitting a missing dimension later means the earlier records will not have it.
Three reports worth building
Once affiliate data is in Pipedrive, the reporting question becomes which view helps you make a decision.
Leads by Channel shows how many leads came from affiliates compared with other channels such as paid search or paid social. Use it to see whether the affiliate program is contributing meaningful volume or is being overshadowed by another channel.
Customers by Affiliate Type breaks new customers down by the kind of affiliate that generated them, such as bloggers, YouTubers, or podcasters. Use it to decide which affiliate profiles are worth recruiting more of.
Revenue by Affiliate shows how much new revenue each affiliate has generated. Use it to identify top performers, understand what they do differently, and decide where additional support would be most valuable.
Worked example: from a blogger link to a revenue report
Suppose a blogger named John Smith shares a link tagged with utm_medium=affiliates, utm_source=bloggers, and utm_campaign=john-smith. A visitor clicks the link, browses several pages, and later submits a quote request form.
At submission, the hidden fields carry Channel = Affiliates, Channel Drilldown 1 = Bloggers, and Channel Drilldown 2 = John Smith into the form record. When that record reaches Pipedrive, the same values appear on the deal or lead.
Now the reports can answer specific questions. Leads by Channel shows how many affiliate leads arrived alongside other channels. Customers by Affiliate Type shows whether bloggers or another affiliate type produced more customers. Revenue by Affiliate shows how much revenue John Smith's referrals generated. Because the same structure applies to non-affiliate channels, you can also compare John Smith's average deal size with customers from Google or Facebook ads.
Diagnosing missing affiliate data
When affiliate data does not appear in Pipedrive, the failure usually sits in one of four places. Check them in order:
- The link: confirm the affiliate link actually contains the UTM parameters. A link copied without them will not carry a source.
- The form: confirm the hidden fields exist on the form that was submitted, not only on a different form.
- The capture step: confirm the capture tool is active on the pages where visitors arrive and convert.
- The CRM connection: confirm the hidden fields are mapped to the intended Pipedrive fields.
This order matters because each step depends on the one before it. A mapping problem cannot be fixed by changing the link, and a missing parameter cannot be fixed by remapping fields.
Plan and trial details
Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.
| Hidden field | What it answers | Report it supports |
|---|---|---|
| Channel | Which broad source brought the lead? | Leads by Channel |
| Channel Drilldown 1 | Which affiliate type or search engine? | Customers by Affiliate Type |
| Channel Drilldown 2 | Which specific affiliate or domain? | Revenue by Affiliate |
| Channel Drilldown 3 | Which keyword, when available? | Keyword-level comparisons |
| Landing Page | Which page received the visit? | Page-level performance |
| Landing Page Group | Which page group received the visit? | Grouped page performance |
Frequently asked questions
Do I need a separate tracking tool if my affiliate platform already adds UTMs?
No. If your affiliate platform inserts UTM parameters automatically, that handles the link-tagging step. You still need a way to write those values into hidden form fields and carry them into Pipedrive, which is the capture and CRM-connection part of the workflow.
What is the difference between Channel and Channel Drilldown?
Channel is the broad source category, such as Affiliates or Organic Search. Channel Drilldown 1, 2, and 3 add increasing specificity, such as affiliate type, affiliate name, or keyword. The drilldown fields let you move from a channel-level view to an individual-affiliate view without changing the underlying record structure.
Can I compare affiliate customers with customers from Google or Facebook ads?
Yes, if both sources are captured through the same hidden-field structure. The Channel field separates Affiliates from Organic Search and paid channels, and the drilldown fields let you compare affiliate types or individual affiliates against those other sources.
Why does a lead show no affiliate source even though the link was tagged?
Check the relay in order: the link may have lost its parameters, the form may be missing hidden fields, the capture tool may not be active on the page, or the CRM mapping may be incomplete. Each step depends on the previous one, so fixing the earliest broken link in the chain is the fastest route.