Pardot integration summary

Stitch’s Pardot integration replicates data using the Pardot API. Refer to the Schema section for a list of objects available for replication.

Pardot feature snapshot

A high-level look at Stitch's Pardot (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Released on February 12, 2020

Supported by

Stitch

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-pardot

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Pardot

Pardot setup requirements

To set up Pardot in Stitch, you need:

  • A user with a preferred timezone of UTC. This is required to ensure you don’t encounter Extraction errors during Daylight Savings Time, as some Replication Key fields used by Stitch are reported in Pardot using the user’s preferred timezone. By using UTC, this ensures that time data is accurately reported during extraction. Otherwise, you might encounter Extraction errors during Daylight Savings Time.


Step 1: Retrieve your Pardot business unit ID

  1. Sign into your Salesforce account.
  2. Navigate to the Setup page.
  3. Enter Pardot Account Setup in the Quick Find.
  4. The Pardot setup page will display. Copy your 18-charater Pardot Business Unit ID and keep it readily available for the next step.

Step 2: Add Pardot as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Pardot icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Pardot” would create a schema called stitch_pardot in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the Pardot Business Unit Id field, paste your Business Unit ID that you copied in Step 1.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Pardot integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Pardot’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Pardot integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Authorize Stitch to access Pardot

  1. When finished in the Integration Settings page, click the Authorize button. You’ll be prompted to sign into your Pardot account.
  2. Sign into your Pardot account.
  3. After the authorization process is successfully completed, you’ll be directed back to Stitch.
  4. Click All Done.

Step 6: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Pardot integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up Pardot, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.


Pardot table reference

campaigns

The campaigns table contains info about the campaigns in your Pardot account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

id

Useful links

Pardot documentation

campaigns schema on GitHub

Pardot API method

Join campaigns with on
opportunities
campaigns.id = opportunities.campaign_id
prospects
campaigns.id = prospects.campaign_id

cost

INTEGER

id

INTEGER

name

STRING

email_clicks

The email_clicks table contains info about email click events.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

created_at

Useful links

Pardot documentation

email_clicks schema on GitHub

Pardot API method

Join email_clicks with on
visitor_activities
email_clicks.email_template_id = visitor_activities.email_template_id
email_clicks.list_email_id = visitor_activities.list_email_id
email_clicks.prospect_id = visitor_activities.prospect_id
list_memberships
email_clicks.prospect_id = list_memberships.prospect_id
prospects
email_clicks.prospect_id = prospects.id
visits
email_clicks.prospect_id = visits.prospect_id

created_at

DATE-TIME

drip_program_action_id

INTEGER

email_template_id

INTEGER

id

INTEGER

list_email_id

INTEGER

prospect_id

INTEGER

tracker_redirect_id

INTEGER

url

STRING

list_memberships

The list_memberships table contains info about list memberships.

Note: To replicate this table, the lists table must also be set to replicate.

Replication Method

Key-based Incremental

Primary Key

id

Replication Keys

id

list_id

updated_at

Useful links

Pardot documentation

list_memberships schema on GitHub

Pardot API method

Join list_memberships with on
lists
list_memberships.list_id = lists.id
email_clicks
list_memberships.prospect_id = email_clicks.prospect_id
prospects
list_memberships.prospect_id = prospects.id
visitor_activities
list_memberships.prospect_id = visitor_activities.prospect_id
visits
list_memberships.prospect_id = visits.prospect_id

created_at

DATE-TIME

id

INTEGER

list_id

INTEGER

opted_out

INTEGER

prospect_id

INTEGER

updated_at

DATE-TIME

lists

The lists table contains info about the lists in your Pardot account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

Pardot documentation

lists schema on GitHub

Pardot API method

Join lists with on
list_memberships
lists.id = list_memberships.list_id

created_at

DATE-TIME

description

STRING

id

INTEGER

is_crm_visible

BOOLEAN

is_dynamic

BOOLEAN

is_public

BOOLEAN

name

STRING

title

STRING

updated_at

DATE-TIME

opportunities

The opportunities table contains info about the opportunities in your Pardot account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Keys

id

updated_at

Useful links

Pardot documentation

opportunities schema on GitHub

Pardot API method

Join opportunities with on
campaigns
opportunities.campaign_id = campaigns.id
prospects
opportunities.campaign_id = prospects.campaign_id

campaign_id

INTEGER

closed_at

DATE-TIME

created_at

DATE-TIME

id

INTEGER

name

STRING

probability

INTEGER

stage

STRING

status

STRING

type

STRING

updated_at

DATE-TIME

value

NUMBER

prospect_accounts

The prospect_accounts table contains info about prospect accounts.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

Pardot documentation

prospect_accounts schema on GitHub

Pardot API method

Join prospect_accounts with on
users
prospect_accounts.assigned_to.user.id = users.id

assigned_to

OBJECT

user

OBJECT

account

INTEGER

created_at

DATE-TIME

email

STRING

first_name

STRING

id

INTEGER

job_tile

STRING

last_name

STRING

role

STRING

updated_at

DATE-TIME

created_at

DATE-TIME

id

INTEGER

name

STRING

updated_at

DATE-TIME

prospects

The prospects table contains info about the prospects in your Pardot account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

