# Salesforce Pardot Destination ## Destination Info * Accepts [Identify](/docs/segment/connections/spec/identify) calls. * Refer to it as **Pardot** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) ### Components * [Browser](https://github.com/segment-integrations/analytics.js-integration-pardot) * Server > \[!WARNING] > > This destination is currently under maintenance. Please check back later or contact support. ## Getting Started When you enable Pardot in the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Pardot's javascript onto your page. This means you should remove Pardot's snippet from your page. Pardot automatically collects anonymous visitor data data on your site. Pardot is supported on the client-side and server-side. ## Update your Segment Pardot destination to use Salesforce SSO > \[!NOTE] > > Starting February 15, 2021, Pardot will require that you authenticate using Salesforce's single sign-on (SSO), rather than a Pardot username and password. If you are not already using SSO, you must reconnect your Segment Pardot destination using Salesforce SSO before February 15th to keep data flowing to Pardot. If you don't have a Salesforce account, contact your Salesforce administrator. They can grant you a Salesforce Identity License, which allows you to use Salesforce for SSO purposes without provisioning a full Salesforce account. To reconnect Pardot to Segment using SSO authentication: 1. In the Segment app, click **Connections** on the left, then click **Destinations**. Select your Pardot destination. 2. On your Pardot settings page, click **Connect to Pardot**, and follow the steps to connect using OAuth. ![Pardot settings page with OAuth connection warning and email invitation option.](https://docs-resources.prod.twilio.com/0802e86bb3bacbb7a27ea326d4b866d31dc1c74cf4ba0599c92cb171ffb8a437.png) 3. On the next screen, you are prompted to authenticate using your Salesforce username and password. If you don't have a Salesforce account, contact your Salesforce administrator. They can grant you a Salesforce Identity License, which allows you to use Salesforce for SSO purposes without provisioning a full Salesforce account. 4. On the Pardot destination settings page, click **Primary Business Unit Id** and specify the [Primary Business Unit Id](/docs/segment/connections/destinations/catalog/pardot/#primary-business-unit-id) associated with your Pardot Account in Salesforce. ## API Access To connect to the Pardot API, Segment requires that you authenticate your account using your Salesforce single sign-on (SSO) credentials. When you first connect to the Pardot destination, you are prompted to sign in using Salesforce SSO. > \[!TIP] > > If you don't have a Salesforce account, contact your Salesforce administrator. They can grant you a Salesforce Identity License, which allows you to use Salesforce for SSO purposes without provisioning a full Salesforce account. ### Pardot Version 3 and Version 4 There are currently two active versions of the Pardot platform, version 3 and version 4. The major change in version 4 is the new ability to create multiple prospects in Pardot with the same email address. Previously, this was not possible. Email was used by Pardot as a distinct identifier. In version 4 however, in order to update an *existing* prospect, you must provide either the Pardot ID for a given user OR the Salesforce FID. If one of these values is not provided in a request, Pardot will create a new prospect. More information is available on their [website](http://developer.pardot.com/kb/api-version-4/). The Segment Pardot destination provides two different options to support this new functionality. Read on to learn more. ## Identify ### Version 3 When you call `identify`, Segment creates or updates a prospect in Pardot. If you are using version 3 of the Pardot platform, make sure you pass an `email` trait so Segment can check if that prospect already exists. If a prospect already exists, Segment updates its fields with the `traits` you provide. Otherwise, Segment creates a new prospect. ```js analytics.identify('YOUR_DATABASE_USER_ID', { email: 'tom@example.com', name: 'Tom Smykowski' company: 'Initech, Inc', department: 'Customer Service', years_in_business: '10', notes: 'Working on a "Jump to Conclusions" mat', description: 'Im a people person. What the hell is wrong with you people?', title: 'VP of Engineering' }); ``` Find other accepted traits in [Pardot's Prospect field reference](https://developer.pardot.com/kb/object-field-references/#prospect). You can provide custom fields, but they won't be updated or visible until you create them in the Pardot user interface by going to **Admin > Configure Fields > Prospect Fields**. ### Version 4 > \[!NOTE] > > The Segment integration with v4 of the Pardot API is currently in beta, and is only available in cloud-mode. If you are using version 4, the functionaly is the same as version 3 except you will need to provide some kind of identifier to Segment that we can use to correctly handle either the creation of a new prospect *or* the update of an existing one. There are two options for this. #### FID or ID Properties If you are able to access either the **SalesforceFID** or **PardotID** for a given user, you can pass these properties to Segment as [integration specific options](/docs/segment/connections/sources/catalog/libraries/server/node/#selecting-destinations). The properties must be named either `id` to pass a PardotID, or `fid` to pass the Salesforce FID. ```javascript analytics.identify({ userId: 'YOUR_DATABASE_USER_ID', traits: { email: 'bill@segment.com' }, integrations: { Pardot: { fid: '00339000033ZUR6' } } }); ``` #### Lookup Field If you do not have access to a given user's **SalesforceFID** or **PardotID**, you can alternatively specify a custom field in your Pardot instance for us to use to lookup and match a given user on. For example, if you maintain an internal uuid for each of your users, you could create a field in Pardot with a name of your choosing (`org_id` for example) and in your integration settings, specify this field name. Then, when you send an `identify` event to Segment we will check to see if a prospect exists in Pardot with a value in this custom field that matches the value of a trait property with the same name as the custom field. If the match is successful, we will update that prospect with their proper PardotID. If not, we will create a new prospect. Here is an example that assumes you have a custom field in Pardot called `org_id`: ```javascript analytics.identify({ userId: 'YOUR_DATABASE_USER_ID', traits: { email: 'bill@segment.com', org_id: '1sf324fd53' } }); ``` If a user existed in your Pardot instance with a custom field called `org_id` and a value of `1sf324fd53`, the user would be successfully updated. Otherwise, a new user would be created with `org_id` properly populated for future reference. **Use UserID as Lookup Field Value** Alternatively, you can specify in your integration settings that we use the `userId` passed in as an argument to the `identify` event to match the user on. Keeping with the above example, if you already were using your internal `org_id` as the `userId` for Segment events, you could enable this option and avoid having to explicitly define it as a trait. **Important**: If you have users in Pardot that do not have values for the custom field you will be using as a lookup field, you will likely see duplicate prospects being created. If possible, we recommend you explore bulk updating all existing users to ensure they have a value for this custom field before enabling the integration. ### Client Side On the client-side browser Segment loads Pardot's JavaScript snippet to enable [anonymous visitor tracking](http://www.pardot.com/products/marketing-automation/benefits/website-visitor-id-and-anonymous-visitor-tracking/). ### Troubleshooting #### Updating a prospect's email creates a new prospect If you use Version 4 of the API and use a lookup field to match existing prospects with Segment `identify` events, Pardot creates a new prospect when you try to update a prospect's email address. This is because the Pardot API does not allow write operations using an email address - you can only run a read (or lookup) operation with email addresses. (This restriction also applies to the SalesforceFID.) In this case the Segment integration performs a *read* operation for a prospect matching the new email you sent. The read operation does not return a lookup field match, and so Pardot creates a new user. To update a user's email, you must pass either a PardotID or a SalesforceFID (see above for specifics on how to do this). ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`. When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync. > \[!NOTE] > > Real-time audience syncs to Salesforce Pardot may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected. ## Settings Segment lets you change these destination settings from the Segment app without having to touch any code. | Field | Description | Required | Type | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | | API Version | Please choose which version of the Pardot API you are using. If you are unsure, please reference this \[guide]\(http://developer.pardot.com/kb/api-version-4/) to verify. If your account \*\*allows\*\* multiple prospects with the same email address, you are using version 4. Otherwise, you are using version 3. \*\*Important:\*\* If you are selecting version 4, please read our \[documentation]\(/docs/segment/connections/destinations/catalog/pardot) thoroughly before proceeding. | No | select | | Prospect Lookup Field ID | Specify the Field ID in Pardot to use as a lookup to identify unique prospects with. The Field Id cannot be \`id\` or \`fid\` as these are reserved keywords in the Pardot API. Needs to be case sensitive. \*\*Important:\*\* this option is only applicable if you are using version 4 of the Pardot API. If you are using V4 of the API but plan on passing a \`SalesforceFID\` or \`PardotID\` as a property of an \`identify\` event, you can also ignore this setting. Please see our \[documentation]\(/docs/segment/connections/destinations/catalog/pardot/) for more details. | No | string | | Use User ID as Lookup Value | If enabled, we will use the userId you pass into \`identify\` events as the lookup key value. If disabled, we will search for a trait in the event with the same name as the lookup field ID and match on that. | No | boolean | | Account ID | You can find your Account ID (or \`piAId\`) under \*\*Marketing > Campaigns\*\* in your \[Pardot account]\(https://pi.pardot.com/campaign). After selecting your desired website campaign, press \*\*View Tracking Code\*\*. | Yes | string | | Campaign ID | This setting is only used in the client side \`analytics.js\` integration with Pardot and will not be used if you are sending data from a server side source. You can find your Campaign ID (or \`piCId\`) under \*\*Marketing > Campaigns\*\* in your \[Pardot account]\(https://pi.pardot.com/campaign). After selecting your desired website campaign, press \*\*View Tracking Code\*\*. Note: you can still use a URL query parameter of \`pi\_campaign\_id\` to override this on specific pages. | Yes | string | | Primary Business Unit Id | Specify the Pardot \*\*Business Unit Id\*\* associated with your Pardot Account in Salesforce. To find your Business Unit ID in Salesforce, go to Setup and search for \`Pardot\`. Your Pardot Business Unit ID is an 18 character long string that starts with \`0Uv\`. If you cannot access the Pardot Account Setup information, ask your Salesforce Administrator to find the Pardot Business Unit ID for you. | No | string |