Release date: June 22, 2022
Updates to existing features in Adobe Experience Platform:
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.
|Access Type configuration for datastreams||When creating a new datastream, you can now select what type of requests you want the Edge Network to accept:
|Render propositions in single-page applications without incrementing metrics.||The newly added
|Mobile-to-web and cross-domain ID sharing||The Adobe Experience Platform Web SDK now supports visitor ID sharing capabilities that enable you to deliver personalized experiences more accurately, between mobile apps and mobile web content, and across domains.|
For more information on data collection in Platform, please see the data collection overview.
Data Science Workspace uses machine learning and artificial intelligence to unleash insights from your data. Integrated into Adobe Experience Platform, Data Science Workspace helps you make predictions using your content and data assets across Adobe solutions. One of the ways Data Science Workspace accomplishes this is through the use of JupyterLab. JupyterLab is a web-based user interface for Project Jupyter and is tightly integrated into Adobe Experience Platform. It provides an interactive development environment for data scientists to work with Jupyter notebooks, code, and data.
|JupyterLab Launcher||The JupyterLab Launcher now includes starters for Spark 3.2 notebooks. Spark 2.4 notebook starters are now replaced by Spark 3.2 notebooks and will be a part of this release.|
|Spark 3.2||New Scala (Spark) and PySpark recipes now use Spark 3.2|
|Kernels||Scala (Spark) notebooks are now authored via the Scala kernel. PySpark notebooks are now authored via the Python Kernel. The Spark and PySpark kernel are deprecated and set to be removed in a subsequent release.|
|Recipes||New PySpark and Spark recipes now follow the Docker workflow similar to Python and R recipes.|
For more general information on Data Science Workspace, see the overview documentation.
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
|(Beta) Destination SDK support for Google Cloud Storage file-based destinations and configurable file names.||You can now use the Destination SDK to create Google Cloud Storage destinations and define custom file names for exported files, via file name macros.
File-based destination support in Adobe Experience Platform Destination SDK is currently in Beta. The documentation and functionality are subject to change.
|Segment column in dataflow runs to batch destinations||For dataflow runs to batch destinations, the UI now displays the name of the segment associated with each dataflow run. Read more about dataflow runs to batch destinations.|
|(Beta) Google Ad Manager 360||The Google Ad Manager 360 connection enables batch upload for publisher provided identifiers (PPID) into Google Ad Manager 360, via Google Cloud Storage
This destination is currently in Beta and is only available to a limited number of customers. To request access to the Google Ad Manager 360 connection, contact your Adobe representative and provide your IMS Organization ID.
|Medallia||Activate profiles for targeted Medallia surveys and feedback collection to better understand customer needs and expectations.|
|Adobe Advertising Cloud DSP||The Adobe Advertising Cloud Demand-Side Platform (DSP) destination allows you to share authenticated first-party segments with approved advertisers and users for campaign activation with DSP.|
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.
New XDM components
|Class||Medication||A healthcare industry class that captures details about a substance used for medical treament, especially a medicine or drug.|
|Class||Plan||A healthcare industry class that captures details about a medical plan, such as a health plan or insurance plan.|
|Class||Provider||A healthcare industry class that captures details about a healthcare provider.|
|Class||Payer||A healthcare industry class that captures details about an insurance company.|
|Class||Live Event Schedule||A sports and entertainment industry class that captures details about a live event schedule, such as a traveling concert schedule or a sports team’s schedule.|
|Class||Location||A sports and entertainment industry class that captures the location of a live event, such as a concert hall or sports arena.|
|Field group||Healthcare medication||A field group for the Medication class that captures details about the medication such as brand name, lot number, and quantity.|
|Field group||Healthcare Plan Details||A field group for the Plan class that captures details such as network, type, and active status.|
|Field group||Healthcare Provider||A field group for the Provider class that captures details of an individual health professional or a health facility organization licensed to provide healthcare diagnosis and treatment services.|
|Field group||Healthcare Member Details||A field group for the XDM Individual Profile class that captures details of a person that has or will receive a service or care, such as contact information, primary care physician, and plan information.|
|Field group||Sitetool Details||A field group for the XDM ExperienceEvent class that captures information collected by sitetools such as chatbot, survey, and so on.|
|Field group||Live Event Ticket Purchase||A field group for the XDM ExperienceEvent class that captures the purchase history for tickets to a live event, such as a concert or sports game.|
|Field group||Sports and Entertainment Event Schedule||A field group for the Live Event Schedule class that captures further details about the schedule, such as the attraction name, door opening times, and more.|
|Field group||Sports Entertainment Event Venue||A field group for the Location class that captures further details about the event venue, such as seating capacity and Designated Market Areas (DMAs).|
|Global schema||(Several)||New global schemas are available for destinations metrics for RTCDP Insights. See the following pull request for more details.|
Updated XDM components
|Component type||Name||Update description|
|Behavior||Time-series Schema||Added a media states-update event type.|
|Field group||Lodging Reservation||Added a lodging checkout property.|
|Data type||Media information||Added states-start and states-end fields.|
|Extension||Workfront Change Event||Added two fields used to store attributes to help identify the user and the time of a create event.|
|Extension||Adobe CJM ExperienceEvent - Message interaction details||Added subscription, consent, custom email, and additional data information in the landing page object.|
For more information on XDM in Platform, see the XDM System overview.
Query Service allows you to use standard SQL to query data in Adobe Experience Platform Data Lake. You can join any datasets from the 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.
|Ad hoc schema labeling||Manage access to sensitive data by applying labels to data fields of ad hoc schemas that are automatically generated through Query Service CTAS queres. You can restrict the usage of certain fields, or datasets, of ad hoc schemas to control access to both sensitive personal data and personally identifiable information. By using the attribute-based access control capability you can you label ad hoc schema fields through the Platform UI.|
||When connecting to a database through third-party BI tools, the
For more information on Query Services, refer to the Query Service 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.
|Beta release of Mixpanel source||You can now use the Mixpanel source to ingest analytics data from your Mixpanel account to Experience Platform. See the Mixpanel source documentation for more information.|
To learn more about sources, see the sources overview.