Destinations are pre-built integrations with destination platforms that allow for the seamless activation of data from 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 functionality
Feature
Description
Control which audiences to export to enterprise destinations
Use the new Include mapped audiences only toggle to choose what the segmentMembership object contains when you export audiences to the HTTP API, Amazon Kinesis, and Azure Event Hubs destinations. Turn it on to include only the audiences mapped in that dataflow, or leave it off to include every audience a profile qualifies for. All dataflows to enterprise destinations created prior to this release will have the toggle turned off by default, keeping their existing behavior.
In the Select destination step of the activation workflow, you can now search by flow name to locate a destination or an existing dataflow. You can also use filtering and tagging options to find the right destination to activate data to. {modal="regular"}
In the Select audiences step of the activation workflow, you can now filter audiences by evaluation type (edge, streaming, or batch), namespace origin, audience tags, and more. You can also use the same tags that you use for audiences across other screens, making audience management easier in the context of activation. {modal="regular"}
Use the new search field in the Select source field dialog to filter the identity namespace list by name when mapping audiences during activation. {modal="regular"}
Use the Microsoft Ads Customer Match destination to match customers by email address and re-engage with them across the Microsoft Advertising Network, including Search and Audience ads. Note: The Microsoft Ads Customer Match destination is rolling out to all customers over the course of this week, by July 30.
The Kevel destination now supports profile attribute mapping. You can map a profile attribute to the incrementality testing group field in the Kevel destination, so exported user records include the correct group value for incrementality testing use cases. {modal="regular"}
We have made several updates to the LiveRamp onboarding connector:
Added a new ONCE export frequency.
Reduced or eliminated file splits for audiences with high population sizes, which helps prevent cases on the LiveRamp side where large audiences imported from Adobe could be overwritten because of numerous file splits.
Map three new optional target fields, title, jobLevel, and jobFunction, to the Demandbase People destination in addition to the existing mandatory and recommended mappings. Adobe recommends mapping these fields when available for richer person data and better downstream audience targeting.
The file-split threshold for exported files increased from 10 million to 100 million rows, so audiences are less likely to be split across multiple files when exported.
Use the Adhese destination to send audiences for targeted ad delivery on publisher-owned inventory. Audience exports are delivered as files to Adhese’s secure cloud storage.
With Real-Time CDP, you can unify customer data from multiple sources, build rich audiences, and activate them across channels in real time, all within Experience Platform. This helps you deliver timely, personalized, privacy-compliant experiences through seamless cross-channel campaigns.
New or updated features
Feature
Description
Spectrum 2 Visual Refresh
The Real-Time CDP interface is being updated to reflect Adobe’s Spectrum 2 design system, delivering a more modern, cohesive, and accessible experience across the platform. This release includes visual refinements to typography, buttons, tags, search fields, inventory tables, and page backgrounds across core areas including Audiences, Datasets, Schemas, Profiles, Sources, and Destinations. Additional areas will continue to be updated in upcoming releases. These changes are visual only and do not affect functionality, data, or workflows.
View the images below for before and after examples of the visual refresh:
Use Real-Time Customer Profile to create a holistic view of each individual known and anonymous customer, aggregated from multiple online and offline sources in real time.
New or updated features
Feature
Description
Faster profile exports and activation
Profile attribute data is now consolidated when data is written, instead of repeatedly at read time. As a result, profile exports complete significantly faster, making downstream activations to destinations and Adobe Journey Optimizer available sooner. This is a fully managed, back-end update. There is no change to how you configure or use Real-Time Customer Profile, nor is there any change to functionality or merge behavior. However, ingestion of profile attributes may take slightly longer, since more processing now happens at write time. This update is being rolled out through the end of July 2026. Review your scheduled ingestion and segmentation jobs to confirm that the timing buffer between them remains appropriate, and consider moving up downstream activation schedules that were previously limited by processing time.
Pseudonymous profile data expiration update
The CJA Audiences Profile Dataset that is created through the Customer Journey Analytics (CJA) Audience Service publishing flow is now correctly identified as containing system-generated data. Previously, these datasets could affect pseudonymous profile lifecycle management, resulting in inflated profile counts in Real-Time CDP. Newly created datasets are now automatically flagged as holding system generated data, and existing datasets created through this publishing flow have been updated accordingly.
Adobe Experience Platform is built to enrich digital experience applications on a global scale. Companies often run multiple digital experience applications in parallel and need to cater to the development, testing, and deployment of these applications while ensuring operational compliance.
New or updated features
Feature
Description
Sandbox Tooling agentic skill
The Sandbox Tooling agentic skill in CX Coworker gives you a conversational way to replicate sandbox object metadata across environments. Describe what you want in natural language, and the agent can help you:
Discover objects in a source sandbox
Package selected objects with their dependencies
Validate changes before import
Migrate configurations to a target sandbox
Monitor migration progress
The agent surfaces execution plans and dependency analysis so you can review proposed work before it runs. Use it to speed up sandbox development while making migrations safer and easier to reason about. For setup, usage, plan interpretation, and best practices, read the documentation on Sandbox Tooling agentic skills. Note: In this release, only Schema and Audience objects are supported.
Use Segmentation Service to create audiences from your customer data and manage their full lifecycle in Experience Platform.
New or updated features
Feature
Description
External audience file support for JSON and Parquet
Upload external audiences as JSON or Parquet files, in addition to existing supported formats. The dataFilterStartTime field is now optional when you create an external audience from an uploaded file. For more information, read the external audiences endpoint guide.
Discontinuation of Segment Match
Segment Match will be discontinued and no longer available for use after November 27, 2026. Real-Time CDP Prime and Ultimate customers should transition data collaboration use cases from Segment Match to Real-Time CDP Collaboration. For more information, read the Segment Match documentation.
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.
New or updated sources
Source
Description
Google Ads
Use the Google Ads source to configure the complete ingestion workflow using APIs or the UI. Connect your Google Ads account and bring paid media data directly into Experience Platform for activation and analysis. Read the Google Ads overview for more information.
Meta Ads
Use the Meta Ads source to configure the complete Meta Ads ingestion workflow in the Sources UI. Connect your Meta Ads account and bring paid media data directly into Experience Platform for activation and analysis. Read the Meta Ads overview for more information.
