RTI audience file format reference

If you are a supported RTI provider that facilitates audience transactions, you can send your audience files to Index Exchange (IX) using SFTP to be processed within 15-20 minutes by the Audience Manager system.

Note: This audience format is only available for select RTI providers. If you have any questions, contact your IX Representative.

File formats

IX supports a dual file format for an audience file. With a dual file format, IX expects to receive a single audience for each pair of files (multi-audience upload is not yet supported). Each audience is represented by two files: the data file and meta file. Both the data and meta files are required for every audience upload, including any changes to existing audiences. For more information on these file formats, refer to the table below.

file type file name file format contents

file type	file name	file format	contents
Data	`<audienceID>.gz`	gzip	List of RTI identifiers separated by newline characters.
Meta v1.1	`<audienceID>.json`	json	Meta file version, audience scope, audience name, audience ID, source audience ID, advertiser account ID, file name, export timestamp. With the addition of audience scope in meta file v1.1, advertisers can run their audience across all eligible IX publishers with a single file upload. A meta file with `audience_scope` set to `PLATFORM` increases audience scale dramatically for advertisers. If `audience_scope` is set to `DIRECT`, advertisers can transact on audiences directly with a specific publisher.
Meta v1.0	`<audienceID>.json`	json	Audience name, audience ID, source audience ID, advertiser account ID, IX publisher ID, file name, export timestamp.

Data

<audienceID>.gz

gzip

List of RTI identifiers separated by newline characters.

Meta v1.1

<audienceID>.json

json

Meta file version, audience scope, audience name, audience ID, source audience ID, advertiser account ID, file name, export timestamp.

With the addition of audience scope in meta file v1.1, advertisers can run their audience across all eligible IX publishers with a single file upload. A meta file with audience_scope set to PLATFORM increases audience scale dramatically for advertisers. If audience_scope is set to DIRECT, advertisers can transact on audiences directly with a specific publisher.

Meta v1.0 <audienceID>.json json Audience name, audience ID, source audience ID, advertiser account ID, IX publisher ID, file name, export timestamp.

The data and meta files are linked by the audience ID and the file name, as shown in the following example:

Data file name: 1a956a17-7f7d-48fd-92ad-ade76e154a6b.gz

Meta file name: 1a956a17-7f7d-48fd-92ad-ade76e154a6b.json

List of meta file fields

field	supported meta file version	description
`meta_version`	1.1	Version of the meta file, where `1.0` is version 1.0 and does not support platform audience scope `1.1` is version 1.1 and supports platform audience scope
`audience_scope`	1.1	The scope of audience matching. `PLATFORM` specifies that audiences can match across the platform (all eligible IX publishers) `DIRECT` specifies that audiences match exclusively on a specific publisher
`audienceName`	All	Name of the audience or segment. This name is what appears in the IX App.
`audienceID`	All	Provider-specific identifier for a given audience. Uploads with the same `audienceID` are treated as updates to the audience. Uploads with unique `audienceID`s are treated as separate, new audiences.
`advertiserAccount_id`	All	Unique Identity identifier for the advertiser or buyer of the audience assigned by the RTI provider.
`publisher_id`	All	IX publisher identifier. A `publisher_id` is only needed when `audience_scope` is set to `DIRECT`.
`exportTimestamp`	All	Time, in UTC (Coordinated Universal Time), of when the audience was exported.

Meta file version 1.1 examples

The following meta file has a direct audience scope:

{
	"meta_version": "1.1",
	"audience_scope": "DIRECT",
	"audienceName": "New Customers Signups",
	"audienceID": "1a956a17-7f7d-48fd-92ad-ade76e154a6b",
	"advertiserAccount_id": "Netflix",                            
	"publisher_id": 183728,            
	"exportTimestamp": "2018-06-11 13:20:35"
}

The following meta file has a platform audience scope:

{
	"meta_version": "1.1",
	"audience_scope": "PLATFORM",
	"audienceName": "New Customers Signups",
	"audienceID": "1a956a17-7f7d-48fd-92ad-ade76e154a6b",
	"advertiserAccount_id": "Netflix",                            
	"exportTimestamp": "2018-06-11 13:20:35"
}

Meta file version 1.0 example

{
	"audienceName": "New Customers Signups",
	"audienceID": "1a956a17-7f7d-48fd-92ad-ade76e154a6b",
	"advertiserAccount_id": "Netflix",                            
	"publisher_id": 183728,            
	"exportTimestamp": "2018-06-11 13:20:35",
}