Pardot documentation

prospects schema on GitHub

Pardot API method

Join prospects with on
campaigns
prospects.campaign_id = campaigns.id
opportunities
prospects.campaign_id = opportunities.campaign_id
email_clicks
prospects.id = email_clicks.prospect_id
list_memberships
prospects.id = list_memberships.prospect_id
visitor_activities
prospects.id = visitor_activities.prospect_id
visits
prospects.id = visits.prospect_id

address_one

STRING

address_two

STRING

annual_revenue

STRING

campaign_id

INTEGER

city

STRING

comments

STRING

company

STRING

country

STRING

created_at

DATE-TIME

crm_account_fid

STRING

crm_contact_fid

STRING

crm_last_sync

DATE-TIME

crm_lead_fid

STRING

crm_owner_fid

STRING

crm_url

STRING

department

STRING

email

STRING

employees

STRING

fax

STRING

first_name

STRING

grade

STRING

id

INTEGER

industry

STRING

is_do_not_call

BOOLEAN

is_do_not_email

BOOLEAN

is_reviewed

BOOLEAN

is_starred

BOOLEAN

job_title

STRING

last_activity_at

DATE-TIME

last_name

STRING

notes

STRING

opted_out

BOOLEAN

password

STRING

phone

STRING

prospect_account_id

INTEGER

recent_interaction

STRING

salutation

STRING

score

INTEGER

source

STRING

state

STRING

territory

STRING

updated_at

DATE-TIME

website

STRING

years_in_business

STRING

zip

STRING

users

The users table contains info about the users in your Pardot account.

Replication Method

Key-based Incremental

Primary Key

id

Replication Keys

id

updated_at

Useful links

Pardot documentation

users schema on GitHub

Pardot API method

Join users with on
prospect_accounts
users.id = prospect_accounts.assigned_to.user.id

created_at

DATE-TIME

email

STRING

first_name

STRING

id

INTEGER

job_title

STRING

last_name

STRING

role

STRING

updated_at

DATE-TIME

visitor_activities

The visitor_activities table contains info about visitor activities.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

id

Useful links

Pardot documentation

visitor_activities schema on GitHub

Pardot API method

Join visitor_activities with on
email_clicks
visitor_activities.email_template_id = email_clicks.email_template_id
visitor_activities.list_email_id = email_clicks.list_email_id
visitor_activities.prospect_id = email_clicks.prospect_id
list_memberships
visitor_activities.prospect_id = list_memberships.prospect_id
prospects
visitor_activities.prospect_id = prospects.id
visits
visitor_activities.prospect_id = visits.prospect_id
visitor_activities.visitor_id = visits.visitor_id
visitors
visitor_activities.visitor_id = visitors.id

campaign

OBJECT

campaign_id

INTEGER

created_at

DATE-TIME

details

STRING

email_id

INTEGER

email_template_id

INTEGER

file_id

INTEGER

form_handler_id

INTEGER

form_id

INTEGER

id

INTEGER

landing_page_id

INTEGER

list_email_id

INTEGER

multivariate_test_variation_id

INTEGER

paid_search_id_id

INTEGER

prospect_id

INTEGER

site_search_query_id

INTEGER

type

INTEGER

type_name

STRING

updated_at

DATE-TIME

visitor_id

INTEGER

visitor_page_view_id

INTEGER

visitors

The visitors table contains info about visitors.

Replication Method

Key-based Incremental

Primary Key

id

Replication Key

updated_at

Useful links

Pardot documentation

visitors schema on GitHub

Pardot API method

Join visitors with on
visitor_activities
visitors.id = visitor_activities.visitor_id
visits
visitors.id = visits.visitor_id

campaign_parameter

STRING

content_parameter

STRING

created_at

DATE-TIME

hostname

STRING

id

INTEGER

ip_address

STRING

medium_parameter

STRING

page_view_count

INTEGER

source_parameter

STRING

term_parameter

STRING

updated_at

DATE-TIME

visits

The visits table contains info about visits.

Note: To replicate this table, you must also set the visitors table to replicate.

Replication Method

Key-based Incremental

Primary Key

id

Replication Keys

id

updated_at

Useful links

Pardot documentation

visits schema on GitHub

Pardot API method

Join visits with on
email_clicks
visits.prospect_id = email_clicks.prospect_id
list_memberships
visits.prospect_id = list_memberships.prospect_id
prospects
visits.prospect_id = prospects.id
visitor_activities
visits.prospect_id = visitor_activities.prospect_id
visits.visitor_id = visitor_activities.visitor_id
visitors
visits.visitor_id = visitors.id

campaign_parameter

STRING

content_parameter

STRING

created_at

DATE-TIME

duration_in_seconds

INTEGER

first_visitor_page_view_at

DATE-TIME

id

INTEGER

last_visitor_page_view_at

DATE-TIME

medium_parameter

STRING

prospect_id

INTEGER

source_parameter

STRING

term_parameter

STRING

updated_at

DATE-TIME

visitor_id

INTEGER

visitor_page_view_count

INTEGER

visitor_page_views

OBJECT

visitor_page_view

ARRAY

created_at

DATE-TIME

id

INTEGER

title

STRING

url

STRING


Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.