- Audience Manager Guide
- Evolution guide to Real-Time CDP
- 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
Profile Merge Rules Options Defined
The profile merge rule options let you control the type of data Audience Manager uses for segmentation. A profile merge rule can include device profiles mapped by the Profile Link device graph and/or other, third-party device graph providers who are integrated with Audience Manager. You can create a maximum of 4 Profile Merge Rules. The fourth Profile Merge Rule is available exclusively to customers who purchased the People-Based Destinations add-on.
You build a Profile Merge Rule by making a selection from the options described below, in Profile Merge Rule Setup.
Profile Merge Rule Options Overview
Profile Merge Rules allow for a number of rule combinations, each geared towards specific use cases. See the table below for details on when to use each rule combination.
| Cross-Device Option | Device Option | Availability | Evaluation Type | Audience Lab Support | Use Cases |
|---|---|---|---|---|---|
| No Cross-Device Profile | Device Profile | All customers | Real-time and batch | Yes | Device Targeting |
| No Cross-Device Profile | External Device Graph | All customers | Real-time and batch | No | Expanded Device Targeting |
| Current Authenticated Profiles | No Device Profile | All customers | Real-time only | No | Shared Device Targeting |
| Last Authenticated Profiles | Device Profile | All customers | Real-time and batch | Yes | Online/Offline Targeting |
| Last Authenticated Profiles | Profile Link Device Graph | All customers | Real-time and batch | Yes | Cross-device Targeting |
| Last Authenticated Profiles | External Device Graph | All customers | Real-time and batch | No | Advanced Cross-Device Targeting |
| All Cross-Device Profiles | N/A | Exclusive to People-Based Destinations customers | Batch only | No | Targeting for People-Based Destinations |
Profile Merge Rule Segment Evaluation
Depending on your Profile Merge Rules configuration, Audience Manager can perform the segment evaluation in real-time, in batch, or both.
- Real-time segment evaluation requires the DCS to see visitors access your digital properties in real-time, to qualify for the segment.
- Batch segment evaluation is performed against previously qualified traits.
- Profile Merge Rules that support both real-time and batch segment evaluation combine the real-time visitor activity with previously qualified traits.
Profile Merge Rules Reporting Latency
Real-time segment evaluation reflects immediately in the Profile Merge Rules reports.
Batch segment evaluation can take up to 24 hours to reflect in the Profile Merge Rules reports.
Cross-Device Options
The Cross-Device Options let you select authenticated and unauthenticated users and leverage their cross-device profile for segmentation. These options help you identify and reach specific users on a shared device. For more information on anonymous and authenticated users, see Visitor Authentication States in Audience Manager.
| Cross-Device Option | Description |
|---|---|
| No Cross-Device Profile |
Tells Audience Manager not to use data collected from authenticated users. |
| Current Authenticated Profiles |
Tells Audience Manager to read and write data to the authenticated profile if a visitor has logged in to your site. |
| Last Authenticated Profiles |
Tells Audience Manager to read data from the authenticated profile of the user who last logged in on the device. When selected, Audience Manager will not write new trait data to the authenticated profile if the user is anonymous. Upon authentication, new trait data gets written to the user's authenticated profile. |
| All Cross-Device Profiles |
Tells Audience Manager to read data from all cross-device profiles, regardless of the authentication state. This option is only available for Audience Manager customers who have purchased the People-Based Destinations add-on. |
Cross-Device Profile Options
The Cross-Device Profile Options lists your cross-device data sources. These options use the names you provided when you created a cross-device data source (see Create a Cross-Device Data Source). You can select up to 3 cross-device data sources to use with each profile rule. The Authenticated Profile Options are available when you choose Current Authenticated Profiles or Last Authenticated Profiles.
Device Options
The Device Options let you select the type of device profile used by a Profile Merge Rule. A device profile is built from traits collected from anonymous browsing activity. At a minimum, a profile merge rule includes an authenticated option and a device option.
| Device Option | Description |
|---|---|
| No Device Profile |
Tells Audience Manager not to use the traits contained in the anonymous profile for segmentation. |
| Device Profile |
Tells Audience Manager to use the anonymous device profile for segmentation. |
| Profile Link Device Graph |
Tells Audience Manager to read the profiles from the current device and up to 100 other devices that the user has authenticated from. This device graph is built on your own, first-party data in Audience Manager. It is ideal for customers who have a high level of authentication across their digital properties. The Profile Link device graph is updated in real time. This option is available when you select Current Authenticated Profile or Last Authenticated Profile. When using this option, you can only choose a single authenticated profile ( Audience Manager automatically grays out the others). See also, Profile Link Device Graph Use Cases. |
| Third-Party Device Graph Options (Person and Household) |
These options let you build merge rules based on device graph technology provided by a third-party vendor. A third-party device graph provides:
To use these options, you must be a customer of a device graph provides who is already integrated with Audience Manager. Contact your account manager for more information or to get started. |
External Merge Policies
Audience segments that were automatically created from other Experience Cloud solutions, based on merge rules defined outside of Audience Manager, are marked as using an External Merge Policy. For example, see Audience Sharing Between Audience Manager and Adobe Experience Platform.
Resources
Adobe Account
