- Audience Manager Guide
- 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
- Custom Partner Integrations
- Integration with Adobe Experience Platform
- Integration with Other Experience Cloud Solutions
- 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
- 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
Unused Signals Report
This report returns a frequency count of all the unused information collected on your inventory and sent to Audience Manager. To access this report, navigate to Analytics > Audience Reports > Other Reports > Unused Signals.
If you see the message “You don’t have access to Audience Reports”, contact your Audience Manager consultant or Customer Care to provision the report for you.
Overview
A signal is information from your website passed in to Audience Manager in the form of key-value pairs (e.g., color=blue, price>100, gender=female, etc.).
Unused signals consist of data that you collect but have not been mapped to a trait. The Unused Signals report shows data in a table by date, key, value, and frequency count. Any unmapped signal passed in to Audience Manager at least 100 times in a day qualifies for the Unused Signals report.
Review this report to help identify orphaned signals that can be mapped to new or existing traits.
Specify a key or value name in the search fields to limit results to specific records.
Use Cases
| Examples | Description |
|---|---|
| Ensure Trait Uniformity or Add Related Values to a Single Key |
Review the report to account for different value variations for a particular signal. For example, say you have a trait for the state "North Carolina" defined in a key-value pair as
|
| Create New Traits |
Review the report to see what new values get passed in on a particular key. You may want to create new key-value pairs based on these new values.
Note: Check the report bi-weekly for values that change frequently (e.g., shows, campaigns, celebrities, etc.). |
| Find Unmapped Values |
Review the report for the number 1. The number 1 in an Unused Signals report represents a null value. This is not necessarily bad. It simply means that a particular key does not have an associated value mapping. When you see a lot of 1 values for an important variable, check with your site team to make sure all your pages are tagged correctly. |
Best Practices
Run and check the Unused Signals report:
- After you create a trait or update trait rules. This helps ensure your traits and rules are set up properly. The number 1 in results indicates a new trait may not be configured correctly.
- Bi-weekly or monthly. Scheduled reviews help ensure trait mappings are up-to-date.
When searching for unused values in the report, please consider the following particularity. There is a difference in expression between the two examples below:
- T(v=1 AND NOT (a=23))
- T(v=1 AND (a!=23))
- Both examples show a trait which contains two key-value pairs v and a. The first expression translates into: the trait contains key v with the value 1 AND NOT the key a with the value 23. The second expression contains key v with the value 1 AND the key a with the value NOT EQUAL 23.
- Considering the two different expressions above, let’s say you search in the Unused Signals Report for the values that get passed on key a with any value different than 23, you’ll only obtain results in the first case because values for key were not sent AT ALL. In the second case, values different than 23 were sent so key a is not unused.
Bulk Trait Creation
Contact your Partner Solutions representative if you need to bulk create a lot of traits based on data obtained from the Unused Signals report.