Pardot

Pardot is a Software as a Service(SaaS) marketing automation platform by Salesforce which serves as a central location to manage your email automation, targeted email campaign, and lead management projects. Hevo accesses the data present in your Pardot environment using your SSO-enabled Salesforce login.

Pardot uses the concept of domains and business units to host the data for all your projects.

• Pardot Domain: Pardot provides you the following domains for hosting your different Pardot environments:

  • pi.demo.pardot.com: This domain hosts demo, developer org, and sandbox environments.

  • pi.pardot.com: This domain hosts training and production environments.

• Pardot Business Unit: Business Units are separate databases within a Pardot account that can hold data for your prospects, campaigns, and assets. Business units allow you to partition the data by regions, products, or services. For example, if your website is hosted on a different region, you can set up one business unit for each region.

You can replicate data from any Pardot domain and business unit to the Destination system using Hevo Pipelines. You must create one Pipeline for each business unit you want to replicate data from.

---

Prerequisites

• An active Pardot account with Administrator access.

• Single sign-on (SSO) is enabled for the Salesforce user, as Hevo accesses your Pardot environment using Salesforce login.

---

Configuring Pardot as a Source

Perform the following steps to configure Pardot as a Source in your Pipeline:

1. Click PIPELINES in the Asset Palette.

2. Click + CREATE in the Pipelines List View.

3. In the Select Source Type page, select Pardot.

4. In the Configure your Salesforce Account linked to Pardot page, click + ADD SALESFORCE ACCOUNT LINKED TO PARDOT.

   

5. Select the environment associated with your Salesforce login and click CONTINUE.

   

6. Log in to your Salesforce account.

7. Click Allow to authorize Hevo to access your Pardot environment.

   

   You are then redirected to the Configure your Pardot Source page.

8. In the Configure your Pardot Source page, specify the following:

   

   1. Pipeline Name: A unique name for your Pipeline.

   2. Pardot Domain Name: Select the domain name where your Pardot data is hosted.

   3. Pardot Business Unit ID: A unique identifier for your Pardot business unit whose data you want to replicate. It is 18 characters long and begins with the value 0Uv.

   4. Historical Sync Duration: The duration for which the past data must be ingested. Historical sync duration is All Available Data by default.

9. Click TEST & CONTINUE.

10. Proceed to configuring the data ingestion and setting up the Destination.

---

Locating the Pardot Business Unit ID

To locate the Pardot business unit ID:

1. Log in to your Salesforce account linked to Pardot.

2. In the top right, click the gear icon, and then click Setup in the drop-down.

   

3. In the left navigation pane, search for and click Pardot Account Setup in the Quick Find search bar.

   

4. In the Assign Your Pardot Admins page, locate your Business Unit ID.

   

---

Enabling Single Sign-on for the Salesforce User

You must enable Salesforce Single Sign-On (SSO) in Pardot to allow Hevo to access your Pardot data. To do this:

1. Log in to your Salesforce account linked to Pardot.

2. Click the menu icon in the top-left, and then, search and click Pardot to launch the Pardot Lightning App.

   

   Note: If you do not have Pardot Lightning App enabled, then read this.

3. Click the Pardot Settings tab.

4. In the left navigation pane, click the User Management drop-down, and then click Users.

   

5. Select the user for whom you want to enable SSO.

6. Click the gear icon next to the selected user and in the drop-down, click Edit.

   

7. Scroll down and select the Salesforce CRM Username of the user for whom you want to enable SSO from the CRM Username drop-down.

   

   Note: A user’s username and email address need not be the same but the username must be in the form of an email address.

8. Click Save user.

---

Data Replication

Historical Data: Once you create the Pipeline, all data associated with the Pardot account is ingested by Hevo and loaded into your Destination.

Incremental Data: Once the historical load is completed, each subsequent run of the Pipeline:

• Fetches the entire data for the email_click and tag_object.

• Fetches the incremental data for all the other objects.

---

Source Consideration

• The earliest date from which the data is fetched is 1st Jan, 2007.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

---

Data Model

Hevo uses the following data model to ingest data from your Pardot account:

Object	Description
campaign	Contains details of the Salesforce campaigns linked with Pardot.
email_click	Records the event details when an email is opened.
list	Contains list of emails sent.
list_membership	Contains information on all the prospects within a list.
opportunity	Tracks pending or actual revenue from a sale.
opportunity_prospect	Is a custom table generated by Hevo to maintain data sanity between the opportunity & the prospect.
prospect	Contains a list of prospect and their details. Prospects are visitors with an associated email address in Pardot.
prospect_account	Contains a list of companies and their details. A prospect account allows you to group prospects that work for the same company.
tag	Contains a list of tags. Tags are taxonomy defined to help in reporting.
tag_object	Contains information about the location where tags are assigned.
user	Contains a list of Pardot users.
visit	Contains details of each visit made by a visitor.
visitor	Contains a list of visitors. Visitors are anonymous users who visit your website.
visitor_activity	Contains visitor’s activity data.
visitor_page_view	Contains details of pages visited by a visitor during each visit.

---

Limitations

• Hevo does not support data integration for Pardot-only users. Hevo requires you to have a Salesforce account linked to Pardot for replicating your Pardot data into a Destination system.