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 | New or Updated | Description |
|---|---|---|
| MoEngage | New | Use the Moengage destination to connect and map your Adobe data (user attributes, segments and events) to MoEngage in real-time. Customers can then act on this data, delivering personalized, targeted experiences. |
| Qualtrics Automations | New | Use the aggregation of multiple sources of operational data in Adobe Experience Platform as an input in Qualtrics Experience ID to better understand your customers and enable targeted outreach to close the gap when it comes to understanding intent, emotion and experience drivers. |
New or updated functionality
| Functionality | Description |
|---|---|
| (Beta) Support for hashing functions in calculated fields | In addition to the functions specific for exporting arrays or elements from an array, you can now use additional hashing functions to hash attributes in the exported files. The supported hashing functions are: sha, sha256, sha512, hash, md5, crc32. |
| (Limited GA) Activate account audiences to certain destinations | Real-Time CDP B2B customers can now activate account audiences to certain destinations. For more information about this feature, please read the activate account audiences tutorial. |
Fixes and enhancements
For more general information on destinations, refer to the destinations overview.
Sandboxes
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 for the development, testing, and deployment of these applications while ensuring operational compliance. To address this need, Experience Platform provides sandboxes that partition a single Platform instance into separate virtual environments to help develop and evolve digital experience applications.
New feature
| Feature | Description |
|---|---|
| Sandbox tooling | The sandbox tooling feature allows you to improve configuration accuracy across sandboxes and seamlessly export and import sandbox configurations between sandboxes. You can use the sandbox tooling feature to select different objects and export them into a package. For more information, see the sandbox tooling UI guide. |
For more information on sandboxes, please see the sandboxes overview.
Segmentation Service
Segmentation Service allows you to segment data stored in Experience Platform that relates to individuals (such as customers, prospects, users, or organizations) into audiences. You can create audiences through segment definitions or other sources from your Real-Time Customer Profile data. These audiences are centrally configured and maintained on Platform, and are readily accessible by any Adobe solution.
New feature
| Feature | Description |
|---|---|
| Account audiences (Limited GA) | In Real-Time Customer Data Platform B2B Edition, you can now use account segmentation to bring the full ease and sophistication of the marketing segmentation experience from people-based audiences to account-based audiences. For more information about this feature, please read the account audiences overview. |
To learn more about Segmentation Service, please read the Segmentation Service overview.
Sources
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 features
| Feature | Description |
|---|---|
| Updated authentication for Data Landing Zone | You can now see the designated expiry date of your Data Landing Zone when viewing your credentials. You must refresh your token before the expiry date in order to continue using it in your application. If you do not manually refresh your token before the stated expiry date, then it will automatically refresh and provide a new token the next time you retrieve your credentials. For more information, read the documentation on using the Data Landing Zone. |
To learn more about sources, please read the sources overview.