MI: Sending OOH (Out of Home) Ad Locations to Factual
For Factual’s Out of Home (OOH) solutions, Factual may require the list of OOH ad locations used for a specific campaign (e.g., running Factual Measurement Intelligence on an OOH campaign). This document describes how to format the OOH ad locations file that you send to Factual.
File Naming
For the filename, please include your company name, the name of the campaign, and the phrase “OOHLocations” in the file name, separated by dashes (“-”). Use the following format:
[CompanyName]-[CampaignName]-OOHLocations.tsv
Do not include any non-alphanumeric characters (spaces, underscores, apostrophes, etc.) in the chain name. As an example, if your company name is MarketerX and you are sending Factual the OOH ad locations for BacktoSchoolCampaign, the filename should be:
MarketerX-BacktoSchoolCampaign-OOHLocations.tsv
File Format
Your file should be a tab-separated value (TSV) file containing the fields described in the table below. Individual records should be delimited by a new line. The header should be included in the first line of the file. Each file should include only the OOH ad locations running during a particular date range or campaign flight.
If you have more than one unique date range for your OOH campaign, please create a unique file for each unique date range.
For example, if you have one campaign flight running from 10/01-11/15, and another campaign flight running from 10/15 - 11/15, you would need to create two files, one for the OOH ads in the 10/01 - 11/15 flight, and a second for the OOH ads in the 10/15-11/15 flight.
Field | Type | Description | Example |
---|---|---|---|
Ad ID | String;required | A unique identifier for a specific OOH advertisement. | A275 |
Latitude | String;required | Latitude of the OOH advertisement. Factual strongly recommends at least 6 decimal places of precision. | 34.181072 |
Longitude | String;required | Longitude of the OOH advertisement. Factual strongly recommends at least 6 decimal places of precision. | -118.31153 |
Direction | String; optional | Direction (N, S, E or W) of the OOH advertisement; required if client desires advertisement direction to be incorporated in Factual’s deliverable. | N |
Ext1 | String; optional | Optional field with an attribute of the OOH advertisement (i.e. DMA) | Los Angeles |
Ext2 | String; optional | Optional field with an attribute of the OOH advertisement (i.e. Vendor) | `Vendor X`` |
Ext3 | String; optional | Optional field with an attribute of the OOH advertisement (i.e. Inventory type) | Inventory X |
Ext4 | String; optional | Optional field with an attribute of the OOH advertisement (i.e. Creative ID) | 123 |
Examples
The following are two examples of compliant files. Note the header is included in the first line of the file.
The first file has the following fields: Ad ID
, Latitude
, Longitude
Ad ID | Latitude | Longitude |
---|---|---|
6C9 | 34.181072 | -118.311543 |
3H4 | 34.181046 | -118.311511 |
HWE | 34.181100 | -118.311545 |
The second file has the following fields: Ad ID
, Latitude
, Longitude
, Ext1
, Ext2
, Ext3
, Ext4
Ad ID | Latitude | Longitude | Direction | Ext1 | Ext2 | Ext3 | Ext4 |
---|---|---|---|---|---|---|---|
6C9 | 34.181072 | -118.311543 | N | Los Angeles DMA | Transit Shelter | Vendor X | 69x48 |
3H4 | 34.181046 | -118.311511 | N | Los Angeles DMA | Large Format Digital | Vendor Y | 33x21 |
HWE | 34.1811 | -118.311545 | S | Los Angeles DMA | Phone Kiosk | Vendor Z | 50x26 |
Updated over 3 years ago