Replay Webinar : The stats inside Pipedrive

The stats inside Pipedrive: how to build useful insights from clean CRM data

The webinar focuses on one central idea: statistics are only valuable if the CRM setup behind them is solid. The speakers explain that many companies ask for dashboards or reports without first knowing why they need them or how they will use them. As a result, they often end up with graphs that look useful but do not support real decisions.

Before creating any report in Pipedrive, it is important to define the objective behind the data. A business should know what it wants to measure, why it matters, and how the result will help improve the sales process.

Why statistics are only as good as your setup

A major theme throughout the webinar is that Insights cannot fix a messy CRM. If deals are not updated properly, if custom fields are poorly structured, or if users are not following a clear process, then the reports generated in Pipedrive will be incomplete or misleading.

The speakers insist on a few basic principles:

• The database must be clean.
• Deals must be updated with the correct status and dates.
• Users must work consistently.
• Custom fields must be created in the right format.
• Data must be stored in the right object, such as deals, people, or organizations.

Without these foundations, it becomes difficult to trust the numbers shown in dashboards and reports.

Understanding Pipedrive logic before building reports

Pipedrive reports are based on conditions and logic rules. To build useful insights, users need to understand how Pipedrive structures data and how filters behave.

For example, when building a report, it is essential to know:

• whether a field is a text field, single option field, or multiple option field;
• whether the data belongs to a deal, an organization, a person, or an activity;
• whether the report should include all pipelines or only selected ones;
• whether the relevant date is the creation date, won date, lost date, due date, or marked-as-done date.

The speakers explain that many reporting issues come from a misunderstanding of these basic points rather than from a technical limitation in the tool.

Structuring pipelines, stages, and lost reasons

The webinar highlights how much reporting depends on the way pipelines and stages are organized.

Pipedrive allows users to analyze deals by stage, including where deals are won or lost. This can help identify weaknesses in the sales cycle. For example, if many deals are lost at the demo stage, it may suggest that the sales team is not communicating enough value. If many deals are lost in negotiation, pricing or budget may be the issue.

Why lost reasons matter

Lost reasons are especially important because they provide context behind the numbers. Rather than simply marking a deal as lost, the team should choose a structured reason from a defined list.

Examples mentioned include:

• the deal is too expensive;
• the project is delayed;
• the client is not engaging;
• the budget was not approved.

The speakers recommend limiting free-form inputs as much as possible so reporting stays consistent. Optional notes can still be added for extra detail, but the main lost reason should remain standardized.

This makes it easier to identify patterns later and improve the sales process.

Choosing the right custom fields

Custom fields have a direct impact on reporting quality. The webinar explains that when importing data from Excel or another CRM, it is not enough to move the information over. Users also need to decide what kind of field each column should become inside Pipedrive.

Situation	Better choice in Pipedrive	Why it matters
Free descriptive content	Text field	Useful for flexible notes, but harder to report on
A fixed list of categories	Single option field	Easier to filter and analyze consistently
Multiple tags on the same item	Multiple option field	Useful, but reporting conditions differ

The speakers also remind users to place fields in the correct object. A field related to a company should not necessarily live on a deal, and vice versa.

The three main areas inside Pipedrive Insights

Pipedrive Insights is presented as three separate but connected areas:

Dashboards

Dashboards are visual spaces where reports are grouped together. Depending on the Pipedrive plan, users can create one or multiple dashboards.

Dashboards are useful for reviewing several KPIs at once, especially during team meetings or management reviews.

Goals

Goals allow users to track targets for themselves or for a team. These targets can be based on deals, activities, or forecasted revenue.

They can be measured:

• weekly,
• monthly,
• quarterly,
• yearly.

Goals can also be defined as a count or a value.

Reports

Reports are the building blocks of dashboards. They can be created for different types of data such as deals, activities, leads, people, organizations, campaigns, products, or revenue forecasts.

The speakers explain that reports can also be organized into folders to keep Insights structured and easier to navigate.

Reports and dashboards are private by default

One important practical point is that reports and dashboards are personal by default.

If one user creates a dashboard, other users will not automatically see it. It must be shared manually. This is an important detail because teams often assume that reports are visible across the whole account.

The webinar also points out another limitation: reports cannot simply be transferred from one user to another. If the wrong user creates them, they may need to be recreated.

