- 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
Outbound Data File Name: Syntax and Examples
Describes the required fields, syntax, and conventions used to name an outbound data file.
The style elements (monospaced text, italics, brackets [ ] ( ), etc.) in this document indicate code elements and options. See Style Conventions for Code and Text Elements for more information.
Syntax and File Name Elements
Outbound file names contain the following elements. All of the elements below are optional.
[SYNC_TYPE][_DID][_MASTER_DPID][_PID_ALIAS][_SYNC-MODE][_TIMESTAMP]SPLITNUM.sync[.gz]
Parameters
The table defines the elements in an outbound data file name.
| File Name Element | Description |
|---|---|
| |
Refers to the data transfer methods. Transfer methods include:
|
| |
Destination ID. In Audience Manager , a destination is the instance of the integration where you can map your targetable segments. Customers can have multiple destinations, depending on the business requirement. |
| |
Data-provider or data source ID. This ID identifies the type of User ID present in the file content. Most common User ID keys are:
See Global Data Sources for more details. |
| |
The customer identifier from the 3rd party platform. |
| |
Sync mode is a macro placeholder that adds a label to the file name based on synchronization type. Synchronization types include full and incremental. They'll appear in the file name as
|
| |
A 13-digit UNIX timestamp in milliseconds, in the UTC time zone. |
|
|
An integer. Identifies part of a file that's been split into multiple parts to improve processing times. The number indicates which part of the original file the data belongs to. The integer must be at least 3 digits long, preceded by zeros, if the split size is lower than 100 parts. The original file will not have any split number. The first split file will end with 001. See examples below. |
| |
GZIP compression. |
File Name Examples
Scenario 1
Files sent over to an Amazon S3 location, with PID_ALIAS="XYZCustomer" and with Google Advertiser IDs in the file content.
E.g. incremental files:
-
S3_1234_20914_XYZCustomer_iter_1486140844000.sync.gz -
S3_1234_20914_XYZCustomer_iter_1486140844000001.sync.gz -
S3_1234_20914_XYZCustomer_iter_1486140844000002.sync.gz
E.g. full files:
-
S3_1234_20914_XYZCustomer_full_1486140844000.sync.gz -
S3_1234_20914_XYZCustomer_full_1486140844000001.sync.gz
Scenario 2
Files sent over to FTP location, without PID_ALIAS and with Apple Advertiser IDs in the file content:
E.g. incremental files:
-
ftp_1234_20915_iter_1486140843000.sync.gz -
ftp_1234_20915_iter_1486140843000001.sync.gz
E.g. full files:
-
ftp_1234_20915_full_1486140843000.sync.gz -
ftp_1234_20915_full_1486140843000001.sync.gz
Scenario 3: Files sent over to FTP location, with PID_ALIAS="XYZCustomer" and with 3rd party User ID in the file content ( Vendor ID=45454):
E.g. incremental files:
-
ftp_1234_45454_XYZCustomer_iter_1486140843000.sync.gz -
ftp_1234_45454_XYZCustomer_iter_1486140843000001.sync.gz -
ftp_1234_45454_XYZCustomer_iter_1486140843000001.sync.gz
E.g. full files:
-
ftp_1234_45454_XYZCustomer_full_1486140843200.sync.gz -
ftp_1234_45454_XYZCustomer_full_1486140843200001.sync.gz
Outbound Data File Contents: Syntax and Parameters
Describes the required fields, syntax, and conventions used to organize information in an outbound data file. Format your data according to these specifications.
The style elements (monospaced text, italics, brackets [ ] ( ), etc.) in this document indicate code elements and options. See Style Conventions for Code and Text Elements for more information.
Syntax
Fields in the data file appear in this order:
UUID<SPACE>SEGMENT_1,SEGMENT_2<SPACE>REMOVED_SEGMENT_,...
Parameters
The table lists variables that define the contents of a data file.
| Parameter | Description |
|---|---|
| |
A unique user ID assigned by Audience Manager . |
| |
Separate the UUID and segment data with a space |
| |
The segment ID that a visitor belongs to. Separate multiple segments with a comma. |
| |
The segment ID from which the user was disqualified. Separate multiple segments with a comma. With a full synchronization, you can ignore the removed segments because the data file will contain the complete list of current segments for the user. Usually, you want to know about segments a user belongs to rather than those they've been removed from. See also Outbound Data File Name: Syntax and Examples . |
Example: Basic File Format
A properly formatted data file could look similar to the following sample. This file entry indicates a user qualifies for segments 24, 26, and 27. As required, a space separates the UUID and segment IDs. Another space separates the sets of segment IDs. In this example, a user belongs to segments 24, 26, and 27. They’ve been removed from segments 25 and 28.
59767559181262060060278870901087098252 24,26,27 25,28
Business.Adobe.com resources
Resources
Adobe Account
