Release date: April 27, 2022
Updates to existing features in Adobe Experience Platform:
Platform provides multiple dashboards through which you can view important information about your organization’s data, as captured during daily snapshots.
Dashboards provide pre-configured reporting options for your organization’s data and are built directly into the marketer workflow within Platform. These dashboards are available without the need for additional IT support or the time and effort it would otherwise take to export and process data with additional data warehousing design and implementation.
The following widgets are available through the Widget library on their respective dashboards. See the documentation for more information on how to add widgets through the Widget library.
|Profiles added trend||Profiles||This widget uses a line graph to illustrate the total number of merged profiles that have been added to the Profile Store daily over the last 30 days, 90 days, or 12 months.|
|Audiences mapped to destination status||Profiles||This widget displays the total number of both mapped and unmapped audiences in a single metric and uses a doughnut chart to illustrate the proportional difference between their totals.|
|Audiences size||Profiles||This widget provides a two-column table that lists up to 20 segments and the total number of audiences contained in each segment. The list is dependent on the merge policy applied and ordered from high to low according to the total number of audiences.|
|Profile count trend||Profiles||This widget uses a line graph to illustrate the trend in the total number of profiles contained in the system over time. The data can be visualized over 30 days, 90 days, and 12 month periods.|
|Single identity profiles by identity||Profiles||This widget uses a bar chart to illustrate the total number of profiles that are identified with only a single unique identifier. The widget supports up to five of the most commonly occurring identities.|
|Destination status||Destinations||This widget displays the total number of enabled destinations as a single metric and uses a doughnut chart to illustrate the proportional difference between enabled and disabled destinations.|
|Active destinations by destination platform||Destinations||This widget uses a two-column table to show a list of active destination platforms and the total number of active destinations for each destination platform.|
|Activated audiences across all destinations||Destinations||This widget provides the total number of audiences activated across all destinations in a single metric.|
|Audience activation order||Segments||This widget provides a three-column table that lists the destination name, the platform, and the activation date of the audience.|
|Audience size trend||Segments||This widget provides a line graph illustration for the total number of profiles that meet the criteria of any segment definition over 30 days, 90 days, and 12 month periods.|
|Audience size change trend||Segments||This widget provides a line graph illustration of the difference in the total number of profiles that qualified for a given segment between the most recent daily snapshots. The period of trend analysis can be visualized over 30 days, 90 days, and 12 month periods.|
|Audience size trend by identity||Segments||This widget illustrates the audience size trend for a particular segment based on a selected identity type. The period of trend analysis can be visualized over 30 days, 90 days, and 12 month periods.|
|Orphaned profile segment membership cleanup||Profiles and License Usage||Profile Service now removes leftover segment members on a daily basis to give a more accurate representation of your profiles in your system. This clean up occurs after all the profile fragments for a given profile are deleted. This may show a drop in the “Addressable audience” metric in the license usage dashboard and may show a drop in the “Profile count” metric in the Profile dashboard, since these metrics included leftover segment fragments prior to this release.|
In Platform, data is ingested from many different sources, analyzed within the system, and activated to a wide variety of destinations. Platform makes the process of tracking this potentially non-linear flow of data easier by providing transparency with dataflows.
Dataflows are a representation of jobs that move data across Platform. These dataflows are configured across different services, helping move data from source connectors to target datasets, where it is then utilized by Identity Service and Real-time Customer Profile before ultimately being activated to destinations.
|Segments dashboard||You can now use the monitoring dashboard to monitor dataflows for segments. To learn more, please read the guide on monitoring segments in the UI|
Data Prep allows data engineers to map, transform, and validate data to and from Experience Data Model (XDM).
|Support for Adobe Analytics source||The Adobe Analytics source now supports Data Prep features, allowing you to map your Analytics report-suite data to a target XDM schema when creating a dataflow. See the tutorial on creating an Analytics source connection for more information.|
|Support for importing existing mapping rules||You can now import mapping rules from an existing dataflow to accelerate your dataflow configurations and limit errors. See the tutorial on importing existing mapping rules for more information.|
For more information on Data Prep, please see the Data Prep overview.
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 or updated features
|Advanced Enterprise Destination Connectors||Three enterprise destination connectors are now generally available: Amazon Kinesis, Azure Event Hubs, and HTTP API.
The general availability of enterprise destination connectors includes all the capabilities offered previously in the Beta phase, and more:
|In-context alerts for destination dataflows||You can now subscribe to alerts when creating a destination dataflow, to receive alert messages regarding the status, success, or failure of your dataflow run. You can choose to receive alerts in the Experience Platform UI or via email.|
For the Amazon Kinesis, Azure Event Hubs, and HTTP API destinations, during the release process (starting April 27th), you will see both the former Beta destination card, as well as the new generally available (GA) destination card in the destinations catalog. Any dataflows configured by customers using the beta destinations will be migrated in the next couple of days to the GA version of the same destination. This migration should ultimately be completed by the end of day Friday April 29th. The Beta destinations will be continue to be visible during this short time-window and labeled as Deprecated.
If you have been utilizing these destinations in the Beta phase, please note the following:
|Criteo||Connect and activate data to the Criteo advertising platform.|
|Sendgrid||Connect and activate data to the Sendgrid platform for transactional and marketing emails.|
For more general information on destinations, refer to the destinations overview.
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.
|Add or remove individual standard fields for a schema||The Schema Editor UI now allows you to add portions of standard field groups to your schemas, providing more flexibility for the fields you choose to include without needing to build custom resources from scratch.
You can now also define ad-hoc custom fields directly within the schema structure and assign them to a new or existing custom field group without needing to create or edit the field group beforehand.
See the guide on creating and editing schemas in the UI for more information on these new workflows.
New XDM components
|Global schema||Data Hygiene Operation Request||Captures the details of a data cleansing request to delete or modify records in a specified dataset or sandbox.|
|Descriptor||Time-series Granularity Descriptor||Indicates the granularity of time-series and summary data. When applied to a schema, the schema’s
|Class||XDM Summary Metrics||Provides pre-summarized metrics with grouping dimensions, such as the results of an SQL SELECT with a GROUP BY.|
|Field group||Consent policies evaluation results map||Captures the consent policy evaluation result for an individual.|
|Field group||Site Search||Captures site-search related information such as search query, filtering, and ordering.|
|Field group||Merge Leads||Captures the details of an event where two or more leads are merged.|
|Field group||Email Sent||Captures the details of an event where an email is sent to a recipient.|
|Field group||Stitching Fields||Captures values computed through the identity stitching process for an event.|
|Field group||Secondary Recipient Detail For Audit||An Adobe Journey Optimizer field group that captures a secondary recipient detail for an audit.|
|Field group||XDM Business Account Person Relation Details||Captures details related to an account-person relationship.|
|Field group||Account Person Details||Captures details related to an account-person relationship.|
|Data type||Cart||Captures information about an e-commerce shopping cart.|
|Data type||Shipping||Captures shipping information for one or more products.|
|Data type||Site Search||Captures information on site-search activity.|
|Extension (Workfront)||Operational Task Attributes||Captures details related to an operational task.|
|Extension (Workfront)||Work Portfolio Attributes||Captures details related to a work portfolio.|
|Extension (Workfront)||Work Program Attributes||Captures details related to a work program.|
|Extension (Workfront)||Work Project Attributes||Captures details related to a work project.|
Updated XDM components
|Component type||Name||Update description|
|Global schema||Destinations||New enum values for
|Descriptor||Friendly Name Descriptor||Added support for removing suggested values (
|Field group||User Login Process||
|Data type||Commerce||Several cart-related fields have been added.|
|Data type||Product list item||New fields added for selected options and discount amount.|
|Extension (Intelligent Services)||Intelligent Services JourneyAI Send Time Optimization||Optimize storage format for send-time scores.|
|Extension (Workfront)||Workfront Change Event||Several fields replaced with a
|Extension (Workfront)||Work Task Attributes||Several fields added.|
|Extension (Workfront)||Work Object||New fields for parent object type and custom form fields.|
For more information on XDM in Platform, see the XDM System overview.
AI/ML services empower marketing analysts and practitioners to leverage the power of artificial intelligence and machine learning in customer experience use cases. This allows for marketing analysts to set up predictions specific to a company’s needs using business-level configurations without the need for data science expertise.
Attribution AI is used to attribute credits to touchpoints leading to conversion events. This can be used by marketers to help quantify the marketing impact of each individual marketing touchpoint across customer journeys.
|Support for Multi Dataset||The Multi Dataset feature now supports all Experience Event datasets as well as the selection of Identity Map as an identity. Customers can select the Identity Map and any associated IDs as long as there is a common identity namespace across datasets. Attribution AI supports the following schemas: Adobe Analytics, Experience Event, Consumer Experience Event. For more information on Multi Dataset support in Attribution AI, refer to the Attribution AI user guide.|
For more information on Intelligent Services, please see the Intelligent Services overview.
Customer AI available in 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.
|Support for Multi Dataset||The Multi Dataset feature now supports all Experience Event datasets as well as the selection of Identity Map as an identity. Customers can select the Identity Map and any associated IDs as long as there is a common identity namespace across datasets. Customer AI supports the following schemas: Adobe Analytics, Experience Event, Consumer Experience Event, and the Adobe Audience Manager schema. For more information on Multi Dataset support in Customer AI, refer to the Customer AI user guide.|
|New model evaluation metrics in Customer AI||New Gains charts in Customer AI allow marketers to determine the group size to target based on their budget and ROI goals. New Lift charts measure the quality of the model, providing better visibility into the lift they would get over random targeting. For more information, see the discover insights with Customer AI document.|
For more information on Intelligent Services, please see the Intelligent Services overview.
Built on Real-time Customer Data Platform (Real-time CDP), Real-time CDP B2B Edition is purpose-built for marketers operating in a business-to-business service model. It brings together data from multiple sources and combines it into a single view of people and account profiles. This unified data allows marketers to precisely target specific audiences and engage those audiences across all available channels.
||All Marketo datasets except
To learn more about Real-time Customer Data Platform B2B Edition, see the B2B overview.
Adobe Experience Platform can ingest data from external sources while allowing 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.
|Support for OneTrust Integration||You can now use the OneTrust Integration source to ingest consent and preferences data from your OneTrust account to Platform. See the documentation on creating a OneTrust Integration source connection for more information.|
|Support for Square||You can now use the Square source to ingest payments data from your Square account to Platform.|
|Support for deleting Customer Attributes dataflows||You can now delete dataflows created with the Customer Attributes source connector.|
To learn more about sources, see the sources overview.