Source connector

Pardot connector

Pardot integration for databases, warehouses and BI tools

B2B marketing automation on the Salesforce platform. Datrise captures Pardot entities such as prospects, campaigns, emails, forms, and engagement grades, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Pardot API v4 (legacy) - superseded by the Account Engagement API v5 authenticates with OAuth 2.0, incremental runs key on updated_at, and Pardot caps calls at Daily API request limits by Account Engagement edition: 25,000/day (Growth), 50,000/day (Plus), 100,000/day (Advanced/Premium); at most 5 concurrent requests per account (exceeding it returns error code 66).

Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 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 `pardot_prospects`) with a schema derived from the 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 Pardot pipeline page, and join the waitlist to get the Pardot connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What 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	pardot_prospects	Upsert by primary key, incremental on updated-at
campaigns	pardot_campaigns	Upsert by primary key, incremental on updated-at
emails	pardot_emails	Upsert by primary key, incremental on updated-at
forms	pardot_forms	Upsert by primary key, incremental on updated-at
engagement grades	pardot_engagement_grades	Upsert by primary key, incremental on updated-at

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	Pardot API v4 (legacy) - superseded by the Account Engagement API v5
Authentication	OAuth 2.0 — Salesforce OAuth 2.0 (typically the Web Server Flow) with the `pardot_api` scope; every request also requires a `Pardot-Business-Unit-Id` header (an 18-character ID starting `0Uv`) alongside the `Authorization: Bearer` token.
Pagination	cursor — Query endpoints return up to 200 rows per page and are paged with a caller-tracked high-water mark (largest `id`, or most recent `created_at`/`updated_at`) passed back as `id_greater_than`/`created_after`/`updated_after`, rather than a server-issued offset or token.
Rate limit	Daily API request limits by Account Engagement edition: 25,000/day (Growth), 50,000/day (Plus), 100,000/day (Advanced/Premium); at most 5 concurrent requests per account (exceeding it returns error code 66).
Incremental cursor	updated_at — List/query endpoints accept `updated_after`/`updated_before` (and `created_after`/`created_before`) search criteria for incremental extraction.
Webhooks	No
Bulk export	Yes — Export API for visitor activity (asynchronous); other objects use the paginated Query endpoint with high-water-mark iteration as the de facto bulk mechanism
Deletes detectable	No

Official API reference

What bites when replicating Pardot

Pardot API v4 (used only by Business Units with 'Allow Multiple Prospects with Same Email Address' enabled) and v3 (non-AMPSEA) are both legacy and functionally frozen; Salesforce's current guide steers all new integration work to Account Engagement API v5, which unifies both variants under `v5/objects/` paths and changes prospect updates to be keyed by `id` instead of `email`.
Every request must carry a `Pardot-Business-Unit-Id` header in addition to the OAuth bearer token; omitting it (a common miss when reusing generic Salesforce OAuth boilerplate) fails auth even with an otherwise valid token.
The account is capped at 5 concurrent API requests regardless of edition (error code 66 on the 6th), so a connector that parallelizes object pulls too aggressively will throttle itself well before hitting the daily request-count ceiling.
Query-endpoint pagination has no server-side cursor token; the client must track its own high-water mark (largest `id` or `updated_at` seen) and stop only when a page returns fewer than 200 rows, so a naive fixed-offset paging implementation will silently loop or skip records as data changes mid-pull.

Compare this against every other documented API

Popular destinations for 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

Pardot connector FAQ

What Pardot data does the connector extract?: 5 objects: prospects, campaigns, emails, forms and engagement grades. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the 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 Pardot data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each 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 Pardot pipeline with guided onboarding

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