Account Export API
The Marketing Cloud Personalization Account Export API helps you retrieve account-level data from datasets such as segments, engagement scores, change in engagement scores, and customer activity for use in other systems.
Your Personalization contract defines the volume of records you can export using the Account Export API. For more information, refer to your contract or contact your account representative.
Account Profiles was retired in August 2024. For more information, see Personalization Account Profiles Retirement.
Export account data from a Personalization dataset.
GET /api/dataset/<datasetId>/accounts.< json | csv >
https://<accountName>.<instance>.evergage.com/api/dataset/<datasetId>/accounts.< json | csv >
| URL Parameter | Required? | Description |
|---|---|---|
accountName | Yes | The Personalization account name. You can find the accountName by accessing Gears from the Personalization UI and reviewing the URL. For example, if the Gears URL is https://demo.us-1.evergage.com/, then the account name is demo. |
instance | Yes | The Personalization instance identifier. You can find this value by accessing Gears from the Personalization UI and reviewing the URL. For example, if the Gears URL is https://demo.us-1.evergage.com/, then the instance identifier is us-1. |
datasetId | Yes | The name or identifier of the Personalization dataset you’re exporting account data from. |
filter | No | Optional Segment name or ID |
start | No | Optional start time in epoch milliseconds used for engagement statistics |
end | No | Optional end time in epoch milliseconds used for engagement statistics |
segmentationId | No | Optional segmentation identifier |
segmentId | No | Optional segment identifier |
pageSize | No | Number of records to return. Returns all records unless specified. |
page | No | Page number of records to show, starting at zero for the first page. Starts at zero unless specified. |
Authorization: Basic <base64-encoded-API-token>
The Account Export API uses API tokens to authenticate requests. Your API token must be a strict Base64 encoding of your API Key ID and its API Secret Key, separated by a colon. You can use an existing API token if it has the required permissions. Alternatively, you can ask an account administrator to generate a new one from the Personalization UI. For more information on API tokens, see Personalization API Tokens on Salesforce Help.
Alternatively, if you use cURL to interact with the API, you can send your API Key ID and its API Key Secret using the -u "apiKeyId:apiKeySecret" command-line option. cURL automatically converts the apiKeyId:apiKeySecret pair into a Base64-encoded string and adds the Authorization: Basic <base64-encoded-API-token> to the request header. For an example of how to pass your API credentials in a cURL request, refer to the Example section in this article.
The following is an example GET request sent using cURL that retrieves account data in the JSON format from the specified Personalization dataset.
The following example request passes API credentials using the -u command-line option.
The preceding example cURL request generates the following example response in the JSON format.
- Salesforce Help: Personalization API Tokens