This page provides you with instructions on how to extract data from Pipedrive and analyze it in Google Data Studio. (If the mechanics of extracting data from Pipedrive seem too complex or difficult to maintain, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)
What is Pipedrive?
Pipedrive is a CRM and sales pipeline platform designed to help small teams manage long sales processes. Organizations can set goals, plan activities, and monitor deals. Pipedrive also offers reporting tools to monitor individual and team targets and analyze sales data.
Getting data out of Pipedrive
Pipedrive provides a RESTful API that lets developers get at organization, people, message, and other information stored in the platform. For example, to get information about an organization using the Pipedrive API, you would call
Preparing Pipedrive data
If you don't already have a data structure in which to store the data you retrieve, you'll have to create a schema for your data tables. Then, for each value in the response, you'll need to identify a predefined datatype (INTEGER, DATETIME, etc.) and build a table that can receive them. Pipedrive's documentation should tell you what fields are provided by each endpoint, along with their corresponding datatypes.
Complicating things is the fact that the records retrieved from the source may not always be "flat" – some of the objects may actually be lists. In these cases you'll likely have to create additional tables to capture the unpredictable cardinality in each record.
Keeping Pipedrive data up to date
At this point you've coded up a script or written a program to get the data you want and successfully moved it into your data warehouse. But how will you load new or updated data? It's not a good idea to replicate all of your data each time you have updated records. That process would be painfully slow and resource-intensive.
The key is to build your script in such a way that it can identify incremental updates to your data. You may be able to use DATETIME fields to identify records that are new since your last update (or since the newest record you've copied). Once you've take new data into account, you can set your script up as a cron job or continuous loop to keep pulling down new data as it appears.
From Pipedrive to your data warehouse: An easier solution
As mentioned earlier, the best practice for analyzing Pipedrive data in Google Data Studio is to store that data inside a data warehousing platform alongside data from your other databases and third-party sources. You can find instructions for doing these extractions for leading warehouses on our sister sites Pipedrive to Redshift, Pipedrive to BigQuery, Pipedrive to Azure SQL Data Warehouse, Pipedrive to PostgreSQL, Pipedrive to Panoply, and Pipedrive to Snowflake.
Easier yet, however, is using a solution that does all that work for you. Products like Stitch were built to move data from Pipedrive to Google Data Studio automatically. With just a few clicks, Stitch starts extracting your Pipedrive data via the API, structuring it in a way that is optimized for analysis, and inserting that data into a data warehouse that can be easily accessed and analyzed by Google Data Studio.