How to Integrate Pardot with Your Headless CMS

What is Pardot?

Pardot, now called Salesforce Marketing Cloud Account Engagement, is Salesforce's B2B marketing automation product. Marketing and revenue teams use it for lead capture, scoring, grading, email nurturing, campaign attribution, forms, landing pages, and prospect activity tracking. It's common in Salesforce-centered stacks where sales and marketing teams need prospect data to move between campaigns and CRM records.

Why integrate Pardot with a headless CMS?

If your campaign copy, gated asset metadata, form settings, and Pardot campaign IDs live in different places, launches get slow fast. A marketer publishes a webinar page, then someone copies the title into an email, pastes the form handler URL into the frontend, adds a campaign ID in Pardot, checks UTM values, and asks a developer to confirm that the right list membership fires. That works for 3 campaigns. It breaks when you're running 40 regional landing pages and 12 nurture tracks.

Connecting Pardot to a headless CMS category setup gives your marketing stack one place to read structured campaign content from. With Sanity's AI Content Operating System, campaign pages can model fields like Pardot campaign ID, form handler URL, scoring category, gated asset URL, CTA copy, and UTM defaults as typed JSON in the Content Lake. GROQ selects exactly the fields Pardot needs, and webhooks or Functions can run when a page is published, updated, or unpublished.

The alternative is manual coordination. You get copy drift between the website and Pardot emails, stale campaign IDs, broken form mappings, and reporting that depends on spreadsheet notes. The trade-off is that you do need to define the data contract clearly. Pardot is strict about authenticated API calls, business unit IDs, and field names, so the integration should validate required fields before publish instead of failing after launch.

Architecture overview

A typical Sanity and Pardot integration starts when an editor publishes a campaign landing page, gated asset, event, or resource in Sanity Studio. The document is written to the Content Lake as structured JSON. A GROQ-filtered webhook, for example _type == "campaignLandingPage" && defined(pardot.campaignId), fires only for content that should sync to Pardot. That webhook can call a Sanity Function or your own API route. The server-side handler uses @sanity/client to fetch the full document with GROQ, including joined references like author, topic, region, CTA, and gated asset. The handler then authenticates with Salesforce OAuth, gets an access token, and calls the Pardot Account Engagement API with the Authorization header and Pardot-Business-Unit-Id header. For content-led campaigns, the handler might create or update a Pardot custom redirect for a trackable CTA URL, sync the Pardot campaign ID used by the frontend, or validate the form handler configuration before publish. For lead capture flows, the frontend can submit to a Pardot form handler or to your middleware, which then calls Pardot's prospect and list membership endpoints. The end user sees a landing page built from Sanity content, submits a form or clicks a tracked CTA, and Pardot records the prospect activity for scoring, nurturing, and Salesforce attribution.

Common use cases

Step-by-step integration

1. 1

   Set up Pardot API access

   In Salesforce, create or use an Account Engagement business unit, then copy the Pardot Business Unit ID from Setup. Create a Salesforce Connected App with OAuth scopes such as api and refresh_token, offline_access. Pardot's current API flow uses Salesforce OAuth, not a standalone Pardot API key, so you'll need a client ID, client secret, refresh token, login URL, and business unit ID.

2. 2

   Install the integration dependencies

   For a TypeScript webhook handler or Sanity Function, install @sanity/client and use Node's fetch API, or install node-fetch if your runtime needs it. Keep Salesforce OAuth credentials and the Pardot Business Unit ID in environment variables, not in Sanity documents.

3. 3

   Model Pardot fields in Sanity Studio

   Add fields to campaign-focused schemas, such as pardot.campaignId, pardot.formHandlerUrl, pardot.listId, pardot.scoringCategory, gatedAsset, ctaLabel, ctaUrl, audience, region, and funnelStage. Use validation rules for required Pardot fields so editors can't publish a gated page without the IDs needed by the integration.

4. 4

   Create the sync trigger

   Add a GROQ-filtered webhook or Sanity Function trigger that runs on publish for only the document types Pardot needs. For example, trigger on campaignLandingPage, webinar, and gatedResource documents where a Pardot campaign ID is present.

5. 5

   Call the Pardot API from server-side code

   In the handler, fetch the full Sanity document with GROQ, request a Salesforce OAuth access token, then call the Pardot Account Engagement API. Use the Pardot-Business-Unit-Id header on API requests. For prospect flows, call the v5 prospect and list membership endpoints. For tracked content links, create or update Pardot custom redirects.

6. 6

   Test the frontend and reporting path

   Publish a test campaign page, confirm the webhook fires, confirm the Pardot API response, submit a test form, and verify the prospect activity in Pardot. Check the Salesforce campaign attribution before rolling the flow out to production campaigns.

How Sanity + Pardot works

CMS approaches to Pardot

Keep building

Explore related integrations to complete your content stack.