- 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
Geotargeting With Platform-level Keys
Describes the common platform-level key-value pairs you can use to target users with geographic variables across all properties in your Audience Manager account.
Purpose of Platform-level Variables
Platform-level variables let you take data passed in from a particular site and make it available for targeting across all the properties in your Audience Manager account. These variables are formed by key-value pairs with the key prefixed by d_ as shown below.
Adding Values to Platform-level Keys
For some platform-level keys, you can specify the value yourself. With others, the keys are associated with corresponding IP addresses passed in on an event call. In either case, you still need to specify the value when building traits in Trait Builder.
User-defined Platform-level Keys
If you already have, or are establishing, a process to define and collect key-value pairs, then utilize this option. If you want to use keys pre-defined by IP address, continue to the next section. In the case of user-defined keys, you specify the value when building traits with these key-value pairs:
| Key | For Targeting |
|---|---|
d_zx |
ZIP code (e.g., d_zx=10022). |
Platform-level Keys Defined by IP Address
We work with Digital Envoy to obtain and update the demographic and geographic data for the keys below. The values for these keys are determined by matching IP addresses to corresponding geographic and demographic data. However, you’ll still have to enter the value parameter when creating the key-value pair in Trait Builder.
| Key | For Targeting |
|---|---|
| d_area_code | North America area codes. For example:
|
| d_city | Cities and towns. Download the cities list. For example:
d_city coupled with d_country to be sure you’re not targeting two cities with the same name in different countries. You can be even more specific in your targeting by using d_postal_code. |
| d_country | Values correspond to ISO country codes. For a searchable list of codes, see the ISO Online Browsing Platform. Targeting for the United Kingdom is the only special case that does not obey ISO 3166. You should use “UK” instead of “GB” for targeting in the United Kingdom. To target the Netherlands Antilles, the code “AN” has been deprecated since 2010. The area has been dissolved into five separate territorial units. The implication is that for targeting in the Netherlands Antilles, you should not use “AN,” but a combination of the country codes for “CW,” “SX,” and “BQ.” For example: Trait: d_country=CZ Trait Name: Czech Republic Trait: d_country=UK Trait Name: United Kingdom Trait: d_country=CW OR d_country=SX OR d_country=BQ Trait Name: Netherlands Antilles |
| d_dma_code | Metropolitan area DMA codes. Download the DMA region list (.csv format). For example:
|
| d_lat | Latitude (e.g. d_lat=40.75). Download the latitudes list. |
| d_long | Longitude (e.g. d_long=73.98). Download the longitudes list. |
| d_postal_code | ZIP codes (exclude the extended +4 code). Download the postal codes list. For example:
|
| d_state | 2-character abbreviation for a US state. Download the states codes list. For example:
|
| d_region | Regional alphanumeric IDs. Download the region list. Then, you can use this list to match region IDs to region names. |
| d_isp | ISP/organization. Download the ISP List. |
The list of all location-based signals comprises all the signals above, in the following order: d_country,d_city,d_region,d_state,d_dma_code,d_postal_code,d_area_code,d_lat,d_long
Resources
Adobe Account
Change language
Copyright © 2023 Adobe. All Rights Reserved.
