FTP Name and File Size Requirements for Inbound Data Files

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.

WARNING

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.

NOTE

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.

File Name Syntax

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.

NOTE

Audience Manager only processes ASCII and UTF-8 encoded files.

Name Elements

The table defines the elements in an FTP file name.

File Name Element Description

ftp_dpm_

The path to and name of your Audience Manager FTP directory. Contact your Account Manager for the FTP directory and credentials.

DPID

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:

  • Data Source ID (also known as Data Provider ID): This is a unique ID that Audience Manager assigns to a data source (refer to the Audience Manager index of IDs ). Use this assigned ID in a file name when sending in data that contains your own user IDs. For example, ...ftp_dpm_21_123456789.sync tells Audience Manager to onboard data to IDs belonging to data source 21.
  • Android IDs (GAID): Use ID 20914 in a data file name if it contains Android IDs. You need to use the field _DPID_TARGET_DATA_OWNER when you use Android IDs. For example, ...ftp_dpm_20914_DPID_TARGET_DATA_OWNER_123456789.sync tells Audience Manager that the data file contains Android IDs only and the IDs should qualify for the traits belonging to the _DPID_TARGET_DATA_OWNER data source.
  • iOS IDs (IDFA): Use ID 20915 in a data file name if it contains iOS IDs. You need to use the field _DPID_TARGET_DATA_OWNER when you use iOS IDs. For example, ...ftp_dpm_20915_DPID_TARGET_DATA_OWNER_123456789.sync tells Audience Manager that the data file contains iOS IDs only and the IDs should qualify for the traits belonging to the _DPID_TARGET_DATA_OWNER data source.
  • IDs belonging to other global data sources: You can onboard Roku IDs for Advertising (RIDA), Microsoft Advertising IDs (MAID), and other IDs. Use the ID corresponding to each data source, as described in the global data sources article.

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.

_DPID_TARGET_DATA_OWNER

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.

For example:

  • ...ftp_dpm_33_21_1234567890.sync tells Audience Manager that you're qualifying customer IDs belonging to data source 33 for traits or signals belonging to data source 21.
  • Android IDs (GAID): ...ftp_dpm_20914_21_1234567890.sync tells Audience Manager that the data file contains Android IDs only and the IDs should qualify for the traits belonging to data source 21.
  • iOS IDs (IDFA): ...ftp_dpm_20915_21_1234567890.sync tells Audience Manager that the data file contains iOS IDs only and the IDs should qualify for the traits belonging to data source 21.
  • IDs belonging to other global data sources: ...ftp_dpm_121963_21_1234567890.sync tells Audience Manager that the data file contains Roku IDs only and the IDs should qualify for the traits belonging to data source 21. Use the ID corresponding to each data source, as described in the global data sources article.

(.sync |.overwrite)

Synchronization options that include:

  • sync: Normal scenario when third-party data providers send traits on a per-user basis to be added or removed in the Audience Manager system.
  • overwrite: Lets customers and data providers send a list of traits on a per-user basis that should overwrite all of this user's existing traits for a given data source in Audience Manager. You do not need to include all of your users in an overwrite file. Include only those users that you want to change. Traits that are not assigned to the target data source will not be erased.

[SPLIT_NUMBER]

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:

  • Uncompressed: 1 GB
  • Compressed: 200-300 MB

See the first 2 file name examples below.

TIMESTAMP

A 10-digit, UTC UNIX timestamp in seconds. The timestamp helps make each file name unique.

[.gz]

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 .

File Name Examples

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.

Accepted File Sizes

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

On this page