Adobe Experience Platform release notes
Release date: June 21, 2023
Updates to existing features in Adobe Experience Platform:
- Authentication to Experience Platform APIs
- Data collection
- Destinations
- Experience Data Model (XDM)
- Query Service
- Sources
Authentication to Experience Platform APIs
For Experience Platform API users, the method to obtain required access tokens to authenticate and make calls to API endpoints is now simplified. The JWT method to obtain access tokens is deprecated and replaced by a simpler OAuth Server-to-Server authentication method.
While existing API integrations using the JWT authentication method will continue to work until January 1st, 2025, Adobe strongly recommends that you migrate existing integrations to the new OAuth Server-to-Server method before that date. Read the guide on migrating from Service Account (JWT) credential to OAuth Server-to-Server credential.
Read the updated Experience Platform authentication tutorial for more information.
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
| Type | Feature | Description |
|---|---|---|
| Extension | Google Cloud Platform event forwarding extension | The Google Cloud Platform event forwarding extension allows you to forward event data to Google for activation via Google Pub/Sub. |
| Secret | OAuth 2 JWT Secret | The OAuth 2 JWT Secret allows you to use Adobe and Google Service tokens to support server-server interactions in event forwarding. |
To learn more about data collection, read the data collection overview.
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 or updated destinations
| Destination | Description |
|---|---|
| The Amazon Ads integration with Adobe Experience Platform now supports regional routing to the various Amazon Ads marketplaces. Read more in the destination changelog. |
New or updated functionality
| Functionality | Description |
|---|---|
| Workspace support for Adobe Target destinations. | You can now select the Adobe Target workspace that you want to share audiences to, when configuring a new Adobe Target destination connection. See the connection parameters section for more information. Additionally, see the tutorial on configuring workspaces in Adobe Target for more information about workspaces. |
For more general information on destinations, refer to the destinations overview.
Experience Data Model (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 XDM components
| Component type | Name | Description |
|---|---|---|
| Extension (Prospect-Profile) | Adobe Unified Profile Service Prospect-Profile Union Extension | Added required fields for the Prospect-Profile union schema. |
| Extension | Decisioning Asset | Add a data type to represent assets used in decisioning. Decisioning Asset provides a reference to assets used to render the decisionItems. |
| Data type | Commerce | Commerce stores records related to the buying and selling activity. |
| Field group | Profile Partner Enrichment(Sample) | A sample schema was added for profile partner enrichment. |
| Field group | Partner Prospect Details(Sample) | A sample schema was added for data vendor prospect profile extensions. |
| Data type | Commerce Scope | Commerce Scope identifies where an event occurred. For example, in the store view, the store, or website, and so on. |
| Data type | Billing | Billing information, for one or more payments, was added to the Commerce schema. |
Updated XDM components
| Component type | Name | Update description |
|---|---|---|
| Field group | MediaAnalytics Interaction Details | Changed bitrateAverageBucket from 100 to “800-899”. |
| Data type | Qoe Data details information | Changed bitrateAverageBucket data type to string. |
| Field Group | Segment Membership Details | Added to Prospect Profile class. |
| Schema | Computed Attributes System Schema | Identity map added to the Computed Attributes System Schema. |
| Datatype | Content Delivery Network | Field added to Session details information to describe the content delivery network used. |
| Extension | Adobe Unified Profile Service Account Union Extension | Identity map added to the Adobe Unified Profile Service Account Union Extension. |
| Data type | Order | discountAmount was added to Order. This conveys the difference between the regular order price and the special price. It is applied to the entire order rather than to individual products. |
| Schema | AEP Hygiene Operation Request | The targetServices field was added to provide the names of services that process the data hygiene operations. |
| Data type | Shipping | currencyCode was added to the shipping information for one or more products. It is an ISO 4217 alphabetic currency code used for pricing the product. |
| Data type | Application | The language field was added to provide the user’s linguistic, geographical, or cultural preferences to the application. |
| Extension | AJO Entity Fields | AJO Timestamp Entity was added to indicate the time when the message was last modified. |
| Data type | (Multiple) | Removed several media details across several data types for consistency. |
For more information on XDM in Platform, see the XDM System overview
Query Service
Query Service allows you to use standard SQL to query data in Adobe Experience Platform data lake. You can join any datasets from data lake and capture the query results as a new dataset for use in reporting, Data Science Workspace, or for ingestion into Real-Time Customer Profile.
Updated features
| Feature | Description |
|---|---|
| Inline templates | Query Service now supports the use of templates that reference other templates within your SQL. Reduce your workload, and avoid errors by leveraging inline templates in your queries. You can reuse statements or conditions, and reference nested templates for greater flexibility in your SQL. There is no limit in the size of queries that can be stored as templates, or the number of templates that can be referenced from your original query. For more information, read the inline template guide. |
| Scheduled query UI updates | Manage all your scheduled queries from one location in the UI with the Scheduled Queries tab. The Scheduled Queries UI has been improved with the addition of inline query actions and the new query status column. The recent additions include the ability to enable, disable, and delete a schedule, or subscribe to alerts for upcoming query runs directly from the Scheduled Queries view.
|
For more information on Query Service, refer to the Query Service overview.
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.
Updated features
| Feature | Description |
|---|---|
| Adobe Analytics classification source dataflows deletion support | You can now delete source dataflows that use Adobe Analytics classifications as its source. Under Sources > Dataflows, select the desired dataflow, then select delete. For more information, read the guide on creating a source connection for Adobe Analytics classifications data. |
| Filtering support for Microsoft Dynamics using the API | Use logical and comparison operators to filter row-level data for the Microsoft Dynamics source. For more information, read the guide on filtering data for a source using the API. |
| You can now use the RainFocus sources integration to bring event management and analytics data from your RainFocus account to Experience Platform. For more information, read the RainFocus source overview. | |
| Support for Adobe Commerce | You can now use the Adobe Commerce sources integration to bring data from your Adobe Commerce account to Experience Platform. For more information, read the Adobe Commerce source overview. |
| Support for Mixpanel | You can now use the Mixpanel sources integration to bring analytics data from your Mixpanel account to Experience Platform using APIs or the user interface. For more information, read the Mixpanel source overview. |
| Support for Zendesk | You can now use the Zendesk sources integration to bring customer success data from your Zendesk account to Experience Platform using APIs or the user interface. For more information, read the Zendesk source overview. |
To learn more about sources, read the sources overview.
