Name and Content Requirements for ID Synchronization Files
Describes the required fields, syntax, and naming conventions used for file-based ID synchronization. Name and organize your file contents according to these specifications.
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 and Examples
ID file names contain the following required and optional elements:
[adobe_id_] [c2c_id_] MASTERDPID_DPID [_DPID] _TIMESTAMP.sync [.SPLIT_NUMBER] [.gz]
A static prefix that identifies the file as an ID synchronization file. Use this prefix when matching device IDs to other device IDs or customer IDs (DPUUIDs).
A static prefix that identifies the file as an ID synchronization file for People-Based Destinations. Use this prefix when matching customer IDs (DPUUIDs) to hashed email addresses for People-Based Destinations.
|MASTERDPID||The master data provider ID is the parent ID of the DPIDs in the file name. Also, the first user ID in the data file corresponds to the master ID. The subsequent DPIDs are other identifiers that belong to the master. Synchronization maps DPIDs in the file name to UUIDs in the file.|
Data provider IDs. These IDs represent entities or data sources associated with the master DPID. Synchronization maps DPIDs in the file name to UUIDs in the file.
The number of DPIDs in the file name must match the number of UUIDs in the data file. For example, say your file name contains a master DPID and 3 DPIDs. Your data file must include 4 corresponding columns of UUIDs, formatted as described in the file content section below.
A 10-digit, UNIX timestamp in seconds. The timestamp helps make each file name unique.
Indicates a normal, full synchronization.
[ .SPLIT_NUMBER ]
An integer. Used when you split large files into multiple smaller files. This helps improve processing times. The number indicates which part of the original file you're sending in. See the file name examples below.
Specifies that your file is compressed with optional gzip compression.
File Name Examples
The following examples show properly formatted files names. Your file names could look similar.
For ID synchronization file naming (c2c prefix) for People-Based Destinations, see Workflow A - Personalization Based on All Online Activity Combined with Offline Data or Workflow B - Personalization Based on Offline-Only Data .
File Content Syntax and Examples
The contents of an ID file include the following elements:
UUID <tab> UUID <tab> UUID <tab> UUID
The file contains user IDs (UUID). In each row, separate the IDs with a tab. The following example shows a properly formatted ID file. Your contents could look similar.
abc123 def456 ghi789 xyz987
Synchronization Matches DPUUIDs to UUIDs
The purpose of an ID sync file is to sync the DPUUIDs from your own Data Sources with Audience Manager UUIDs. Synchronization maps the DPUUIDs from the master DPID and its related DPIDs to the Audience Manager UUIDs. Where you put the IDs in the file name and body determines how these identifiers are mapped to each other. For example, take the two sample files shown here:
- File 1: adobe_id_0_12345_1476312152.sync
- File 2: adobe_id_12345_67890_1476312876.sync
Given the sample name and contents, the IDs map together like this:
File 1 ( Download sample file )
DPID 0 = Adobe Audience Manager UUIDs
Step 1: the ID sync process will sync the DPUUIDs from DPID 12345 with the Audience Manager UUIDs in the left column. Note that the DPID "0" in the file name represents Audience Manager UUIDs.
File 2 ( Download sample file )
Step 2: the DPUUIDs from DPID 12345 have been synced in step 1 with the Audience Manager UUIDs. What this ID sync will do is sync the DPUUIDs from DPID 67890 with the Audience Manager UUIDs from step 1.
Other Format Requirements
User IDs cannot:
- Have tabs in the ID itself. Tabs are used only to separate individual IDs in the data file.
- Contain personally identifiable information (PII).
- Use URL encoding. Pass in unencoded IDs only.
Any rows that end with tabs or spaces will not be processed or realized. As a rule, make sure you keep the end of the rows clear.