Destinations overview
- Topics:
- Destinations
CREATED FOR:
- Beginner
- User
- Admin
Destinations are pre-built integrations with destination platforms that activate and export data to those partners in a seamless way. Learn about the destination types that you can use to get data out of Real-Time CDP, Experience Platform, and Tags to support a wide variety of use cases. For more information, please visit the documentation.
Transcript
Now let’s dig into what destinations are and the different types of destinations available. Destinations are pre-built integrations with destination platforms supported by Real-Time Customer Data Platform that activates data to those partners in a seamless way. You can explore a list of destinations by navigating to our destination catalog page.
In Adobe Real-Time CDP there are currently two types of destinations. Profile export and segment export. Profile export destinations generate a file containing profiles and their attributes. Segment export destinations send the profile and segments they’re qualified for. The main difference between profile export destinations and segment export destinations is that profile export uses raw PII data with email often as the primary key. While segment export uses segment IDs and user IDs or pseudonymous data such as hash emails for social networks. There isn’t a destination that is better than another and most marketers use a combination of both. It all depends on your use case.
Let’s dig into profile exports. This type of destination is typically used to integrate with marketing automation platforms. Or email marketing platforms. Profile export destinations send customizable profile attributes or raw PII data in a CSV or tab-delimited file to a marketer specified SFTP server or Amazon S3 bucket.
A marketer can send profiles as segments to filter and qualify the profiles that get exported. When sending profile by segments to the destinations, a file will be generated for each segment. Let’s say that you have created multiple segments in your organization, such as a segment for VIP customers who bought a T-shirt or newly registered VIP members. If you wanted to activate that data into your email marketing platform so that you can use those segments for personalized email campaigns, this would be an example of a profile export destination use case. Now let’s take a look at segment exports. This type of destination is typically used to integrate with social networks, demand side platforms, supply side platforms, or digital media target platforms. Segment export destinations only export the audiences for which a user has qualified with a given partner. They don’t export a full profile, just the segments that are mapped to the destination for which the profile is qualified. The data sent to segment export destinations is anonymized using segment IDs and user IDs or pseudonymous data in the case of hash emails for social network. Adobe handles the hash email when sending the data so there’s no need to upload hash data. A typical use case for a segment export destination will be if you wanted to target visitors who have visited your website in the last seven days in a retargeting ad campaign. So those are the two types of destinations that you can use to activate data with Real-Time CDP.
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
- Authenticate to Experience Platform APIs
- Import sample data to Experience Platform
- Administration
- AI Assistant
- 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 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
- 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
- Data Science Workspace
- Overview
- Architecture
- Load data in JupyterLab notebooks
- Query and discover data in JupyterLab notebooks
- Exploratory Data Analysis
- Recipes, models, and services overview
- Build a model using the recipe builder template
- Analyze model performance
- Create and publish a trained model (UI)
- Schedule automated training and scoring for a service
- Enrich Real-Time Customer Profiles with machine learning insights
- Package source files into a recipe
- Import a packaged recipe (UI)
- Import a packaged recipe (API)
- Destinations
- Destinations overview
- Connecting to destinations
- Create destinations and activate data
- Activate profiles and segments to a destination
- Configure a dataset export 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
- 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