- 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
Documentation
File Compression for Inbound Data Transfer Files
You can compress data files when sending them to Audience Manager.
Audience Manager supports gzip (.gz) compression for inbound, asynchronous data transfers.
Audience Manager also supports uncompressed files.
IMPORTANT
We don’t support encryption on inbound files compressed using gzip (.gz).
To encrypt and compress inbound files, use PGP encryption. PGP encryption includes file compression.
Amazon S3 Compression
For delivery to Amazon S3, you must use .gz or uncompressed files. Compressed files must be 1 GB or smaller. If the files are larger, please discuss the file and transfer process with Customer Care. Although Audience Manager can handle very large files, there may be ways to reduce the file size or make transfer of data more efficient.
IMPORTANT
Your FTP client must use binary mode to transfer compressed or encrypted files. Compressed or encrypted files sent in ASCII mode will corrupt the data transfer file.
Best Practices
- Files should be .gzip compressed (and have a .gz file extension).
- The maximum compressed file size for a
.gzcompressed file is 1 GB. - Optimal split sizes, for fastest/earliest processing of your files, is approximately 1 GB uncompressed or 200-300 MB compressed.
- Amazon S3 imposes its own, 5 GB file size limit on uploaded files.
Resources
Adobe Account
Change language
Copyright © 2023 Adobe. All Rights Reserved.