This means companies should think in advance about who should own reporting assets in the CRM.

Building reports: activities, campaigns, deals, and more

The session includes several examples of how reports can be created.

Activity reports

An activity report can measure how many activities of a certain type were created or completed during a period. For example, a team might want to measure the number of calls marked as done this month.

A useful report may include conditions such as:

• activity type is “call”;
• linked deal is not empty;
• marked-as-done date is within a selected period.

This allows teams to separate prospecting calls from deal-related calls and get a more accurate view of performance.

Campaign reports

If campaigns are enabled in Pipedrive, users can build reports on performance and conversion. The exact options depend on the plan tier.

The webinar shows that campaign reports can include metrics such as:

• open rate,
• click rate,
• unsubscribe rate.

The standard campaigns plan gives fewer options, while the premium version unlocks more reporting possibilities.

Deal reports

Deal reports provide the most flexibility. Users can build reports based on won deals, lost deals, forecasted revenue, products linked to deals, or deal performance across pipelines and stages.

This is where understanding date logic becomes critical.

Why date filters are essential 📅

One of the strongest recommendations from the webinar is to always include a date filter, especially for deals and activities.

Without a date condition, the data is often too broad to analyze meaningfully. Date filters help compare performance over time and make dashboards more useful during meetings.

Relevant date fields may include:

• creation date,
• due date,
• marked-as-done date,
• won time,
• lost time,
• expected close date.

The speakers also explain that dashboard-level filters can override report dates temporarily. This is very useful because one dashboard can be viewed for this month, this quarter, or this year without rebuilding each report.

In the same way, dashboard filters can be used to view data by user, which avoids creating separate reports for every salesperson.

Organizing reports with folders and naming conventions

The webinar encourages users to keep their Insights area clean and organized. Reports can be grouped into folders, for example by region, department, or use case.

Examples of organization ideas include:

• sales by region,
• marketing campaigns,
• shared reports,
• personal reports.

The speakers also mention that naming conventions, numbers, and even a few emojis can help identify reports quickly. The goal is not decoration, but faster navigation and better structure.

Goals and forecast tracking 🎯

Goals are presented as a simple but useful way to track business targets.

A goal can be created for:

• deals won,
• activities completed,
• forecasted revenue.

Users can set goals for themselves, for all users, or for teams depending on their plan.

The webinar also shows how forecast goals can be connected to open deals with expected close dates. This helps teams compare:

• what has already been won;
• what is expected to close;
• how that compares to the target line over time.

This makes goals especially useful for sales planning and visibility.

AI-generated reports: useful, but not perfect

The webinar ends with a look at Pipedrive’s AI report generation feature.

The speakers see potential in it, but they also note that it works best when prompts are specific, structured, and aligned with Pipedrive’s own data logic.

For example, a good prompt should clearly state:

• what object is being analyzed;
• what status is needed;
• what time period should apply;
• whether results should be segmented;
• which chart format is preferred.

However, AI can still make mistakes, especially with date logic. One example shown is the difference between using a fixed custom period and using a dynamic condition such as “last year.” A fixed period may work today but become outdated later, while a dynamic filter updates automatically over time.

The speakers therefore recommend reviewing AI-generated reports carefully rather than trusting them blindly.

A key warning about date logic in AI reports

A particularly important point is the distinction between different deal dates.

For example, there is a big difference between:

• deals created last year;
• deals won last year.

A deal may have been created in one year and won in another. If users apply the wrong date condition, they may get misleading results.

This is one of the clearest examples in the webinar of why understanding Pipedrive’s structure matters more than simply generating a chart.

Exports and further analysis

Although not demonstrated in depth, the webinar also mentions that reports can be exported to formats such as PDF or Excel. This is helpful when teams want to:

• share results externally,
• archive reporting,
• perform deeper analysis in another tool,
• combine Pipedrive data with other data sources.

Final takeaway

The main lesson from the webinar is clear: Pipedrive Insights is powerful when the CRM is configured properly. Dashboards, goals, and reports can give valuable visibility into sales and marketing performance, but only if the underlying data is clean, structured, and used consistently.

The real work starts before reporting. It starts with setting up the CRM properly, choosing the right fields, defining the right processes, and making sure users understand how data should be entered.