Set up your bannerConfigure Your ToolsMarketing Automation and CRM

Salesforce Marketing Cloud Account Engagement (Pardot)

How to configure Salesforce Marketing Cloud Account Engagement (Pardot) at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Support marketing analytics, Receive personalised marketing offers

Overview

This guide explains how to implement different privacy configurations for Account Engagement (formerly Pardot) and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. The Account Engagement website tracking code and Tracking & Consent JavaScript API. Salesforce, Inc. is a US company.

What the service does in this scope. Account Engagement uses two cookies, visitor_id (with the account ID appended) and pi_opt_in. With first-party tracking, tracking moves from the Pardot domain to the customer's tracker domain; it was enabled by default for new business units from February 2023. Pardot sets first-party cookies for tracking and third-party cookies for redundancy. With the Tracking & Consent API (activated in Settings > Edit > Activate the Tracking & Consent JavaScript API), sendPageView makes no request if pi_opt_in is false. When a visitor converts (e.g. by form), activity is associated with a prospect record.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskFirst-party tracking only; anonymous visitor analytics; after consent.
Configuration B — Higher risk (default configuration)Tracking with third-party redundancy cookies; prospects identified via forms and email links; after consent.

No configuration without prior consent. Both cookies are persistent visitor identifiers.

Step 1 — Configure Account Engagement

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
1Processing purposesOperator decisionSupport marketing analyticsSupport marketing analytics; Receive personalised marketing offers
2Tracking domainSettings > First-Party Tracking; Domain ManagementFirst-party tracker domain onlyFirst-party with third-party redundancy
3ConsentTracking & Consent API; pi_opt_inSet after Consenter consentSet after Consenter consent
4Prospect identificationForms, email link trackingNot usedUsed

Step 2 — Map the configuration in the Consenter Manager

Processing location. Salesforce is a US enterprise subject to the US CLOUD Act; list the United States in all configurations, in addition to the hosting region in your contract.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk (default configuration)
Processing purposesSupport marketing analyticsSupport marketing analytics, Receive personalised marketing offers
Tracking methodFirst party tracking (cross-session)Third party tracking (crosssession, cross-website)
IdentifierDevice identifiersDevice identifiers, Direct identifier
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiers, IP address, Privacy choicesAs A, plus direct identifier, User-provided data, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationProfile based
Maximum storage durationPer cookie settingsPer cookie settings
Processing locationContract region; United StatesContract region; United States

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page