Outbound Data File Name: Syntax and Examples

Describes the required fields, syntax, and conventions used to name an outbound data file.

Note: 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 required and optional elements:



The table defines the elements in an outbound data file name.

File Name Element Description


Refers to the data transfer methods. Transfer methods include:

  • FTP - Transfer using SFTP
  • Amazon S3 - Transfer to Amazon AWS


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:

  • 20914 - Google Advertiser ID (raw, unhashed)
  • 20915 - Apple ID for Advertisers (raw, unhashed)
  • Vendor ID - 3rd party user IDs (web/cookie)


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 iter or full.

  • iter: Indicates an "iterative" or incremental synchronization. An incremental file contains only new data collected since the last synchronization..
  • full: Indicates a "full" synchronization. A fully synchronized file contains old data and any new data collected since the last synchronization.


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 original file will not have any split number. The first split file will start with 1. See examples below.

.gz (optional)

GZIP compression.

File Name Examples

Scenario 1: files sent over to 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_1486140844000-1.sync.gz
  • S3_1234_20914_XYZCustomer_iter_1486140844000-10.sync.gz
E.g. full files:
  • S3_1234_20914_XYZCustomer_full_1486140844000.sync.gz
  • S3_1234_20914_XYZCustomer_full_1486140844000-1.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_1486140843000-1.sync.gz
E.g. full files:
  • ftp_1234_20915_full_1486140843000.sync.gz
  • ftp_1234_20915_full_1486140843000-1.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_1486140843000-1.sync.gz
  • ftp_1234_45454_XYZCustomer_iter_1486140843000-10.sync.gz
E.g. full files:
  • ftp_1234_45454_XYZCustomer_full_1486140843200.sync.gz
  • ftp_1234_45454_XYZCustomer_full_1486140843200-1.sync.gz