Source connector

Salesforce Pardot connector

Salesforce Pardot integration for databases, warehouses and BI tools

B2B marketing automation scoring and nurturing leads. Datrise captures Salesforce Pardot entities such as prospects, campaigns, list emails, forms, lead scores and engagement history, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Account Engagement (Pardot) API v5 authenticates with OAuth 2.0, incremental runs key on updatedAt, and Salesforce Pardot caps calls at 25,000 API requests/day on Growth, 50,000 on Plus, 100,000 on Advanced/Premium (resets on the account's timezone, error code 122 past the limit), capped at 5 concurrent requests (error code 66 past that).

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `salesforce_pardot_prospects`) with a schema derived from the Salesforce Pardot API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Salesforce Pardot pipeline page, and join the waitlist to get the Salesforce Pardot connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Salesforce Pardot data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
prospects	salesforce_pardot_prospects	Upsert by primary key, incremental on updated-at
campaigns	salesforce_pardot_campaigns	Upsert by primary key, incremental on updated-at
list emails	salesforce_pardot_list_emails	Upsert by primary key, incremental on updated-at
forms	salesforce_pardot_forms	Upsert by primary key, incremental on updated-at
lead scores	salesforce_pardot_lead_scores	Upsert by primary key, incremental on updated-at
engagement history	salesforce_pardot_engagement_history	Append-only, incremental by timestamp

Salesforce Pardot API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Account Engagement (Pardot) API v5
Authentication	OAuth 2.0 — Uses a Salesforce Connected App OAuth 2.0 flow like core Salesforce, but every request also requires a `Pardot-Business-Unit-Id` header identifying the Account Engagement business unit.
Pagination	token — Queries return a `nextPageToken` (valid 4 hours) to fetch the following page; a token cannot be combined with `orderBy`, `offset`, `limit`, or filter parameters, and `limit` otherwise accepts 1-1000 (default 200).
Rate limit	25,000 API requests/day on Growth, 50,000 on Plus, 100,000 on Advanced/Premium (resets on the account's timezone, error code 122 past the limit), capped at 5 concurrent requests (error code 66 past that)
Incremental cursor	updatedAt — Objects expose `createdAt`/`updatedAt` timestamps usable with `orderBy`, but v5 responses can be served from a cache up to 60 seconds stale, so a poll immediately after a write can miss the change.
Webhooks	No
Bulk export	Yes — Export API (required once an offset beyond 2,000 records is needed, since token pagination caps at 100,000 records per sequence)
Deletes detectable	Yes — the `deleted` query parameter (`true` for recycle-bin-only, `all` for both) surfaces recycled records; a `Pardot-Warning: Record In Recycle Bin` header appears if an operation targets one

Official API reference

What bites when replicating Salesforce Pardot

`nextPageToken` pagination is capped at 100,000 total records per sequence; past that the server stops issuing new tokens and returns a warning header instead, so an Export API job (not the paginated list endpoint) is required for larger extracts.
A page token cannot be combined with `orderBy`, `offset`, `limit`, or filter parameters, so a connector switching from offset-based to token-based paging mid-extract has to drop those parameters entirely.
Daily request quota is edition-gated (25,000/50,000/100,000 depending on Growth/Plus/Advanced-Premium) and shared with every other integration hitting the same business unit, with error code 122 on overage and code 66 past 5 concurrent requests.
V5 responses can be served from a cache up to 60 seconds old, so polling immediately after writing a record through the same API can still return the pre-update value.

Compare this against every other documented API

Popular destinations for Salesforce Pardot

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Salesforce Pardot connector FAQ

What Salesforce Pardot data does the connector extract?: 6 objects: prospects, campaigns, list emails, forms, lead scores and engagement history. Each lands in its own table with types preserved; history-style objects (1: engagement history) load as append-only streams.
Is the Salesforce Pardot integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Salesforce Pardot data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Salesforce Pardot → destination pair has its own page with the object-to-table mapping.

Related Marketing sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Salesforce Pardot pipeline with guided onboarding

Join the waitlist to get priority access for Salesforce Pardot integrations with guided setup, schema-aware mapping, and production-grade incremental sync.