Salesforce Marketing Cloud Account Engagement

The Salesforce Marketing Cloud Account Engagement connector is a Palantir-provided driver for Salesforce Marketing Cloud Account Engagement.

To create a new Salesforce Marketing Cloud Account Engagement source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for Salesforce Marketing Cloud Account Engagement-specific configuration and networking. For the complete property reference, see the official Salesforce Marketing Cloud Account Engagement driver documentation ↗.

Configuration

The properties below are mandatory or recommended.

PropertyRequired?DescriptionDefault
BusinessUnitIDMandatoryYour Salesforce Marketing Cloud Account Engagement Business Unit ID (BU). Required when connecting via OAuth 2.0.
SchemaMandatorySpecify the Salesforce Marketing Cloud Account Engagement API version to use. SalesforcePardotV5 is the rebuilt API.SalesforcePardotV5
AuthSchemeRecommendedThe type of authentication to use when connecting to Salesforce Marketing Cloud Account Engagement.OAuthPassword
InitiateOAuthRecommendedSpecifies the process for obtaining or refreshing the OAuth access token, which maintains user access while an authenticated, authorized user is working.GETANDREFRESH
IsDemoAccountRecommendedWhether the provided account is a demo account or not.FALSE
OAuthClientIdRecommendedSpecifies the client Id that was assigned when the custom OAuth application was created. (Also known as the consumer key.) This ID registers the custom application with the OAuth authorization server.
OAuthClientSecretRecommendedSpecifies the client secret that was assigned when the custom OAuth application was created. (Also known as the consumer secret). This secret registers the custom application with the OAuth authorization server.
PasswordRecommendedThe password of the user that is SSO-enabled.
UserRecommendedThe user that is SSO-enabled.

Networking

The table below lists the domains that the source needs to be able to access in order to successfully run.

For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.

DomainRequired
pi.pardot.comIf IsDemoAccount=FALSE (default)
pi.demo.pardot.comIf IsDemoAccount=TRUE
login.salesforce.comIf UseSalesforceSandbox=FALSE (default)
<Site>.my.salesforce.comAlways. URL returned by API after authentication
test.salesforce.comIf UseSalesforceSandbox=TRUE