Release Notes

December 2024

We have removed the optional Sync External Activities toggle from the connector setup form and now sync the EXTERNAL_ACTIVITY table if you provide the required scopes for the /external-activities endpoint. We make API calls to the endpoint to validate the scopes, and if the calls succeed, we sync the EXTERNAL_ACTIVITY table. For more information, see Pardot documentation.

You must continue to specify the Set up API rate limit for External Activities for the /external-activities endpoint.

If your schema change handling configuration settings is Allow all, we will sync the EXTERNAL_ACTIVITY table to your destination.

July 2024

We have added a new field, Historical Sync Limit, to the connector setup form. This allows you to select the time range for which historical data should be synced. The default value is ALL_TIME. For an existing connector, you can edit the connection details and set the time frame value. We have also added support for the timeframe_months field for connectors created using the Create a Connector endpoint. For more information, see our REST API config.

The historical sync limit only applies to the following tables:

• EMAIL
• LIST_MEMBERSHIP
• VISITOR_ACTIVITY
• VISITOR_PAGE_VIEW

For more information, see our Pardot documentation.

We have added a new table, EXTERNAL_ACTIVITY. For more information, see Pardot's API documentation for the external-activites endpoint.

We will gradually roll out this change to all connectors. The table can be selected by selecting the toggle in the setup form. Refer to Pardot's setup guide for more information.

May 2024

We have added a new table, EMAIL_TEMPLATE with the following child tables:

• REPLY_TO_OPTION
• SENDER_OPTION

April 2024

We have upgraded the following tables of our Pardot connector to version 5 of the Pardot API.

• CAMPAIGN
• LIST
• LIST_MEMBERHSIP
• VISIT
• VISITOR
• VISITOR_ACTIVITY
• VISITOR_PAGE_VIEW

As part of the upgrade, we have made the following schema changes:

• Added the following new columns to the CAMPAIGN table:

  • created_at
  • created_by_id
  • folder_id
  • parent_campaign_id
  • salesforce_id
  • updated_at
  • updated_by_id

• Added the following new columns to the LIST table:

  • campaign_id
  • created_by_id
  • folder_id
  • updated_by_id

• Added the following new columns to the LIST_MEMBERSHIP table:

  • created_by_id
  • updated_by_id

• Added the following new columns to the VISITOR table:

  • campaign_id
  • do_not_sell
  • is_identified

• Added the following new columns to the VISITOR_ACTIVITY table:

  • custom_redirected_id
  • updated_at

• Added the following new columns to the VISITOR_PAGE_VIEW table:

  • campaign_id
  • duration_in_seconds
  • salesforce_id
  • visitor_id

• Deprecated the is_crm_visible column from the LIST table.

We have added a new table CUSTOM_FIELD with the following columns:

• created_at
• created_by_id
• field_id
• id
• is_analytics_synced
• is_record_multiple_responses
• is_required
• is_use_values
• name
• salesforce_id
• type
• updated_at
• updated_by_id

We are gradually rolling out this improvement to all existing connectors.

January 2024

We now perform rollback syncs with a window of three days to capture all the updates made to the EMAIL_TAG table. This addresses the issue where email sent_at dates occurring after their related tag created_at dates led to missed updates. In some cases, if the difference between the email sent_at dates and the related tag object created_at date is more than three days, the email tag objects may not be synced. To resolve this issue, contact our support team.

We are gradually rolling out this improvement to all the existing connectors.

September 2023

We now capture deletes for the LIST_MEMBERSHIP table. We are gradually rolling out this feature to all existing connectors.

May 2023

We have added a new table, LIST_EMAIL, to store the details of your sent emails.

We can now sync the EMAIL table into your destination using the Pardot API version 5 endpoints.

January 2023

We now sync the permanently deleted records of the PROSPECT table. We set the is_permanently_deleted column for the permanently deleted records to true. To capture these deletes, we perform a full re-sync of the PROSPECT table on weekends.

You can now sync the custom properties of the LIST and MAP data types in the PROSPECT table.

December 2022

We have added a new table, LIST_EMAIL, which stores the text and HTML content of emails. For more information about the table, see Pardot's documentation.

We have added the following new columns to the EMAIL table:

• campaign_id
• client_type
• created_by_id
• list_email_id
• list_id
• prospect_id
• sent_at We are gradually rolling out this feature to all existing connectors.

February 2021

The Pardot connector now supports authorization using Salesforce OAuth. You can now authenticate with an SSO-enabled user account. See our setup instructions for more details.

New connectors created after February 16, 2021, will support this new functionality by default.

January 2021

In your connector setup form, you can now limit the REST API calls that your Pardot connector makes per day. By default, the REST API call limit is 150,000 per day.

We have released pre-built, dbt Core-compatible data models for Pardot. Find the model in Fivetran's dbt hub. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.

The Pardot connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Pardot's priority-first syncs fetch the most recent 14 days' worth of data from the EMAIL, VISIT, and VISITOR_ACTIVITY tables. To learn more, see our priority-first sync documentation.

March 2020

We now sync custom fields to the PROSPECT_ACCOUNT table in JSON format.

November 2019

We have fixed a bug in our Pardot connector. Previously, we only synced visitors flagged as "Identified," because by default, the visitor endpoint we use to sync visitors only syncs visitors flagged as "Identified." We have changed the setting and now sync all visitors.

Because of this bug, there may be a mismatch between the list of visitors in your Pardot dashboard and in the VISITOR table in your destination. If you notice a mismatch, you need to re-sync the VISITOR table to fix it. Contact support to trigger a re-sync.

August 2019

We have deprecated the VISITOR_REFERRER table from our schema because the Pardot API does not provide us with information to populate this table.

July 2018

We have added custom_* columns to the CAMPAIGN table.