Overview and Use Cases
- Topics:
- People-based Destinations
Use People-Based Destinations to send first-party audience segments to people-based environments. These environments are closed ecosystems belonging to one entity that controls the content that is being displayed within it. They include social platforms such as Facebook, and other platforms that rely on customer accounts to personalize the displayed content.
Overview
People-Based Destinations enable you to apply segmentation on online and offline data to create audience segments based on hashed identifiers, such as email addresses. Then, you can send these segments to “walled gardens” such as Facebook, where you can target your audience on the social platforms. People-Based Destinations can help you:
- Target offline and online audiences in platforms such as Facebook, based on hashed email addresses;
- Complement existing device and cookie targeting capabilities of Audience Manager;
- Eliminate costs associated with third-party data onboarding solutions;
- Eliminate costs associated with developing custom data onboarding workflows;
- Target audiences in cookie-less environments;
- Target audiences by deduplicating hashed email addresses matched to customer IDs.
You can use People-Based Destinations to segment and target high value customers who may not visited your website, or stop targeting those who have already converted offline. Additionally, you can leverage Profile Merge Rules to combine your offline first-party data with your online first-party data, including customer data from other Adobe Experience Cloud solutions, to optimize your social media advertising efforts.
Availability
People-Based Destinations is a premium Audience Manager integration. Please contact your Adobe representative to take advantage of this premium feature.
Why You Should Use People-Based Destinations
Provide your customers consistent cross-channel experiences by managing your entire audience segmentation from within Audience Manager.
Not activating your audience segments in people-based channels through Audience Manager leads to disjointed experiences between what your customers see when visiting your website and what they see, for instance, in their Facebook feeds. Having a consistent targeting across channels can increase your ad revenue while optimizing your ad spending.
Reach audiences in people-based channels without the need of a dedicated data onboarding solution or custom workflows to send audiences.
The more “traditional” way of targeting audiences across people-based channels involves you having to export your customer data in a format accepted by the platform that you want to advertise on, and then using the platform’s dedicated data onboarding method to bring your customer data to your advertiser account. This is all manual work that you need to do for each platform that you want to advertise on. Additionally, different platforms may have different data format requirements, making the process even more tedious.
Through People-Based Destinations, Audience Manager helps you centralize your customer data, build audience segments, and activate them across multiple people-based channels. You can do this all from within the Audience Manager user interface, avoiding the additional work of manually uploading data to each platform, saving you valuable time in the process.
Create and activate audience segments from purely offline profiles.
People-Based Destinations solve the issue that previously, you could only activate audience segments based on device activity. With People-Based Destinations, you can create segments from purely offline data from your own CRM, and activate them in people-based platforms. Additionally, you can correlate your offline data with device data that you already have in Audience Manager.
Leverage Audience Manager’s data governance and privacy controls to safely handle customer data.
People-Based Destinations requires that you only use irreversibly hashed identifiers. This reduces the risk associated with manually uploading customer data into each destination platform.
Watch the video below to get an overview of the data flow when using People-Based Destinations.
Use Cases
To help you better understand how and when you should use People-Based Destinations, here are two sample use cases that Audience Manager customers can solve by using this feature.
Use Case #1
An online retailer wants to reach existing customers through social platforms and show them personalized offers based on their previous orders. With People-Based Destinations, the online retailer can ingest hashed email addresses from their own CRM to Audience Manager, build segments from their own offline data, and send these segments to the social platforms they want to advertise on, optimizing their advertising spending.
Use Case #2
An airline has different customer tiers (Bronze, Silver, and Gold), and wants to provide each of the tiers with personalized offers via social platforms. The company uses Audience Manager to analyze customer activity on the website. However, not all customers use the airline’s mobile app, and some of them have not logged in to the company’s website. The only identifiers the company has about these customers are membership IDs and email addresses.
To target them across social media and similar people-based channels, they can onboard the customer data from their CRM into Audience Manager, using the hashed email addresses as identifiers.
Next, they can combine their offline data with their existing online activity traits, to build new audience segments that they can target through People-Based Destinations.
Audience Manager
- Audience Manager Guide
- Evolution guide to Real-Time CDP
- Migrate to Web SDK
- Overview
- Features
- Addressable Audiences
- Administration
- Algorithmic Models
- Audience Lab
- Audience Marketplace
- Customer Data Feeds
- Data Explorer
- Data Export Controls
- Data Sources
- Declared IDs
- Derived Signals
- Destinations
- Destinations Overview
- Destinations Home Page
- Adobe Experience Cloud Destinations
- People-Based Destinations
- Device-Based Destinations (Server-to-Server)
- Custom Destinations
- Destinations Reference
- Profile Merge Rules
- Profile Merge Rules Overview
- Getting Started with Profile Merge Rules
- Profile Merge Rules Dashboard
- Profile Merge Rule Options Defined
- General Use Cases for Profile Merge Rules
- Profile Link Device Graph Use Cases
- External Device Graph Use Cases
- Report Metrics for Profile Merge Rules
- Profile Merge Rules and Device Un-Segmentation Processes
- Instant Cross-Device Suppression
- Segments
- Segments: Purpose, Composition, and Rules
- Segments List View
- Segment Summary View
- Retrieving Segment Metadata
- Paused and Deleted Segments
- Recency and Frequency
- Segment Builder
- Code Syntax Used in the Segment Expression Editor
- Trait and Segment Population Data in Segment Builder
- Trait Recommendations
- Trait and Segment Qualification Reference
- Traits
- Traits Overview
- Trait Details Page
- Traits Dashboard
- Active Audience Traits and Data Source Synced Traits
- Folder Traits: About
- Manage Folder Traits
- Trait Builder
- Trait Storage
- Accuracy and Reach
- Classifying Traits with a Common Taxonomy
- Name Requirements for Key Variables
- Segment and Trait Time-to-Live Explained
- Prefix Requirements for Key Variables
- Geotargeting With Platform-level Keys
- Device Targeting With Platform-level Keys
- Sample Expressions With Boolean and Comparison Operators
- Trait and Segment Qualification Reference
- Visitor Profile Viewer
- Reporting
- Reports Overview
- Reports Dashboard
- General Reports
- Trend Reports
- Audience Optimization Reports
- Interactive and Overlap Reports
- Interactive and Overlap Reports Overview
- Trait-to-Trait Overlap Report
- Segment-to-Trait Overlap Report
- Segment-to-Segment Overlap Report
- Unused Signals Report
- Improve Log File Processing Times with Lookup Tables
- Filter Report Results With the Data Sliders
- Overlap Reports: Update Schedule and Minimum Segment Size
- CSV Files for Overlap Reports
- Report Technology
- Onboarding Status Report
- Outbound File History
- Counting Unique Users in Overlap and General Reports
- Data Sampling and Error Rates in Selected Audience Manager Reports
- API and SDK Code
- API and SDK Code Overview
- Audience Manager API Code Migration
- Data Collection Server (DCS) API Methods and Code
- REST APIs
- REST APIs Overview
- Getting Started with REST APIs
- Algorithmic API Methods
- Data Integration Library API Methods
- Data Source API Methods
- Derived Signals API Methods
- Destination API Methods
- Domain Management API Methods
- Folder API Methods
- Segment API Methods
- Taxonomic API Methods
- Trait API Methods
- Trait Type Methods
- User, Group, and Permissions Management API Methods
- DCS Region API Methods
- SDK Code
- Data Integration Library (DIL) API
- Implementation and Integration Guides
- Implementation and Integration Guides
- Data Integration Methods
- Integrate Google Ad Manager using Google Publisher Tags (GPT)
- Integrating with Third-Party Destinations
- Implementing Audience Manager
- Media Data Integration
- Receiving Audience Data
- Sending Audience Data
- Sending Audience Data
- Real-Time Inbound Data Integration
- Batch Data Transfer Process
- Batch Data Transfer Process Described
- Send Batch Data to Audience Manager Overview
- ID Synchronization for Inbound Data Transfers
- Name and Content Requirements for ID Synchronization Files
- Inbound Data File Contents: Syntax, Invalid Characters, Variables, and Examples
- Amazon S3 Name and File Size Requirements for Inbound Data Files
- FTP Name and File Size Requirements for Inbound Data Files
- File PGP Encryption for Inbound Data Types
- File Compression for Inbound Data Transfer Files
- Sample Message to Partners after Inbound Processing
- Leverage Amazon S3 Cross-Account Bucket Permissions for Your Inbound Files
- Custom Partner Integrations
- Integration with Adobe Experience Platform
- Integration with Other Experience Cloud Applications
- Reference
- Reference Overview
- Amazon S3: About
- Advertiser Use Cases
- Publisher Use Cases
- Beta Environment
- Boolean Expressions in Trait and Segment Builder
- Bulk Management Tools
- CID Replaces DPID and DPUUID
- How Data Delivery and File Processing Times Affect Reports
- Index of IDs in Audience Manager
- Key-Value Pairs Explained
- Password Requirements, Locked Accounts, and Forgotten Passwords
- Signals, Traits, and Segments
- Supported Browsers
- System Components
- Style Conventions for Code and Text Elements
- Time Zones in Audience Manager
- TLS 1.0 and 1.1 Deprecation
- Understanding Calls to the Demdex Domain
- Visitor Authentication States in Audience Manager
- FAQs
- Audience Manager FAQ Overview
- API FAQ
- Audience Lab FAQ
- Customer Data Feed FAQ
- Data Collection and Product Integration FAQ
- Inbound Customer Data Ingestion FAQ
- Privacy and Data Retention FAQ
- People-Based Destinations FAQ
- Product Features and Functions FAQ
- Profile Merge Rules and Device Graph FAQ
- Look-Alike Modeling FAQ
- Predictive Audiences FAQ
- Targeting FAQ
- Reporting FAQ
- Help and Legal
- Top Customer Support Issues
- Overview
- Why did my Onboarded trait populations drop to 0 around October 15th?
- Why do my traits or segments not show up in the Overlap Reports page?
- Why are our Read-Only users able to create, edit or delete traits and segments?
- We are not an Audience Manager customer, but see the Audience Manager Javascript calls on our site
- Should I see my Audience Manager Audience Lab mapped segments on the destination details page?
- Documentation Updates
- Glossary