Capability Requirements Addressed
6 min
Most requirements from the Proof of Concept (POC) Objectives document were demonstrated through use case scenarios. Below, we highlight several items that may not have been explicitly addressed.
Data Integration
- Bidirectional connectivity with Amazon S3 was demonstrated during use case presentations. Adobe Experience Platform (AEP) also supports integration with Snowflake, sFTP, and Databricks.
- Note: Databricks does not have a preconfigured destination, but data can be sent via a cloud storage destination.
- Metric limitations were outlined in the presentation deck.
- Batch and streaming ingestion capabilities were shown in both use case demonstrations and the data foundation overview.
- Federated Audience Composition was presented onsite, illustrating how it minimizes data copying for CDP use cases—addressing the "zero copy" requirement.
Identity Resolution and Data Unification
- The ID graph and deterministic identity matching across all data sources were demonstrated.
- Native RT-CDP does not use probabilistic matching, but such capabilities are available through partner integrations.
- In the Sign-up for Updates use case, we demonstrated stitching a known profile with a new anonymous cookie ID. The initial stitch occurs within minutes of login, after which audience qualifications are updated in real time.
Campaign Orchestration
- Several use cases utilized Adobe Journey Optimizer (AJO) campaign and journey features, supporting calendar, event, and real-time triggers, as well as multi-channel delivery (e.g., SMS and email). All orchestration requirements were covered in the demonstrations.
Activation Tracking
- Activated audiences can be sent to a Stellantis-owned S3 bucket or other cloud storage solution for tracking and logging. RT-CDP supports scheduling and custom file naming to meet specific requirements.
- Activations via AJO benefit from comprehensive reporting in both AJO and Customer Journey Analytics (CJA) interfaces.
Audience Management
- Audience counts and estimates are available during audience creation, as shown in the demonstrations.
- Multi-value attributes are supported in RT-CDP. For the POC, multiple emails per individual are not typically applicable; each new email creates a new profile unless stitched via another identifier (e.g., phone). In these cases, merge policies determine which email is set as the personal address.
API Access & Personalization Support
- API access to CDP for real-time profiles was demonstrated.
- Performance limits (e.g., requests per second) are not published in Experience League documentation.
Application of AI for Orchestration and Analytics
- The POC solutions were orchestrated manually, not by autonomous AI agents.
- Upcoming AI-driven orchestration capabilities were discussed during the onsite presentation.
- The AI Assistant, a conversational agent within the AEP interface, is currently available to provide support and assistance.
Analytics
- Many destinations are pre-configured in AEP to receive data from the platform.
- Audience data can be sent to other destinations, including cloud storage for integration with solutions like Databricks.
- Datasets can be exported for further data science or statistical analysis.
- Power BI can be integrated for reporting within AEP dashboards.
Data Governance
- Governance capabilities in AEP include field labeling and privacy policy configuration for various marketing actions.
- Policies ensure only appropriate fields are sent to designated destinations.
- Extensive documentation is available on AEP data governance in Experience League.