Store Leads
Pipedrive Integration
Contents
- Overview
- Enabling the Integration
- Disabling the Integration
- Configuring the Integration
- Organization Enrichment
- Organization Field Mappings
- Calculated Values for Organizations
- Manual Creation
- Manual Enrichment
- Bulk Creation
- Automatic Enrichment
- Automatic Organization Creation
- Person Enrichment
- Using Pipedrive Data within Store Leads
- Best Practices
- Information Security Considerations
Overview
Pipedrive lets you track your sales pipeline, optimize leads, manage deals with AI and automate your entire sales process so you can focus on selling. customer relationship management platform.
With the Pipedrive integration enabled, accounts on all paid plans can manually create new Pipedrive organizations from Store Leads domains. Existing Pipedrive organizations can also be manually updated.
Accounts on the Pro, Elite or Enterprise plans can also:
- Update all existing Pipedrive organizations and people with the latest Store Leads data. This can be configured to happen automatically as soon as we refresh our data (weekly) or triggered manually.
- Automatically update Pipedrive organizations and people when they are manually created or modified within Pipedrive.
- Automatically create new Pipedrive organizations for any new stores on a list.
- Automatically create new Pipedrive people from the non-personal email addresses in the Store Leads database.
Enabling the Pipedrive Integration
-
To enable the Pipedrive integration, visit the Integrations page in the Dashboard and click on Pipedrive.
Pipedrive Integration Summary. -
You'll see a page that summarizes the Pipedrive integration. Click the enable button to proceed.
Enable Pipedrive Integration. -
At this point, you may be asked to login to your Pipedrive instance. You'll also be asked for permission to allow Store Leads to manage data in your Pipedrive instance. You must approve this request in order to use the Pipedrive integration.
Once you approve the request, your Pipedrive integration will be enabled. As soon as the integration is enabled, we scan your Pipedrive instance to determine the overlap between organizations in Pipedrive and domains in the Store Leads database.
Connecting to Pipedrive with Individual Accounts
When the Pipedrive integration is enabled by the Store Leads account owner, it establishes an "Organization Connection" to Pipedrive. This means that:
- All automated actions that Store Leads performs in Pipedrive will be done using the Pipedrive credential supplied when establishing the organization connection.
- If you have shared access to your Store Leads account with other users, then any manual actions performed by those users will also default to using the Pipedrive credentials of the organization connection. To fix this, each Store Leads user can also connect to Pipedrive using their own Pipedrive account credentials. Doing so ensures that accounts created manually by a user are attributed to the right person in Pipedrive. Each account should visit the Integrations page, click on the "Pipedrive" link and then click on the "Connect to Pipedrive" button.
Disabling the Pipedrive Integration
If you wish to deactivate the integration, simply click the disable button.
Configuring the Pipedrive Integration
After the integration is enabled, choose which objects within Pipedrive should be enriched. By default, we will enrich your Organization records but not your Person records. To enable Person enrichment, click on the Person table and enable the Enrich People checkbox.
Next, review the available configuration options under the General tab.
- Create separate Pipedrive organizations for each of the merchant's subdomains. If there are 3 domains for a single merchant (www.merchant.com, uk.merchant.com and merchant.ca), all 3 will be created as separate Pipedrive organizations if this option is enabled. If this setting is disabled, only a single organization (with the highest ranked domain) will be created in Pipedrive.
- Assign owner when manually creating organizations or people in Pipedrive.. By default, an owner is assigned to newly created Pipedrive records when manually created through our website. Disable if an owner should not be assigned.
- Assign owner when automatically creating organizations or people in Pipedrive through workflows.. By default, an owner is assigned to newly created Pipedrive records when automatically created through workflows. Disable if an owner should not be assigned.
- Send Daily Integration Error Email. Enable this option to receive a daily email of any errors that occurred when trying to enrich records.
Organization Enrichment
By default, Store Leads will automatically enrich Pipedrive organizations every week when we publish our weekly data update. Pipedrive organizations are also enriched as soon as they are created or changed. Pipedrive organizations are only enriched if they have a Website Field that matches a store in our database that your plan can access.
Pipedrive Organization Fields
By default, Store Leads data will be set in the following organization fields.
- A list of alternate domain names for the store's ecommerce website.
- Suggested field type: Large text
- The id of the store's Android app (if any).
- Suggested field type: Text (max length 255)
- The url of the store's Android app (if any).
- Suggested field type: Text (max length 255)
- The average price of products sold in the store's ecommerce website. Values in the major unit of the store's currency (e.g., dollars of USD).
- Suggested field type: Monetary
- The average weight of products sold in the store's ecommerce website (in grams).
- Suggested field type: Numerical
- The url of the store's brands page (if any).
- Suggested field type: Text (max length 255)
- A list of the store's ecommerce website categories. Categories represent the store's industry vertical (e.g., "/Apparel" or "/Beauty & Fitness/Face & Body Care")
- Suggested field type: Large text
- A list of the store's ecommerce website top-level categories. Categories represent the store's industry vertical (e.g., "/Apparel" or "/Beauty & Fitness")
- Suggested field type: Large text
- The city of the merchant (if known)
- Suggested field type: Text (max length 255)
- For merchants that have multiple domains (e.g., merchant.com, merchant.co.uk and merchant.com.au), cluster_domains contains a list Domain names that are in the same cluster.
- Suggested field type: Large text
- A list of company ids (e.g., "CVR nr. 94052542") found on the store's website.
- Suggested field type: Text (max length 255)
- The url of the store's contact page (if any).
- Suggested field type: Text (max length 255)
- The store's country code.
- Suggested field type: Text (max length 255)
- The date at which the store's ecommerce website was created.
- Suggested field type: Date
- The 3-letter ISO currency code used on the store's ecommerce website.
- Suggested field type: Text (max length 255)
- A text description of the store's ecommerce website. Generally used to describe the goods and services provided by the merchant. Comes from the meta description tag on the stores's home page.
- Suggested field type: Large text
- The name of the ecommerce platform's pricing plan that the merchant is using (if known). e.g. "Shopify Plus"
- Suggested field type: Text (max length 255)
- The company's first email address.
- Suggested field type: Text (max length 255)
- The email address(es) listed on the company's ecommerce website
- Suggested field type: Text (max length 255)
- The number of employees working at the company that runs the store (if known).
- Suggested field type: Numerical
- An estimate of monthly page views for the store.
- Suggested field type: Numerical
- The store's estimated monthly sales (based on traffic estimates to the store's ecommerce website). Values in USD dollars.
- Suggested field type: Monetary
- The store's estimated yearly sales (based on traffic estimates to the store's ecommerce website). Values in USD dollars.
- Suggested field type: Monetary
- An estimate of monthly visits for the store.
- Suggested field type: Numerical
- The url of the store's FAQ page (if any).
- Suggested field type: Text (max length 255)
- The name of the company's Facebook account.
- Suggested field type: Text (max length 255)
- The URL of the company's Facebook account.
- Suggested field type: Text (max length 255)
- The name of the company's Facebook group.
- Suggested field type: Text (max length 255)
- The URL of the company's Facebook group.
- Suggested field type: Text (max length 255)
- A list of features enabled on the domain. e.g., "Shopify Pay"
- Suggested field type: Large text
- The url of the store's financing page (if any).
- Suggested field type: Text (max length 255)
- The full address of the store (includes street address, city, state, country if known).
- Suggested field type: Text (max length 255)
- The name of the company's Instagram account.
- Suggested field type: Text (max length 255)
- The URL of the company's Instagram account.
- Suggested field type: Text (max length 255)
- The date at which the store's website was last crawled.
- Suggested field type: Date
- The date at which the store's ecommerce platform's pricing plan was last changed.
- Suggested field type: Date
- The ecommerce platform that the store previously used (if any), prior to switching to their current platform
- Suggested field type: Text (max length 255)
- The date at which the store changed from their last ecommerce platform to their current ecommerce platform.
- Suggested field type: Date
- The URL of the company's LinkedIn page.
- Suggested field type: Text (max length 255)
- A list of Magento apps installed on the store's ecommerce website
- Suggested field type: Large text
- The name of the merchant that is selling on the store's ecommerce store.
- Suggested field type: Text (max length 255)
- The estimated amount the store spends on ecommerce apps every month.
- Suggested field type: Numerical
- The company's first phone number.
- Suggested field type: Text (max length 255)
- The company's second phone number.
- Suggested field type: Text (max length 255)
- The company's third phone number.
- Suggested field type: Text (max length 255)
- The phone number(s) listed on the company's ecommerce website
- Suggested field type: Text (max length 255)
- The name of the company's Pinterest account.
- Suggested field type: Text (max length 255)
- The number of Pinterest followers
- Suggested field type: Numerical
- The change in the number of Pinterest followers over the last 30 days.
- Suggested field type: Numerical
- The URL of the company's Pinterest account.
- Suggested field type: Text (max length 255)
- The ecommerce platform of the store's ecommerce website. (e.g., shopify or magento)
- Suggested field type: Text (max length 255)
- The name of the store's "platform domain". Some ecommerce platforms provide a unique internal domain (e.g., merchant.myshopify.com) that is associated with each store. Merchants can use this domain for their store but most choose to purhcase and register a custom DNS domain.
- Suggested field type: Text (max length 255)
- The Store Leads platform rank for the domain - a measure of the store's popularity relative to all other stores on the same platform.
- Suggested field type: Numerical
- The Store Leads platform rank percentile for the domain - a measure of the store's popularity relative to all other stores on the same platform.
- Suggested field type: Numerical
- The number of product variants (aka SKUs) sold on the store's ecommerce website.
- Suggested field type: Numerical
- The ratio of products sold to distinct vendors. This can be useful when trying to distinguish brands (which typically have a higher ratio since they sell their own products) from retailers (which typically have a lower ratio since they typically sell products from multiple vendors).
- Suggested field type: Numerical
- The number of products sold on the store's ecommerce website.
- Suggested field type: Numerical
- The Store Leads rank for the domain - a measure of the store's popularity relative to all other stores.
- Suggested field type: Numerical
- The Store Leads rank percentile for the domain - a measure of the store's popularity relative to all other stores.
- Suggested field type: Numerical
- The source of the record (always set to "Store Leads")
- Suggested field type: Text (max length 255)
- The url of the store's retailer page (if any).
- Suggested field type: Text (max length 255)
- The url of the store's returns page (if any).
- Suggested field type: Text (max length 255)
- A list of shipping carriers that the store uses.
- Suggested field type: Large text
- A list of Shopify app identifiers installed on the store's ecommerce website
- Suggested field type: Large text
- A list of Shopify app names installed on the store's ecommerce website
- Suggested field type: Large text
- The state or province of the merchant (if known)
- Suggested field type: Text (max length 255)
- The state or province code of the merchant (if known)
- Suggested field type: Text (max length 255)
- The store's status (e.g., active or inactive)
- Suggested field type: Text (max length 255)
- The DNS domain name of the ecommerce store.
- Suggested field type: Text (max length 255)
- The url of the store's store locator page (if any).
- Suggested field type: Text (max length 255)
- The street address of the store (if known).
- Suggested field type: Text (max length 255)
- The "top-level domain plus one" for the domain. For a domain named www.merchant.com, the TLD+1 is merchant.com
- Suggested field type: Text (max length 255)
- A list of third-party technologies installed on the store's ecommerce website
- Suggested field type: Large text
- The name of the current theme used on the store's ecommerce website.
- Suggested field type: Text (max length 255)
- The style of the current theme used on the store's ecommerce website.
- Suggested field type: Text (max length 255)
- The vendor of the current theme used on the store's ecommerce website.
- Suggested field type: Text (max length 255)
- The version of the current theme used on the store's ecommerce website.
- Suggested field type: Text (max length 255)
- The name of the company's TitTok account.
- Suggested field type: Text (max length 255)
- The number of TikTok followers
- Suggested field type: Numerical
- The change in the number of TikTok followers over the last 30 days.
- Suggested field type: Numerical
- The URL of the company's TikTok account.
- Suggested field type: Text (max length 255)
- The title tag on the store's ecommerce website home page
- Suggested field type: Text (max length 255)
- The url of the store's tracking page (if any).
- Suggested field type: Text (max length 255)
- The average rating of TrustPilot reviews for the domain.
- Suggested field type: Numerical
- The numer of reviews for the domain.
- Suggested field type: Numerical
- The name of the company's Twitter account.
- Suggested field type: Text (max length 255)
- The number of Twitter followers
- Suggested field type: Numerical
- The change in the number of Twitter followers over the last 30 days.
- Suggested field type: Numerical
- The URL of the company's Twitter account.
- Suggested field type: Text (max length 255)
- The number of distinct vendors of products sold on the store's ecommerce website. (Only available for Shopify stores)
- Suggested field type: Numerical
- The name of the company's YouTube account.
- Suggested field type: Text (max length 255)
- The number of YouTube followers
- Suggested field type: Numerical
- The change in the number of YouTube followers over the last 30 days.
- Suggested field type: Numerical
- The URL of the company's YouTube account.
- Suggested field type: Text (max length 255)
- The zip or postal code of the merchant (if known)
- Suggested field type: Text (max length 255)
- The id of the store's iOS app (if any).
- Suggested field type: Text (max length 255)
- The url of the store's iOS app (if any).
- Suggested field type: Text (max length 255)
Use the "Organization Field Mappings" section to customize the mappings between Store Leads data and Pipedrive organization fields.
Calculated Values for Organizations
In addition to the fields configured in the Organization Field Mapping section, it is also possible to write calculated values to organization fields. Calculated values write the results of an arbitrary expression to fields in Pipedrive. Expressions are written in Common Expression Language.
Example Expressions
has(_domain.technologies) ? _domain.technologies.size() : 0
Returns the number of different technologies used on the domain.
In addition to the mapped fields, expressions can also reference data that Store Leads collects for each domain.
Limitations:
- An expression cannot reference a property that does not originate from Store Leads.
Writing expressions can be a little tricky, so don't hesitate to ask for help.
Note that calculated values are only available on the Enterprise plan.
Manual Creation of Pipedrive Organizations
The Pipedrive integration allows you to manually create organizations in Pipedrive from Store Leads domains. To do so, click on the Pipedrive tab in the domain detail view.
As long as the domain does not already exist in Pipedrive, you'll be given the option to create a Pipedrive organization for the domain.
As soon as you click Create Organization in Pipedrive, Store Leads will create a new Pipedrive organization for the domain and set all the standard and custom fields configured for the integration.
Manual Update of Pipedrive Organizations
When you're looking at a domain in Store Leads that already exists as a Pipedrive organization, the Pipedrive tab will show you details for the existing Pipedrive organization and any people linked to the organization. Click on the "Enrich Pipedrive Organization" button to trigger a manual enrichment of the organization.
Bulk Creation of Pipedrive Organizations
The easiest way to bulk create organizations within Pipedrive is to create a List and then synchronize that list to Pipedrive.
Automatic Pipedrive Organization Updates On New Store Leads Data
By default, we automatically keep the data you store in Pipedrive in sync with the latest data on Store Leads by updating all your Pipedrive organizations as soon we publish new data (done weekly, typically on a Sunday night.
You may disable this behavior by unchecking the "Enrich Organizations" option.
Instead of waiting until the next weekly data update, it is possible to manually trigger enrichment of all existing Pipedrive organizations. This can be useful if you change your Organization Field Mappings and want the apply the changes to all Pipedrive organizations. To do so, click the "Enrich All Organizations Now" button.
Note: this feature is only available to accounts on the Pro or Elite plans.
Automatic Pipedrive Organization Updates On Changes within Pipedrive
When a new organization is created or updated within Pipedrive (e.g., manually creation in the Pipedrive UI), we'll automatically update it immediately with all our available data.
Note: this feature is only available to accounts on the Pro or Elite plans.
Automatic Pipedrive Organization Creation On New Store Leads Data
New Pipedrive organizations can automatically be created during our weekly data updates for stores matching any custom criteria. This is can be done by using a "Pipedrive Organization Action" within a Workflow.
Every week, as soon as we complete our data update, we'll find all stores matching the workflow criteria and create new Pipedrive organizations for all stores that do not already exist in Pipedrive.
As an example, you can define a list as a saved search that contains all stores with at least 250,000 Instagram followers. By enabling this option on the list, you can ensure that your Pipedrive instance will include all organizations that have at least 250,000 Instagram followers (both now and in the future).
Note: this feature is only available to accounts on the Pro or Elite plans.
Person Enrichment
Existing Pipedrive people can be automatically enriched every week when we publish our weekly data update. People will only be enriched if they are linked to a Pipedrive organization and that organization has a Website Field that matches a store in our database that your plan can access. It is also possible to enrich Pipedrive people as soon as they are created or changed. To enable this, check the "Enrich people" option.
Pipedrive Person Fields
Use the "Person Field Mapping" section to customize the fields set on person objects. The list of available fields for people is the same as the list of fields available for organizations (see "Pipedrive Organization Fields" section above).
Calculated Values for People
In addition to the fields configured in the Person Field Mapping section, it is also possible to write calculated values to person fields. Calculated values write the results of an arbitrary expression to fields in Pipedrive. Expressions are written in Common Expression Language.
Example Expressions
has(_domain.technologies) ? _domain.technologies.size() : 0
Returns the number of different technologies used on the domain.
In addition to the mapped fields, expressions can also reference data that Store Leads collects for each domain.
Limitations:
- An expression cannot reference a property that does not originate from Store Leads.
Writing expressions can be a little tricky, so don't hesitate to ask for help.
Note that calculated values are only available on the Enterprise plan
Automatic Pipedrive Person Updates On New Store Leads Data
We can automatically keep the data you store in Pipedrive in sync with the latest data on Store Leads by updating all your Pipedrive people as soon we publish new data (done weekly, typically on a Sunday night).
You may control this behavior using the "Enrich People" option.
Instead of waiting until the next weekly data update, it is possible to manually trigger enrichment of all existing Pipedrive people. This can be useful if you change your Person Field Mappings and want the apply the changes to all Pipedrive people. To do so, click the "Enrich All People Now" button.
Note: this feature is only available to accounts on the Pro or Elite plans.
Manual Creation of Pipedrive People
The Pipedrive integration allows you to manually create people in Pipedrive from Store Leads domains. To do so, ensure that the following option is enabled for your Pipedrive Integration.
Note that enabling this option requires that we scan all your existing people in Pipedrive. We need to know which people already exist so that we do not create duplicate people. See the Information Security Considerations section for more information.
After the option is enabled, click on the Pipedrive tab in the domain detail view.
You will see a list of existing people for the Pipedrive organization (if any) or people with an email domain that matches the domain of the store that you're currently looking at (if any). You'll also have the option to create new Pipedrive leads from the generic emails in the Store Leads database.
Automatic Pipedrive Person Creation
To automatically create people in Pipedrive as part of our weekly data updates, ensure that the following option is enabled for your Pipedrive Integration.
With the option enabled, you'll be able to configure a workflow to automatically create new people in Pipedrive.
Showing Pipedrive Data Within Store Leads
To view Pipedrive data directly within Store Leads, go to the Pipedrive tab in the store details.
Search Filter
With the Pipedrive integration enabled, new search filters are available that can be used to show all stores in the database that also exist as organizations (or people) in your Pipedrive instance. This filter is also supported in Advanced Search, allowing you to filter out stores that already exist in Pipedrive (a great way to look at new leads).
To filter on organizations, look for a filter called Integration Companies and click the Pipedrive Organizations value.
To filter on pople, look for a filter called Integration Contacts and click the Pipedrive People value.
To filter out stores that already exist in Pipedrive, run an Advanced Search, and create a filter on the "Integration Companies" field with Operation set to "Not Or".
Notes:
- These search filters are only available to accounts on the Pro or Elite or Enterprise plans.
Custom Search Filters
Accounts on the Enterprise plan can also use arbitrary fields in Pipedrive as Store Leads search filters. To get started:
- go to the Integrations page
- click on Pipedrive
- click on the Search tab
- Select the Organization Fields to use as Store Leads search filters
Newly created custom search filters will take a few hours to appear in Store Leads but, after this initial delay, any updates to records in Pipedrive will be reflected in the Store Leads search index within a few minutes.
Custom search filters can be used in Basic and Advanced search.
Search Results
Pipedrive data can be displayed as a column in search results. To do so, customize the columns displayed in search results to include "Pipedrive Organization".
This provides a way to visually filter search results by showing the stores that already exist in Pipedrive. You can also click on the "Pipedrive Organization" link to open the Pipedrive Organization page directly from search results.
Store Details
With the Pipedrive integration enabled, a new "Pipedrive" tab is available when viewing store details.
The list of fields to display for Pipedrive Organizations and People can be fully customized. Data display is fetched on demand from the Pipedrive API and is never stored by Store Leads. For more details, read displaying Pipedrive data within Store Leads.
Chrome Extension
It's also possible to display data for Pipedrive Organizations and People within the Store Leads Chrome Extension.
Best Practices
- Connect your organization to Pipedrive using a dedicated Pipedrive API account. If you connect to Pipedrive using an account linked to a person, the Store Leads integration with Pipedrive will break if that person's account is disabled in Pipedrive (which often happens when the person leaves the organization).
- Each person using Store Leads should also connect to Pipedrive with their personal account. If they do not, then all Pipedrive API calls made when using Store Leads are done with the organization connection. As a result, newly created accounts and leads will not be attributed to the right person.
Information Security Considerations
Since your Pipedrive instance contains PII, it is natural to have concerns about information security when connecting a new app to Pipedrive. Here is an overview of how Store Leads interacts with Pipedrive.
After the Pipedrive integration is enabled, Store Leads will query all Organization records to determine which of the stores in our database already exist as Organizations in Pipedrive. This is necessary so that:
- the Store Leads web interface/chrome extension can tell whether a store already exists in your CRM, and
- to enrich all your existing Organization records on a weekly basis and
- to prevent creating duplicate records
To accomplish this, each Organization's Website and Id fields are retrieved using the Pipedrive API and stored in our database. These are the only attributes accessed at this time.
By default, only Organization enrichment is enabled. If you choose to enable the "Enrich People" option in your integration (or manual creation of people), then we also need to pull and persist the Person Id and the Person's email domain (which is obtained from the person's email address) for the same reasons listed above. The email address is never persisted in raw form. Instead, a one-way hash of the email is persisted so that we can show you which emails (from our database) already exist in your Pipedrive instance.
The only time that attributes other than Domain and Id are retrieved for an Organization record (or Email/Domain/Id for People), is when a Store Leads user looks at the Pipedrive data for a Organization or Person through the Store Leads website or Chrome extension. Both of those features allow each user to configure which fields to pull from the CRM but these fields are never stored. They are pulled from the Pipedrive API live (to render the page) and never persisted. This data might include PII but since a) it is not persisted and b) it is configurable, it should hopefully be a minor concern.