Describes the required fields, syntax, naming conventions and file sizes you need to follow when sending data to Audience Manager. Set the names and sizes of your files according to these specifications when you send data to an Audience Manager FTP directory.
We are gradually phasing out support for FTP configurations. While inbound data file ingestion is still supported in existing FTP integrations, we strongly recommend using Amazon S3 to onboard offline data for new integrations. See Amazon S3 Name and File Size Requirements for Inbound Data Files for details.
The text styles (monospaced text
, italics, brackets [ ]
( )
, etc.) in this document indicate code elements and options. See Style Conventions for Code and Text Elements for more information.
FTP file names contain the following required and optional elements:
ftp_dpm_DPID[_DPID_TARGET_DATA_OWNER]_TIMESTAMP(.sync|.overwrite)[.SPLIT_NUMBER][.gz]
For other accepted file name formats, see Custom Partner Integrations.
Audience Manager only processes ASCII and UTF-8 encoded files.
The table defines the elements in an FTP file name.
File Name Element | Description |
---|---|
|
The path to and name of your Audience Manager FTP directory. Contact your Account Manager for the FTP directory and credentials. |
|
An lD that tells Audience Manager if a data file contains your own user IDs, Android IDs, iOS IDs, or other IDs belonging to global data sources. Accepts the following options:
Note: Do not mix ID types in your data files. For example, if your file name includes the Android identifier, don't put iOS IDs or your own IDs in the data file. |
|
This field tells Audience Manager which data source to onboard data to. This field is mandatory if you set the DPID to an Android ID or iOS ID or another ID belonging to global data sources. This lets Audience Manager link the file data back to your organization. Important note: You do not need to request a mapping for existing data sharing relationships (for target data sources belonging to other companies into which you onboarded data prior to March 14, 2022). The mapping is also not required when onboarding data into target data sources that belong to your PID. For example:
|
|
Synchronization options that include:
|
|
An integer. Used when you split large files into multiple parts to improve processing times. The number indicates which part of the original file you're sending in. For efficient file processing, split your data files as indicated:
See the first 2 file name examples below. |
|
A 10-digit, UTC UNIX timestamp in seconds. The timestamp helps make each file name unique. |
|
Gzip is the allowed compression format for an FTP file name. If you use file compression, make sure the file name has the proper extension. Compressed files must be 3 GB or smaller. If your files files are larger, please talk to Customer Care. Although Audience Manager can handle large files, we may be able to help you reduce the size of your files and make data transfers more efficient. See File Compression for Inbound Data Transfer Files . |
The following examples show properly formatted file names. Your file names could look similar.
ftp_dpm_478_1366545717.sync.1.gz
ftp_dpm_478_1366545717.sync.2.gz
ftp_dpm_478_1366545717.overwrite
Download the sample file if you need additional examples. This file is saved with the .overwrite
file extension. Open it with a simple text editor.
Consider the figures below for fastest/earliest processing of your files as well as for file size limitations when you send data to an Audience Manager / FTP directory.
File Type | Optimal Size | Maximum Size |
---|---|---|
Compressed | 200-300 MB |
3 GB |
Uncompressed | 1 GB |
5 GB |