Integration
Configure the Adobe Target destination in Real-Time Customer Data Platform
Last update: February 14, 2025
CREATED FOR:
- Intermediate
- Admin
- Developer
- User
Learn how to integrate Adobe Target and Real-Time Customer Data Platform to start sending segments and profile attributes from Real-Time CDP to Target. For more information, see the Adobe Target connection documentation.
Transcript
Hi, this is Daniel and in this video I’m going to show you how to set up the Adobe target destination in Realtime Customer Data Platform so you can begin sharing both segments and profile attributes from real-time CDP to target to personalize your websites, mobile apps, and other connected devices. These are mostly administrative tasks needed to get the integration up and running. In other videos we’ll cover how to actually share and use the segments and profile attributes. The setup is easy and you’ll see it’s just a matter of checking various boxes and pressing buttons, but they’re spread over a few product features and depending on how your company manages user permissions it might require a few people at your company to complete these steps. So the features we need to configure are data streams, merge policies, and destinations. First let’s enable a data stream. To get the most functionality out of the integration you should implement the Adobe Experience Platform web and or mobile SDKs which use platform edge network and data streams to send data to target. You can still share segments to target if you’re still on an older SDK like ATJS, but the segment qualification won’t happen on the edge and will be a little slower. Of course ATJS doesn’t use data stream so if you’re still using that library you can skip this step. Okay so I’m in the platform interface but you can also do this in the data collection interface too. You need to have permissions to view and manage data streams to complete this step. Okay so first both target and experience platform need to be included as services in the data stream. Second in the experience platform service you need to check these two boxes for edge segmentation and personalization destinations. Now I’m doing this in a dev sandbox and you would need to repeat this for any other sandboxes or data streams in which you’re going to use the integration. That’s it for this step. Next let’s make a small change to a merge policy. To complete this step you need to have permissions to view and manage merge policies. In experience platform I’ll navigate to profiles in the left navigation and select the merge policies tab. A merge policy creates a view of a profile specifying which data sets are included and how to prioritize overlapping fields. You can create multiple merge policies that create different views of a single profile but only one merge policy can be selected as the default and only one can be used with edge segments. To keep things simple for your marketers I suggest just activating your default merge policy for edge which you can easily do by enabling this active on edge merge policy toggle and then clicking through the workflow to save the policy. When marketers create segments that evaluate on the edge the segment definition needs to use this active on edge merge policy. Let me just show you quickly in this segment builder. You see here under the gear icon you can see the merge policy used by this segment. So if you hear from a marketer that they’re unable to save an edge segment it’s probably because they’re using the wrong merge policy and that’s why it’s easiest to just enable the default merge policy for edge. Again another simple but important configuration. So finally I’ll set up the Adobe Target connection and a destination. For this I need permission to view and manage destinations. All you have to do is select the connect to destination button and it’s going to connect to the Adobe Target account that’s in your experience cloud organization. This checkbox will subscribe you to alert notifications if a certain threshold of profiles aren’t getting sent to target due to missing attributes or consent violations. You can subscribe to them later as well. On the next screen it’s going to ask me for a name and description as well as the data stream id. For the data stream id I’m going to select the one that I just enabled with those two check boxes. Then I’m asked for the marketing actions used by target. This is a configuration setting for every destination and it helps to automate enforcement of your organization’s data governance policies and your customers consent preferences. It’s basically asking how do you use target which might be slightly different for each one of you. I’ll check a few options and that’s it for the destination and remember you can set up additional destinations for your other data streams and sandboxes. In other videos I’ll show you how you can activate segments and profile attributes to target and use them to personalize your digital properties. So thanks for listening.
Previous pageNext-hit personalization with Adobe Target
Next pageActivate segments and profile attributes
Real-Time Customer Data Platform
- Platform Tutorials
- Introduction to Platform
- A customer experience powered by Experience Platform
- Behind the scenes: A customer experience powered by Experience Platform
- Experience Platform overview
- Key capabilities
- Platform-based applications
- Integrations with Experience Cloud applications
- Key use cases
- Basic architecture
- User interface
- Roles and project phases
- Introduction to Real-Time CDP
- Getting started: Data Architects and Data Engineers
- Import sample data to Experience Platform
- Administration
- AI Assistant
- APIs
- Audiences and Segmentation
- Introduction to Audience Portal and Composition
- Upload audiences
- Overview of Federated Audience Composition
- Connect and configure Federated Audience Composition
- Create a Federated Audience Composition
- Audience rule builder overview
- Create audiences
- Use time constraints
- Create content-based audiences
- Create conversion audiences
- Create audiences from existing audiences
- Create sequential audiences
- Create dynamic audiences
- Create multi-entity audiences
- Create and activate account audiences (B2B)
- Demo of streaming segmentation
- Evaluate batch audiences on demand
- Evaluate an audience rule
- Create a dataset to export data
- Segment Match connection setup
- Segment Match data governance
- Segment Match configuration flow
- Segment Match pre-share insights
- Segment Match receiving data
- Audit logs
- Data Collection
- Collaboration
- Dashboards
- Data Governance
- Data Hygiene
- Data Ingestion
- Overview
- Batch ingestion overview
- Create and populate a dataset
- Delete datasets and batches
- Map a CSV file to XDM
- Sources overview
- Ingest data from Adobe Analytics
- Ingest data from Audience Manager
- Ingest data from cloud storage
- Ingest data from CRM
- Ingest data from databases
- Streaming ingestion overview
- Stream data with HTTP API
- Stream data using Source Connectors
- Web SDK tutorials
- Mobile SDK tutorials
- Data Lifecycle
- Destinations
- Destinations overview
- Connect to destinations
- Create destinations and activate data
- Activate profiles and audiences to a destination
- Export datasets using a cloud storage destination
- Integrate with Google Customer Match
- Configure the Azure Blob destination
- Configure the Marketo destination
- Configure file-based cloud storage or email marketing destinations
- Configure a social destination
- Activate through LiveRamp destinations
- Adobe Target and Custom Personalization
- Activate data to non-Adobe applications webinar
- Identities
- Intelligent Services
- Monitoring
- Partner data support
- Profiles
- Understanding Real-Time Customer Profile
- Profile overview diagram
- Bring data into Profile
- Customize profile view details
- View account profiles
- Create merge policies
- Union schemas overview
- Create a computed attribute
- Pseudonymous profile expirations (TTL)
- Delete profiles
- Update a specific attribute using upsert
- Privacy and Security
- Introduction to Privacy Service
- Identity data in Privacy requests
- Privacy JavaScript library
- Privacy labels in Adobe Analytics
- Getting started with the Privacy Service API
- Privacy Service UI
- Privacy Service API
- Subscribe to Privacy Events
- Set up customer-managed keys
- 10 considerations for Responsible Customer Data Management
- Elevating the Marketer’s Role as a Data Steward
- Queries and Data Distiller
- Overview
- Query Service UI
- Query Service API
- Explore Data
- Prepare Data
- Adobe Defined Functions
- Data usage patterns
- Run queries
- Generate datasets from query results
- Tableau
- Analyze and visualize data
- Build dashboards using BI tools
- Recharge your customer data
- Connect clients to Query Service
- Validate data in the datalake
- Schemas
- Overview
- Building blocks
- Plan your data model
- Convert your data model to XDM
- Create schemas
- Create schemas for B2B data
- Create classes
- Create field groups
- Create data types
- Configure relationships between schemas
- Use enumerated fields and suggested values
- Copy schemas between sandboxes
- Update schemas
- Create an ad hoc schema
- Sources
- Use Case Playbooks
- Experience Cloud Integrations
- Industry Trends