Pipedrive Reporting Dashboard: Examples, Limits and ROI

Every Pipedrive dashboard is made of reports, and every report starts from one of these types. Knowing the list saves an afternoon of looking for a report that does not exist.

Notice what is not on the list: no report type for ad spend, cost per lead, return on ad spend or customer acquisition cost. That is not an oversight in the menu. Pipedrive simply holds no cost data to report on.

This is the one report that comes closest to a marketing answer, and it is worth setting up properly.

• Win/loss conversion, viewed by source channelPipedrive's deal conversion documentation lists source channel among the fields a win/loss conversion report can be viewed by. The result is a win rate per channel: of the deals that closed either way, how many were won.
• Source channel is an admin defined listThe values are a multiple options list your admin edits under Company Settings. Pipedrive warns that renaming a default option may lead to confusion, because the ID behind it stays the same, so add new options rather than repurposing old ones.
• Source origin says how, not whySource origin is set by Pipedrive and records how the deal was created: Web forms, Chatbot, Import, API, Web visitors. It is accurate and useful, but a web form is a door, not a campaign.

Each of these uses only report types and groupings Pipedrive documents. Put them on one dashboard called Marketing and you have the most a CRM without spend can tell you.

• 1. Win rate by source channelA deal conversion report, win/loss, viewed by source channel, for deals closed in the last two quarters. Use a long range: a few deals per channel per month makes any rate noisy.
• 2. Pipeline funnel by stageThe funnel conversion report across your pipeline stages. Add a filter on source channel, one channel at a time, to see where its deals stall, for example paid leads dropping between qualified and proposal.
• 3. Lead to deal conversionA lead conversion report over time. If marketing hands leads to sales as Pipedrive leads, this is the honest measure of handover quality, and a falling line is the early warning before the deal numbers move.
• 4. Sales cycle lengthA deal duration report on won deals. Knowing the median days from created to won tells you how long to wait before judging a campaign, which is the question most budget arguments skip.
• 5. Won value by campaignA deal performance report on won value, grouped by a campaign custom field. This needs Premium or higher, and it needs something to fill that field reliably at creation, because a field nobody fills reports as one large empty row.

If you run the Campaigns add-on, its performance report belongs on the dashboard too, labelled clearly: its conversion rates are email opens and clicks, not deals.

Every marketing efficiency metric is a ratio with spend on one side. Pipedrive holds the other side very well.

1. No spend, so no ROI, ROAS or CAC. Insights has no cost report and no way to import one. Any ROI figure on a Pipedrive dashboard was typed in by somebody.
2. The source is a label, not a measurement. Source channel is picked by a person or set by an automation, from a list your admin edits. Two reps can file the same lead differently, and nobody can check which was right.
3. The campaign is usually missing. Pipedrive has no default UTM or click ID fields, and its Web Forms documentation says nothing about carrying URL parameters, so without an app the deal knows the channel at best and never the campaign or the ad.
4. The first touch never reached the CRM. Everything Pipedrive records starts when the record is created. The ad click three weeks before the form, the organic visit, the AI answer that sent them: none of that exists in Pipedrive to group by.
5. Campaign conversion is email conversion. The report named Campaign conversion measures opens, clicks, deliverability and unsubscribes. Read it as a sales conversion and email looks better than it is.
6. Custom fields in reports need Premium. On Lite and Growth the visual builder cannot use deal custom fields, so even a well filled campaign field cannot be grouped by.

ROI exists the moment spend and won revenue are joined on the same key, and the only key that works is the campaign the deal came from. There are three ways teams get there.

• The monthly spreadsheet

  Export won deals by source channel, export spend from each ad account, divide. It works at channel level, takes an afternoon every month, and breaks as soon as anybody asks about a campaign.

• Fields from a marketplace app

  GA Connector and similar apps write UTMs, first and last click and GCLID into Pipedrive fields. That fills the campaign side; the spend still has to be joined somewhere else.

• A tool that holds both

  An attribution tool that records the click, writes the campaign onto the deal and pulls spend from the ad platforms can compute ROI per campaign without a spreadsheet in the middle.

Before building any of the dashboards above, four numbers tell you which ones will be worth reading.

1. The empty channel share. Deals created in the last 90 days with no source channel. Every one of them is invisible to dashboard one.
2. The campaign share. Of the same deals, how many carry a campaign in any field. That is the ceiling on dashboard five.
3. The origin mix. Deals by source origin. A high share of Manually created, Import or API means a person or a system chose the channel, not a click.
4. The plan check. If you are on Lite or Growth, any report on a custom field is off the table until you move to Premium.

The Pipedrive integration is native: a one click sign in and a field mapping screen, live in about 21 minutes, no developer. It writes source, campaign, ad, click ID, UTMs, landing page and a link to the 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. Stage changes and won deals are read as they happen.

On the website, 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 gclid, gbraid, wbraid, fbclid, li_fat_id and msclkid at the click. The anonymous history is joined to the person at the form fill, the call or the booking, with no attribution window on the journey.

Spend is pulled from the ad platforms and joined to the deals, so ROI, ROAS and cost per won deal are computed per campaign under five attribution models. Won deals go back to Meta and LinkedIn through their Conversions APIs, to Google Ads as an offline conversion on gclid and to Microsoft Ads on msclkid, with the deal value.

The limits: tracking respects consent decisions, so a visitor who declines is not measured, and a lead that never touched your website still needs a source typed in by a person.

The rest of the cluster: Pipedrive lead source tracking, UTM parameters in Pipedrive and Pipedrive and Google Analytics. For the metrics, the glossary entries on return on ad spend and customer acquisition cost, and the ROAS calculator. For tools, attribution tools that work with Pipedrive and the best marketing dashboard tools.