Adobe Experience Platform release notes
Release date: January 25, 2023
Updates to existing features in Adobe Experience Platform:
Artificial Intelligence/Machine Learning Services ai-ml
Artificial Intelligence and Machine Learning services empower marketing analysts and practitioners to leverage the power of AI/ML in customer experience use cases. This allows for marketing analysts to set up predictions, without the need for data science expertise, specific to a company’s needs using business-level configurations.
Attribution AI
Attribution AI is used to attribute credits to touchpoints that lead to conversion events. This can be used by marketers to help quantify the marketing impact of each individual marketing touchpoint across customer journeys.
Updated features
Please see the AI/ML services overview for more information.
Customer AI
Customer AI for Real-Time Customer Data Platform, is used to generate custom propensity scores such as churn and conversion for individual profiles at scale. This is accomplished without having to transform the business needs to a machine learning problem, pick an algorithm, train, or deploy.
Updated features
Please see the AI/ML services overview for more information.
Assurance assurance
Adobe Assurance lets you inspect, proof, simulate, and validate how you collect data or serve experiences in your mobile app.
New or updated features
For more information about Assurance, please read the Assurance documentation.
Data collection data-collection
Adobe Experience Platform provides a suite of technologies that allow you to collect client-side customer experience data and send it to the Adobe Experience Platform Edge Network where it can be enriched, transformed, and distributed to Adobe or non-Adobe destinations.
New or updated features
The home page for Data Collection UI has been updated to include helpful onboarding information and links to streamline productivity. This includes:
- Documentation and recommended workflows to get started
- Recent properties, rules, and data elements
- Popular extensions
- New extension updates with a quick install feature
Destinations (updated February 2nd) destinations
Destinations are pre-built integrations with destination platforms that allow for the seamless activation of data from Adobe Experience Platform. You can use destinations to activate your known and unknown data for cross-channel marketing campaigns, email campaigns, targeted advertising, and many other use cases.
New destinations
With the release of EUID (European Unified ID), you are now seeing two The Trade Desk - CRM destinations in the destinations catalog.
- If you source data in the EU, please use the The Trade Desk - CRM (EU) destination.
- If you source data in the APAC or NAMER regions, please use the The Trade Desk - CRM (NAMER & APAC) destination.
New or updated functionality
Note: This functionality is available only to customers of Privacy and Security Shield, and those of Healthcare Shield.
:, Pipe, Semicolon ;) are now available for the new beta cloud storage destinations - (Beta) Amazon S3, (Beta) Azure Blob, (Beta) Azure Data Lake Storage Gen2, (Beta) Data Landing Zone, (Beta) Google Cloud Storage, (Beta) SFTP.Read about the supported file formatting options for file-based destinations.
unique: Use this parameter when you need to create a customer data field whose value must be unique across all destination dataflows set up by a user’s organization.For example, the Integration alias field in the Custom Personalization destination must be unique, meaning that two separate dataflows to this destination cannot have the same value for this field.
Fixes and enhancements
We fixed an issue in the behavior of mandatory attributes when exporting data files to batch destinations.
Previously, every record in the output files was verified to contain both:
- A non-null value of the
mandatoryFieldcolumn and - A non-null value on at least one of the other non-mandatory fields.
The second condition has been removed. As a result, you might be seeing more output rows in your exported data files, as shown in the example below:
Sample behavior before January 2023 release
Mandatory field: emailAddress
Input data to activate
| table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 | |
|---|---|
| firstName | emailAddress |
| John | john@acme.com |
| null | peter@acme.com |
| Jenifer | jennifer@acme.com |
| null | diana@acme.com |
Activation output
| table 0-row-2 1-row-2 2-row-2 | |
|---|---|
| firstName | emailAddress |
| John | john@acme.com |
| Jenifer | jennifer@acme.com |
Sample behavior after January 2023 release
Activation output
| table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 | |
|---|---|
| firstName | emailAddress |
| John | john@acme.com |
| null | peter@acme.com |
| Jenifer | jennifer@acme.com |
| null | diana@acme.com |
Validation is now enforced as follows in the UI and API when mapping fields in the activate destinations workflow:
-
Required mappings: If the destination has been set up by the destination developer with required mappings (for example, the Google Ad Manager 360 destination), then these required mappings need to be added by the user when activating data to the destination.
-
Duplicate mappings: In the mapping step of the activation workflow, you can add duplicate values in the source fields, but not in the target fields. See the table below for an example of allowed and forbidden mapping combinations.
table 0-row-3 1-row-3 2-row-3 Allowed/forbidden Source field Target field Allowed - email.address
- email.address
- emailalias1
- email alias2
Forbidden - email.address
- hashed.emails
- emailalias1
- emailalias1
For more general information on destinations, refer to the destinations overview.
Experience Data Model (XDM) xdm
XDM is an open-source specification that provides common structures and definitions (schemas) for data that is brought into Adobe Experience Platform. By adhering to XDM standards, all customer experience data can be incorporated into a common representation to deliver insights in a faster, more integrated way. You can gain valuable insights from customer actions, define customer audiences through segments, and use customer attributes for personalization purposes.
New or updated features
New XDM components
Updated XDM components
ID field has been renamed to name, and the previous name field is now friendlyName.selectionStrategy field which captures the details of a selection strategy.isAuthorized field to authorized, and updated its type to a string when it was previously a Boolean.journeyNodeID, journeyNodeName, and journeyModeType.For more information on XDM in Platform, see the XDM System overview.
Real-Time Customer Profile profile
Adobe Experience Platform enables you to drive coordinated, consistent, and relevant experiences for your customers no matter where or when they interact with your brand. With Real-Time Customer Profile, you can see a holistic view of each individual customer that combines data from multiple channels, including online, offline, CRM, and third party data. Profile allows you to consolidate customer data into a unified view offering an actionable, timestamped account of every customer interaction.
Upcoming deprecation
In order to remove redundancy in the segment membership lifecycle, the Existing status will be deprecated from the segment membership map at the end of March 2023. A follow-up announcement will include the exact deprecation date.
Post deprecation, profiles qualified in a segment will be represented as Realized and profiles disqualified will continue to be represented as Exited. This will bring parity with file-based destinations with Active and Expired segment statuses.
This change could impact you if you’re using enterprise destinations (Amazon Kinesis, Azure Event Hubs, HTTP API) and have automated downstream processes in place, based on the Existing status. Please review your downstream integrations if this is the case for you. If you are interested in identifying newly qualified profiles beyond a certain time, please consider using a combination of the Realized status and the lastQualificationTime in your segment membership map. For more information, please reach out to your Adobe representative.
To learn more about Real-Time Customer Profile, including tutorials and best practices for working with profile data, please begin by reading the Real-Time Customer Profile overview.
Segmentation Service segmentation
Segmentation Service defines a particular subset of profiles by describing the criteria that distinguishes a marketable group of people within your customer base. Segments can be based on record data (such as demographic information) or time series events representing customer interactions with your brand.
New or updated features
validUntil field during the ingestion of audience data.Exited state for more than 30 days, based on the lastQualificationTime field will be subject to deletion.For more information on Segmentation Service, please see the Segmentation overview.
Sources sources
Adobe Experience Platform can ingest data from external sources and allows you to structure, label, and enhance that data using Platform services. You can ingest data from a variety of sources such as Adobe applications, cloud-based storage, third-party software, and your CRM system.
Experience Platform provides a RESTful API and an interactive UI that lets you set up source connections for various data providers with ease. These source connections allow you to authenticate and connect to external storage systems and CRM services, set times for ingestion runs, and manage data ingestion throughput.