About Visitor Privacy API
Use the Visitor Privacy API to query visitor profile records from the Customer Data Hub.
Visitor Privacy V2 API is now deprecated. The Visitor Privacy V2 API will become obsolete, and will no longer be available, on October 2, 2024. For the current version, see the Visitor Privacy V3 API.
These requests can also be used in support of General Data Protection Regulation (GDPR) compliance to satisfy the requirement of responding to data subject access requests.
How it works
Server-side Editor permission within CDH permissions is required for this API. Visitor lookups are based on a Visitor ID attribute from your account.
Permission requirements
- Server-side editor permission
Limits and intended use
The Visitor Privacy API is intended to satisfy regulatory requirements such as GDPR and CCPA and is not designed for high volume usage. We recommend that you have a maximum of one (1) connection open to this API at any given time. Contact your account manager if you estimate that your usage will exceed 1000 API calls per day.
Authentication
The bearer token is used to authenticate all API calls and not the API key. The API key is only used in the authentication call.
See the Getting Started guide to learn about generating a bearer token from the API key.
This page was last updated: July 23, 2024