Guardrails
Journey Optimizer Guardrails Product Link
Guardrails and End to End Latency Guidance
Implementation steps
Adobe Experience Platform
Schema/datasets
- Configure individual profile, experience event, and multi-entity schemas in Experience Platform, based on customer-supplied data.
- Create Experience Event class-based schemas for Adobe Campaign broadLog, trackingLog and non-deliverable addresses tables (optional).
- Create datasets in Experience Platform for data to be ingested.
- Add data usage labels in Experience Platform to the dataset for governance.
- Create policies that enforce governance on destinations.
Profile/identity
- Create any customer-specific namespaces.
- Add identities to schemas.
- Enable the schemas and datasets for Profile.
- Set up merge policies for differing views of Real-time Customer Profile (optional).
- Create segments for Journey usage.
Sources/destinations
- Ingest data into Experience Platform using streaming APIs & source connectors.
Journey Optimizer
- Configure your Experience Platform datasource and determine what fields should be cached as part of the profileStreaming data used to initiate a customer journey must be configured within Journey Optimizer first to get an orchestration ID. This orchestration ID is then supplied to the developer to use with ingestion
- Configure external data sources
- Configure custom actions for Campaign instance