This integration is currently available for private beta testing. Contact [email protected] if you wish to get this enabled for your site.
On this page we look at all the configuration options available for the Pipedrive integration. You can access the configuration page by navigating as follows:
These settings are also displayed during the time that the integration is setup for the first time.
Discussed below are the available options for configuring how customer records are synced from Chargebee to person and organization records in Pipedrive. The images below show the various options available:
Each of the options available above are discussed below:
This option is selected by default.
Customer records are synced to Pipedrive even if they do not have subscriptions attached.
Only those customer records are synced to Pipedrive that have subscriptions attached to them.
This option is enabled by default.
Once a matching Pipedrive person record is found for a given Chargebee customer record, they are mapped to each other. This setting determines what happens when a match is not found.
Enable this toggle to allow Chargebee to create new person records in Pipedrive when a match is not found in the latter. This is useful when some leads appear in Chargebee first, as customer records and you want them to be synced to Pipedrive so that your sales team may nurture them. For example, when your customers sign-up for trial subscriptions from an online storefront.
|Disabled||Disable this toggle to prevent new person records from being created in Pipedrive by Chargebee. You would choose this option if you have a sales-driven workflow and leads are never created in Chargebee first.|
This option is disabled by default.
Select this option to allow Chargebee to create organization records in Pipedrive and manage their relationships with person records. This option helps if you are a B2B business that needs to have Chargebee customer records mapped to Pipedrive organizations. Disable this option if you are a B2C-only business that has only individual consumers as customers.
Once, if subscription data has been synced to the organization object (due to setting 3.1), then this setting cannot be disabled.
If the company name of the customer record matches an organization name in Pipedrive, the mapped person record is linked to that organization. If a matching organization is not found, a new one is created. Also, if the company name of a customer record is changed, then on syncing, the person record is delinked from its organization and then linked to the updated organization. The new organization, if not found in Pipedrive, is created.
If two or more Pipedrive organization records have the same name, and a Chargebee customer record matches that organization name, it would fail to sync. This is because it is unclear as to which Pipedrive organization record, the Chargebee customer record should sync to.
What's the company name for a customer in Chargebee?
Subscription data in Chargebee can also be pushed to Pipedrive. Here, you can choose the object you want to append the data to: either People or Organization. Note that if setting 3 is disabled, then the subscription data is synced to people records. You can select the specific fields that are synced under this configuration. If you don't want subscription data to be pushed to Pipedrive, you can uncheck the subscription fields under that configuration.
To maintain data integrity, this setting cannot be changed once subscription data has been synced to Pipedrive.
When there are multiple subscriptions for any given customer record, the most relevant is selected by Chargebee to be synced to Pipedrive. The most relevant subscription is the one with the highest rank according to the following table:
Here too, if there are multiple subscriptions of the highest rank, then the one that was modified last is chosen for syncing.
The ranking logic described above is applied on every sync so that the most relevant subscription is kept synced to Pipedrive.
This option is selected by default if setting 3 is disabled.
CB Customer Status custom field in the person record to
This option is selected by default if setting 3 is enabled.
CB Customer Status field in the person record to
Deleted. Also, if there are no other person records attached to the organization, the
CB Status field for the latter is also set to
No changes are made.
The default value selected for this setting is email address.
Choose the fields used to match Chargebee customer records with Pipedrive person records. Some considerations follow:
If you use an API-based integration where you create customers in Chargebee on lead generation in Pipedrive, then do the following:
Deals can be updated in Pipedrive based on changes in subscriptions or one-time invoices for customers.
Delayed sync for deals
Deals are updated in Pipedrive only from the second full sync onwards. This limits the time taken for the first sync to complete especially when there are a lot of customer records in Chargebee.
Chargebee allows you to create deals for the following events:
Here's how a deal is created:
When deals are created by Chargebee, they're linked to the contact that the subscription details are appended to. See setting 3.1.
The integration allows you to update existing deals in Pipedrive for the following events:
Here's how a deal is updated:
If no deals meeting the above conditions are found, then Chargebee looks for open deals for the contact and updates the last created one. Further, if no open deals are found for the contact, a sync error occurs. The "contact" here refers to "person" or "organization", depending on how setting 3.1 is set above.
If you create multiple deals for the same contact, you would end up having more than one subscription for the contact. Insert the subscription ID of each subscription into the CB Subscription ID field of the corresponding deal to ensure that the correct deal is updated for every subscription. Similarly, for deals that correspond to one-time invoices for customers, insert the invoice Id into the CB Invoice ID field of the corresponding deal.
When creating or updating deals based on subscription-related events, there are several options available for setting the deal value.
To understand the options available, consider an invoice with the following details:
A. 12 months plan: $1200
B. Recurring addon with period 2 months: $120
C. Non-recurring addon: $50
D. Subtotal: A + B + C = $1370
E. US sales tax @ 2% = $27.4
F. TOTAL: D + E = $1397.4
The options available are as follows:
You can choose to add automated notes to deals when they are created or updated. Here are some sample notes that are added:
The integration always syncs a set of standard fields from Chargebee to Pipedrive. You can also choose to sync additional Chargebee customer and subscription fields (including custom fields) to the Pipedrive contacts. Customer fields chosen here are synced to the person object. Subscription fields are synced to the person object by default or the organization object if configured accordingly under setting 3.1. The field names are synced to the Pipedrive objects as custom fields with the naming convention CB
After the first full sync, the following options are available on the left side of the integration page as shown:
Auto sync is enabled by default. When enabled, the sync runs automatically every 1 hour. The Overview page shows the the last time the sync was run.
Choose this option to go to the configuration page (as described from the beginning of this page).
Any changes made here only affect new records synced from the point of applying the change. The changes are not applied retrospectively, that is, the previously synced records are not affected.
For example, If you change the unique Id used to match records between Chargebee and Pipedrive, the mapping between existing customer and person records is not changed. Any new customer records created after this change are matched using the new setting when the sync runs next.
Unlinking the integration deletes the integration configuration information and stops any information from being pushed to Pipedrive.