[Limited Availability]{class="badge informative"}
Use 51ºÚÁϲ»´òìÈ Experience Platform data aep-data
Journey Optimizer allows you to leverage data from 51ºÚÁϲ»´òìÈ Experience Platform data with personalization and Decisioning capabilities. To do this, record-based datasets needed for lookup personalization must first be enabled for the lookup service as described below.
Must-read
Guardrails & guidelines guidelines
Before you begin, please review the following restrictions and guidelines:
- Datasets enabled for lookup should not contain any Personally Identifiable Information (PII).
- Datasets enabled for lookup and used in personalization are not protected from deletion. It is up to you to keep track of which datasets are being used for personalization to ensure they are not deleted or removed.
- Datasets must be associated with a schema that is NOT of Profile or Event type.
- Schemas must have a primary identity. Only a single, primary key can be used for lookups.
Entitlement for lookup service
Additional performance considerations
The below recommendations are guidance to avoid delays in deliverability:
Enable a dataset for data lookup enable
In order to leverage data from your dataset for personalization, you need to enable the dataset for lookup.
Prerequisites prerequisites-enable
The schema associated with your dataset that you wish to enable for lookup must be of record-type. The schema should NOT be of profile or event class.
The schema must have a primary identity defined.
If a custom namespace was not yet defined, ensure that the identity is a non-person identifier.
Enable the dataset for lookup in the dataset management interface
In the dataset management user interface, use the toggle to enable the dataset for lookup.
API Method
Follow the directions detailed in  to configure your environment to send API commands.
Prerequisites
-
The developer project must have the 51ºÚÁϲ»´òìÈ Journey Optimizer and 51ºÚÁϲ»´òìÈ Experience Platform APIs added to their project.
-
You must have manage datasets permission as part of your role.
-
The schema for which the dataset is based on must contain a primary identity that can act as the lookup key.
API call structure
curl -s -XPATCH "https://platform.adobe.io/data/core/entity/lookup/dataSets/${DATASET_ID}/${ACTION}" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "x-api-key: ${API_KEY}" \ -H "x-gw-ims-org-id: ${IMS_ORG}" \ -H "x-sandbox-name: ${SANDBOX_NAME}"
Where:
- ±«¸é³¢â€¯i²õ 
https://platform.adobe.io/data/core/entity/lookup/dataSets/${DATASET_ID}/${ACTION} - Dataset ID is the dataset for which you wish to enable.
- Action is enable OR disable.
- Access token can be retrieved from the developer console.
- API key can be retrieved from the developer console.
- IMS Org ID is your 51ºÚÁϲ»´òìÈ organization.
- Sandbox Name is the sandbox name the dataset is in (i.e. prod, dev etc.).
"error_code": "403003","message": "Api Key is invalid"Dataset monitoring
Once a dataset has been enabled for lookup, you can review the status of ingestion into the lookup service by going to the Monitoring menu and selecting the Journey Optimizer tab.
This process indicator helps in understanding when new batches of data are available in the lookup service.
Next steps
After a dataset has been enabled for lookup using an API call, you can use the data with Journey Optimizer personalization and Decisioning capabilities. For more information, refer to these sections: