Pipedrive Website Tracking: The Web Visitors Add-on and Beyond

Web Visitors is genuinely useful for the job it was built for, which is account based prospecting: a list of companies showing interest, before any of them fills in a form.

• Companies, not people

  A tracking script on your site reports which organisations visited. Pipedrive says plainly that it is powered by Leadfeeder. Contact persons at those companies come from Prospector credits, not from the visit.

• Filters worth having

  Visitors can be filtered by country, by Google AdWords campaign and by pages visited, so a sales rep can see which accounts read the pricing page this week.

• One click to a record

  A visiting company can be turned into a lead, a deal or an organization. Its Source origin then reads Web visitors, which keeps those records apart from form leads in reports.

• Priced by companies identified

  The feature page lists €49 a month for up to 200 identified organizations, €99 for 201 to 500 and €299 for 501 to 2,000, with a 14-day trial. It is a paid add-on on every plan, not included in any.

The phrase website tracking covers two jobs that share a script tag and very little else.

• Who is looking: company identificationMatches a visit to an organisation from its network. Good for outbound and for spotting buying signals at accounts you already know. It cannot tell you which of the twelve people at that company read the page, and it says nothing about a visitor on a home connection.
• What this person did: visit trackingFollows one browser from visit to visit and joins its history to a contact once they identify themselves. This is what attribution needs, because the campaign that paid for the first click belongs to a person, and the deal belongs to that person too.

Web Visitors does the first. We could not find a Pipedrive feature of its own that does the second, which is why the marketplace filled the gap.

Outfunnel has been the best known answer to person level tracking for Pipedrive. Its script sets an anonymous cookie ID, identifies the visitor when they fill in a form or click a link in one of your emails, and writes their visits into the CRM as Activities or Tasks with the lead source, country, pages and session length. Its lead scoring adds web visits, email events, Pipedrive activities and custom fields together, and Outfunnel says it works on any Pipedrive plan, where Pipedrive's own Scores is Premium and higher and scores deals only.

On 5 August 2026 Pipedrive announced that it had acquired Outfunnel. The announcement says Outfunnel will keep operating during a transition period with no disruption to existing customers, and that Pipedrive plans to rebuild the platform's core capabilities natively over the coming months. It does not say which capabilities. Web tracking, lead scoring and engagement sync are all candidates, and none is named.

• GA Connector

  Its Google Analytics Connector app runs its own script and writes UTMs, first and last click, the GA4 client and session IDs and gclid into Pipedrive fields at the moment a lead is created. Source fields rather than a visit history.

• Your own script and the API

  Capture parameters and pages yourself, then write them through a form connector or the Pipedrive API into custom fields. Full control, and somebody has to keep it working. Our guide to Pipedrive UTM parameters walks through it.

• Google Analytics beside the CRM

  GA4 knows the sessions and Pipedrive knows the deals, and nothing native joins them. See Pipedrive and Google Analytics for what the join takes.

1. The ad click that started it. Company identification records that a company came, and visit tracking records what a known contact read. Neither puts the campaign, the ad and the click ID of the very first visit onto the person and the deal.
2. The visits before identification are thin. A cookie based script can only join visits that happened in the same browser, while the cookie lasted, and before anything blocked it. A buyer who researched on their phone and converted on a laptop shows up with half a history.
3. Activities are not attribution. A list of page views on a contact is useful to a salesperson and hard to report on: there is no credit per channel, no revenue by campaign, and no way to compare first click with last click.
4. No ad spend. Pipedrive Insights has no cost data, so even a perfect visit history cannot produce a cost per deal or a return on ad spend inside Pipedrive.
5. Nothing goes back to the ad platforms. Meta and Google keep optimising on whatever conversion their pixel saw, usually the form fill, because no part of this setup tells them which leads turned into revenue.

1. Is the goal prospecting or attribution? Prospecting wants companies; attribution wants people and campaigns. Many teams need both, and they are different purchases.
2. Do you need the first touch or only recent activity? A salesperson calling tomorrow wants the last three visits. A budget owner wants the click that started the journey months ago.
3. Where must the data live in Pipedrive? Activities on a contact are read by people; fields on the deal are read by reports. Decide which you need before choosing a tool.
4. What happens to ad clicks? Check whether the setup records gclid, fbclid and the other click IDs, and whether a won deal is ever sent back.
5. How is consent handled? Every option here places a script. Know what each one does when a visitor declines, and say it in your privacy policy.

LeadJourney is person level visit tracking built for attribution rather than for prospecting. One script on your site or in your GTM container records every visit server-side on your own domain, first-party, at 95%+ accuracy, and captures the click ID at the click: gclid with gbraid and wbraid, fbclid, li_fat_id and msclkid. The anonymous history is joined to the person at the form fill, the call or the booking, and there is no attribution window on the journey, so the ad clicked in spring is still attached when the deal closes in autumn.

The Pipedrive integration is native: a one click sign in and a field mapping screen, live in about 21 minutes with no developer. It writes the source, campaign, ad, click ID, UTMs, landing page and a link to the full journey onto the Person, and the attributed channel, campaign and credit onto the Deal, in dedicated LeadJourney custom fields that leave your existing source fields untouched. It reads stage changes and won deals as they happen.

Spend is pulled from the ad platforms and joined to the deals, so cost per deal and return on ad spend are real numbers. Won deals go back with their value: to Meta through the Conversions API, to Google Ads as an offline conversion import on gclid, to LinkedIn through its Conversions API and to Microsoft Ads on msclkid. Five attribution models run on the same events.

The limits: tracking respects consent, so a visitor who declines is not measured, and a lead who never touched your website still needs a source typed in by a person. It does not name anonymous companies, so if account identification is the job, Web Visitors and LeadJourney sit side by side.

The cluster starts at Pipedrive lead source tracking. For the parts that feed it, Pipedrive UTM parameters, Pipedrive and Google Ads and building a Pipedrive reporting dashboard. On the method, customer journey tracking, server-side tracking and the first-party data glossary entry. Comparing tools: the attribution tools that work with Pipedrive.