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.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- 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.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | First-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 area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk (default configuration) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Support marketing analytics | Support marketing analytics; Receive personalised marketing offers |
| 2 | Tracking domain | Settings > First-Party Tracking; Domain Management | First-party tracker domain only | First-party with third-party redundancy |
| 3 | Consent | Tracking & Consent API; pi_opt_in | Set after Consenter consent | Set after Consenter consent |
| 4 | Prospect identification | Forms, email link tracking | Not used | Used |
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 field | Configuration A — Medium risk | Configuration B — Higher risk (default configuration) |
|---|---|---|
| Processing purposes | Support marketing analytics | Support marketing analytics, Receive personalised marketing offers |
| Tracking method | First party tracking (cross-session) | Third party tracking (crosssession, cross-website) |
| Identifier | Device identifiers | Device identifiers, Direct identifier |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address, Privacy choices | As A, plus direct identifier, User-provided data, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | Profile based |
| Maximum storage duration | Per cookie settings | Per cookie settings |
| Processing location | Contract region; United States | Contract 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