Server to Server Technical Specs - Outbound from Lotame - Batch File Processing

Supported File Transfer Mechanisms

AWS S3 Transfer

Lotame can deliver files to the client's AWS s3 bucket. Lotame requires the following to support this method.

• AWS Secret Key.
  • Please provide it securely by coordinating with your Technical Account Manager for options.
• AWS Bucket Name.
• AWS access permissions to upload and create directories.
• A directory structure as noted below based in the root of the S3 bucket.
  • Either <YYYYMMDDHH>/<clientDir> or <clientDir>/<YYYYMMDDHH>. 
  • The <clientDir> value will be provided by Lotame and it is static and will not change. <YYYYMMDDHH> value is the GMT date + hour of the file contents and will be created by our upload process for each file delivery.

Google Cloud Storage

Lotame can deliver files to the client's Google Cloud Storage bucket. Lotame requires the following to support this method.

• Service Account HMAC Keys.
  • Please provide it securely by coordinating with your Technical Account Manager for options.
• Storage Bucket Name & Path
• Google Cloud Project ID
• Permissions to upload files and create directories
• A directory structure as noted below based in the root of the Cloud Storage bucket.
  • Either <YYYYMMDDHH>/<clientDir> or <clientDir>/<YYYYMMDDHH>. 
  • The <clientDir> value will be provided by Lotame and it is static and will not change.
  • <YYYYMMDDHH> value is the GMT date + hour of the file contents and will be created by our upload process for each file delivery.

sFTP Transfer

Lotame Hosted sFTP Server

Lotame provides an sFTP server for file transfer. When clients provide an SSH public key, Lotame will return the sFTP user account and directory path to retrieve the files.  

• Hostname - booth.crwdcntrl.net
• Port - standard (22)
• A directory structure as noted below based:

Either <YYYYMMDDHH>/<clientDir> or <clientDir>/<YYYYMMDDHH>.  The <clientDir> value will be provided by Lotame and it is static and will not change. <YYYYMMDDHH> value is the GMT date + hour of the file contents and will be created by our upload process for each file delivery.

Client Hosted sFTP Server

In the case where the client wants to the files sent to their own sFTP server, we can support that by doing the following: 

1. Lotame will provide you with our SSH public key which you will need to apply to your server.
2. Provide Lotame the DNS or IP address of the sFTP server.
3. Provide Lotame the username that will allow our SSH key to login.
4. A directory structure as noted below based at the root of the username's path.

<clientDir>= Your Technical Account Manager will coordinate with naming of this directory. Once created, they are static. 

<clientDir>/<YYYYMMDDHH> is the GMT date + hour of the file contents and will be created by our upload process for each file delivery.

Data File Types

Lotame supports sending files as comprehensive or deltas from the prior file.

1. Comprehensive – Lotame will send all users that had activity for the day, and their comprehensive audience membership list.
2. Incremental – Lotame will only send updates:

   1. A new user is created in the Lotame platform

   2. An existing user qualified for a new audience 

Please discuss with your Lotame Technical Account Manager options on which file type works best for your integration.

Note: Delta file types require a periodic comprehensive file sent to ensure our segments do not get out of sync. The default is 30 days, but you can work with your Lotame Technical Account Manager to decide a different timeframe that is best for your business needs.

Data File Specifications

Lotame sends 5 files for the Outbound Batch processing.

1. Audience Membership file which contains all the UserIDs and their associated audiences.
2. Audience Metadata file which contains a mapping of audience ID to human-readable description of that audience.
3. Audience Membership MD5 checksum file to be used to validate the correctness of the Audience Membership file delivery.
4. Audience Metadata MD5 checksum file to be used to validate the correctness of the Audience Metadata file delivery.
5. A DONE file to denote to your processing that Lotame is done with file uploads for that day.

Audience Membership File

This file has a static filename of audiencemembership.tsv.gz. This file is a gzip encoded file to be file space efficient and minimize transfer timings. 

The file is tab-separated between the two data points of UserID and Audiences. The UserID are unique in the file.

Supported UserID Identifiers

To see our full list of supported CTV IDs, please see our CTV Overview page.

Lotame Profile IDs (PID)/ Third Party IDs (TPID), Mobile Advertising Device IDs and CTV (OTT) IDs can be combined in the same file, or separated into multiple files if requested.  

• CTV (OTT) file can be further broken down into multiple files by each device type (Roku, Apple TV etc) on request.

• Third Party IDs (TPID) and Lotame Profile IDs (PID) cannot be combined in the same file.  

Example File

e1ec57335975afb3eb81c898d09cf9b9    395338,285289
cac945ff3946e16842af8c0951e7b9ee    395338
PANO:0bed52425b1b65dec4cf2373119b16d53938b85871267f094f2ea13a224849e5    365147,395338,296412
PANO:ac3382286397f7297242867dbd2216d539381bc632e61fafd9ba38aebf4a4a30    285289,395338,375412
IDFA:C87CB4B6-87A1-42E3-A994-B3734A0D4F69    395338,375412
IDFA:E860367A-E08C-406F-9472-C57A916A2889    285289,395338
GAID:000958bf-4c0d-4c68-9ff5-d6bbb1b08739    358945,285289
GAID:2v2fbcab-13b1-4350-be7f-fd21d0924p2b    395338

Audience Metadata File

This file has a static filename of metadata.json. 

The JSON file is contains an audience object which contains an array of mapping objects. The format of the mapping object is denoted below.

Example File

{
  "audience":[
    {
      "id":"1",
      "name":"Sports Lovers"
    },
    {
      "id":"2",
      "name": "Exposed to Campaign X"
    }
  ]
}

Audience Membership MD5 Hash File

This file has a static filename of audiencemembership.tsv.gz.md5. This plain-text file only contains the MD5 hash of the gzip encoded Audience Membership. Use the MD5 hash to validate the completeness of the uploaded Audience Membership file.

Audience Metadata MD5 Hash File

This file has a static filename of metadata.json.md5. This plain-text file only contains the MD5 hash of the gzip encoded Audience Metadata file. Use the MD5 hash to validate the completeness of the uploaded Audience Metadata file.

Done File

The Done file has a filename of YYYYMMDD.done. This zero-length file will be created when all uploads by Lotame are complete for the day. Please have your processing wait on this file to exist before loading the day's files.