Account Engagement tracks visitor and prospect activities on your website and landing pages by setting cookies on their browsers. Cookies are set to remember preferences (like form field values) when a visitor returns to your site. We also set a cookie for logged-in users to maintain the session and remember table filters.
Account Engagement sets first-party cookies for tracking purposes and sets third-party cookies for redundancy. Using first-party and third-party cookies together is standard in the marketing automation industry. We don’t store personally identifying information, only a unique identifier. First-party cookies are set on Account Engagement domains and tracker subdomains. If you don’t have a tracker subdomain configured, we use third-party cookies on HTTPS pages.
To ask visitors to consent to tracking enable tracking opt-in preferences.
| Name | Details |
|---|---|
| visitor_id<accountid> | The visitor cookie includes a unique visitor ID and the unique identifier for your business unit. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct business unit. The visitor value is the visitor_id in your business unit. This cookie is set for visitors by the Account Engagement tracking code. |
| pi_opt_in<accountid> | If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a true or false value when the
visitor opts in or out of tracking. If a visitor opts in, the value is set to true, and the visitor is cookied and tracked. If the visitor opts
out or ignores the opt-in banner, the opt-in cookie value is set to false. The visitor cookie is disabled, and the visitor isn’t tracked. |
| visitor_id<accountid>-hash | The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor and access corresponding prospect information. |
| lpv<accountid> | This LPV cookie is set to keep us from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view. |
| pardot | A session cookie named pardot is set in your
browser while you’re logged in as a user or when a visitor accesses a form, landing page, or
page with Account Engagement tracking code. The cookie denotes an active session and isn’t
used for tracking. |