Pardot ETL Source

Pardot is a marketing automation platform owned by Salesforce. It helps businesses to attract, convert, and retain customers. It uses automation tools to power engagement campaigns designed to help companies generate leads and close sales.

In Gathr, it can be added as a source to help in fetching customers and prospects data and applying analytics on top of it.

Schema Type #

See the topic Provide Schema for ETL Source → to know how schema details can be provided for data sources.

After providing schema type details, the next step is to configure the data source.

Data Source Configuration #

Connection Name: Connections are the service identifiers. A connection name can be selected from the list if you have created and saved connection details for Pardot earlier. Or create one as explained in the topic - Pardot Source Connection →

Object: Pardot object to be queried should be selected. For example: customField, prospect, campaign, visitorActivity etc.

Query Filter: The possible options for Query Filter based on the Object selected are explained as follows:

updated_at: Option to filter the records that were updated during the specified Time Period for the selected Pardot object.

created_at: Option to filter the records that were created during the specified Time Period for the selected Pardot object.

id_greater_than: Option to fetch all records of the selected Pardot object. This mode is only recommended for Objects with lesser record count. For example: dynamicContent, form, lifecycleStage, tag, user, customField, customRedirect, campaign, list, opportunity and tagObject.

API Type: The possible options for API Type based on the Object selected are explained as follows:

Export: The export API should only be used while reading large volume of data from Pardot. For example: ListMembership, Prospect, ProspectAccount, Visitor, VisitorActivity.

Query: The Query API should only be used while reading small volume of data from Pardot.

Time Period: Option to choose the Time Period for which the data should be fetched, either based on Duration (i.e., number of days) or Time Range specified (i.e., start and end date).

Number of Days: Time (in days) should be provided to fetch records which were created or updated (as per Query Filter) during the specified time duration.

Start Date | End Date: Start Date and End Date along with Time should be provided to fetch records which were created or updated (as per Query Filter) during the specified time range.

Detect Schema #

Check the populated schema details. For more details, see Schema Preview →

Pre Action #

To understand how to provide SQL queries or Stored Procedures that will be executed during pipeline run, see Pre-Actions →).

Notes #

Optionally, enter notes in the Notes → tab and save the configuration.