Amazon S3

Sync your user with Audiens

This document will outline the cookie sync procedure for the Audiens platform.


  1. The user must already be already mapped in the Audiens system.

User mapping steps:

  1. Partner's client: The user visit a page where the Audiens pixel is present and a call is made to the endpoint.
  2. Audiens user mapping: Audiens receive the call identify the user.
  3. Audiens reply: Audiens will conclude the redirect flow with an empty 1x1 pixel.

Add the Audiens pixel

To map the user with Audiens, the partner will call the endpoint and initiate the sync procedure.

The URL must respect the following format:


Mandatory parameters:

The id of the Partner provided by Audiens during the integration kick-off.
The user identification parameter used by the Partner, it will be required to store the matching table on Audiens side.



The simplest way to implement the Audiens Mapping Service to an html page is to add an img tag with the correct formatted URL

<img src='http(s)://' />

Audiens identify the user

Audiens will match the audiens_partner_uuid with the internal profiled user.

From this point forward the audiens_partner_uuid can be used to send user data.


Whenever is possible the system will always try to deliver the invisible 1x1 pixel to avoid console/network notification.

Error codes are listed below:

Reason: Malformed request, there is something wrong with the request

Storage on S3 buckets
Send your data to Audiens using AWS S3

Amazon S3 is provided together with the access credentials :

  • Path of the folder bucket.
  • Access Key.
  • Secret Access Key.

Standard format of the data storage URL is:{partner-id}/{date-component}/{filename}


Is the partner id provided by Audiens during the integration kick-off.


  • 1245
  • 4178


Is the date of files that are provided the split is mandatory as it is used by the system to handle import.


  • 2017/01/01
  • 2017/03/10

The date component is in the format yyyy/mm/dd


The name of the file that the partner is uploading. The filename can be any format the partner desire. The only restriction is that the extension must be .gz and the file is compressed accordingly.


  • 124dfgtre_53ns.gz
  • 20170101_23456789.gz
  • 2017-01-01_11-40_123456.gz

A non mandatory format proposal: yyyymmddhis.gz example 20170101102059.gz

File content format

The content of the file must adhere at the following convention



Is the uuid provided by the partner during the cookie-sync phase, it will be used by the system to relate the segment to the user.


Can be multiple for each line, they represent the segment id of the taxonomy.



The file must not exceed the 20MB size limit

The same partner-uuid should be present only one time per data file