Marketing Cloud Account Engagement (formerly Pardot)

Business software

Built when you ask for it

Sync Marketing Cloud Account Engagement prospect, campaign, email, and form data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Marketing Cloud Account Engagement connector syncs your B2B marketing automation data into analytics-ready tables in your data warehouse. Pull prospects, campaigns, emails, forms, and visits from the API (formerly Pardot), with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Prospects
  • Campaigns
  • Emails
  • Forms
  • Visits

How it gets built

  1. Choose Marketing Cloud Account Engagement (formerly Pardot) when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Marketing Cloud Account Engagement (formerly Pardot)'s documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Marketing Cloud Account Engagement (formerly Pardot) itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

OAuth 2.0 (Salesforce connected app). Create a Salesforce Connected App and complete an OAuth authorization flow; there's no static API key.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Marketing Cloud Account Engagement (formerly Pardot) connector?
Not as a finished connector yet. Ingest builds it from Marketing Cloud Account Engagement (formerly Pardot)'s own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Marketing Cloud Account Engagement (formerly Pardot) data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Marketing Cloud Account Engagement (formerly Pardot) API documentation: https://developer.salesforce.com/docs/marketing/pardot/overview

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Marketing Cloud Account Engagement (formerly Pardot)