Pipedrive CRM
Dashboard and Reporting Software

Databox enables you to use custom Pipedrive Filters, which are set within your Pipedrive CRM account, within the Metric Builders for Pipedrive CRM. Learn more about Metric Builders for Pipedrive CRM here.

Pipedrive Filters are only accessible from within the object where they were created in the Pipedrive CRM Account. This means Filters created in the Deals object will only be visible in the Metric Builder for Pipedrive CRM (Deals), Filters created in the Organizations object will only be visible in the Metric Builder for Pipedrive CRM (Organizations), etc.

If a Pipedrive Filter is set to Shared in the Pipedrive CRM Account, it will be available in Databox. If a Pipedrive Filter is set to Private in the Pipedrive CRM Account, it will only be visible in Databox if the user who created the private Pipedrive Filter is the same as the user who connected the Pipedrive CRM Account to Databox.

When creating Custom metrics in Pipedrive Metric Builder, you can choose from predefined dimensions (such as Deal Owner, Pipeline, Status, etc.) and custom fields unique to your Pipedrive account. The custom fields that can be used in Metric Builder depend on their data type. Only the following custom field types are supported:

• Text
• User
• Varchar
• Stage
• Pipeline

If your custom field uses any other data type, it will not appear in the dimensions drop-down list. To make a custom field available in the Metric Builder, change its data type in Pipedrive to one of the supported types.

Inverted Pipedrive CRM metrics (metrics where a low value indicates positive development and a high value indicates negative development) are:

• Deals Lost
• Deals Lost by Deal Owner
• Deals Lost by Deal Creator
• Deals Lost by Reason

When a Pipedrive CRM metric is first used in Databox, 36 months of historical data is initially synced for the metric.

Certain metrics may have more or less historical data available. For more information about the amount of historical data available for a specific metric, please contact our Support Team at help@databox.com.

All Pipedrive metrics attributed by dimension (such as Deals by Pipeline) are aggregatable. This means that if there are two pipelines with the same name in the connected Pipedrive account, their values will be aggregated. The values for both pipelines will be summed up and displayed as a single pipeline/dimension.

Currently there is no way to retroactively update data for Pipedrive metrics when values are changed in the Pipedrive account after the relevant metric was already created and started syncing in Databox. Changes in Pipedrive include actions like deleting or moving a deal, changing deal status or pipeline or altering the deal amount. So if such changes are made to existing data for past dates in Pipedrive, you might notice discrepancies in Databox metrics, which will not accurately reflect the current Pipedrive data.

This behaviour arises from the fact that all Pipedrive metrics are Event type metrics. For these metrics, updates to existing data are not visible in the API response, which prevents Databox from picking up on such changes.

A potential workaround to ensure your metrics reflect the most up-to-date values is to manually purge data in Databox:

• For Custom Metrics – If the discrepancy affects a Custom metric, purge the individual metric in Databox under Metrics > Custom Metrics > drop down menu for the given Custom metric > Purge Data.
• For Basic metrics – If the discrepancy affects a basic metric, the entire Data Source will need to be purged in Account Management app > Data Manager > drop down menu for the given Data Source > Purge historical data. Please note that this command will purge all synced data for all metrics for the selected Pipedrive Data Source

NOTE: Purge will remove all previously synced data for the system, so keep in mind that this can lead to loss of historical data.

Please note that you will need to perform a purge each time data is changed in Pipedrive to keep your metrics accurate.

If the connected Pipedrive account contains a large volume of deals and activity-related data, requests to fetch this data may time out before returning a preview. While you will still be able to save the Custom metric that is being created, the actual fetching of the data might take a while.

To reduce the fetching time, we recommend using Pipedrive filters to obtain data via Metric Builder. This approach significantly reduces the number of API calls, resulting in faster response times compared to creating the same filter directly in Metric Builder.

Here are two methods to consider:

• Set up filters in your Pipedrive CRM account based on the metrics you want to report on in Databox. When building Custom metrics in Metric Builder, select the Pipedrive filter from the Pipedrive filter dropdown. If the data fetching time is still long, further split the data using additional Pipedrive filters within your Pipedrive CRM account and apply these to Custom metrics. You can also combine multiple metrics if necessary using the Data Calculations feature in Databox.
• Set up a dummy Pipedrive filter within your Pipedrive CRM account that severely restricts the amount of data for deals or activities. Create a Custom metric in Databox using this filter. Once the Custom metric is saved in Metric Builder, modify the Pipedrive filter in your Pipedrive CRM account to sync the data you want to report on. The requested data should automatically sync with Databox during the next scheduled sync.