MI: Submitting OOH (Out of Home) Exposure File to Factual
Factual's Measurement Intelligence solution enables you to measure the impact of your Out of Home (OOH) campaign. To produce Measurement Intelligence, Factual may receive an exposure file representing users exposed to the OOH campaign. This document describes how to format the Out of Home exposure file that you send to Factual.
File Name
For the filename, please include your company name, the name of the chain or store locations that are being measured, the phrase “OOHExposure” in the file name, and the campaign start and end dates, separated by dashes (“-”):
[CompanyName]-[ChainName]-OOHExposure-YYYYMMDD-YYYYMMDD.tsv
Do not include any non-alphanumeric characters (spaces, underscores, apostrophes, etc.) in the chain name. As an example, if your company name is AgencyX and you are measuring visits to StoreX from September 1, 2019 to September 30th, 2019, the filename should be:
AgencyX-StoreX-OOHExposure-20190901-20190930.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 newline. The header should be included in the first line of the file.
Index | Field | Type | Description | Example |
---|---|---|---|---|
1 | Device_ID | String; required | Device ID that was exposed to the ad. ID must be the unhashed identifier for advertising (e.g., Apple’s IFA, Android’s Advertising ID). | f66f31a5-461c-441a-a48e-582351763349 |
2 | Exposure_Timestamp | String; required | Number of seconds since the Unix epoch — 00:00:00 UTC on 1 January 1970. | 1506815998 |
3 | Campaign_ID | String; required | Campaign identifier. | BrandX_Campaign123 |
4 | Placement_ID | String; optional | Optional attribute of the OOH advertisement (i.e. Vendor, DMA/City, etc). This attribute will be reported against in Factual’s Measurement Dashboard. | Los Angeles DMA |
5 | Ad_ID | String; optional | A unique identifier for a specific OOH board. | A275 |
6 | Ext1 | String; optional | Optional custom attribute of the OOH advertisement (i.e. Name, Vendor, DMA, etc). Up to 5 custom parameters are supported. This attribute can be broken out for reporting purposes. | Transit Shelter |
7 | Ext2 | String; optional | Optional custom attribute of the OOH advertisement (i.e. Name, Vendor, DMA, etc). Up to 5 custom parameters are supported. This attribute can be broken out for reporting purposes. | Vendor X |
8 | Ext3 | String; optional | Optional custom attribute of the OOH advertisement (i.e. Name, Vendor, DMA, etc). Up to 5 custom parameters are supported. This attribute can be broken out for reporting purposes. | - |
9 | Ext4 | String; optional | Optional custom attribute of the OOH advertisement (i.e. Name, Vendor, DMA, etc). Up to 5 custom parameters are supported. This attribute can be broken out for reporting purposes. | - |
10 | Ext5 | String; optional | Optional custom attribute of the OOH advertisement (i.e. Name, Vendor, DMA, etc). Up to 5 custom parameters are supported. This attribute can be broken out for reporting purposes. | - |
Providing Control Group Exposures to Factual
If you have set aside your own control group for Factual to conduct a conversion lift study, you must designate a placement or placements for the control group and provide the corresponding ID(s) of those control group placements to your account manager. Control group impression data must follow the same format as described above. A timestamp must be provided. Impressions can either be included in the main exposure file or in a separate file. Factual will then be able to do the conversion lift study in the course of generating the Measurement Intelligence dashboard.
If you do not set aside your own control group, but want Factual to conduct a conversion lift study, Factual will to generate a control group for a conversion lift study.
Examples
The following is an example of a compliant file. Note the header is included in the first line of the file.The file has the following fields: Device_ID, Exposure_Timestamp, Campaign_ID, Placement_ID, Ad_Id
Device_ID | Exposure_Timestamp | Campaign_id | Placement_id | Ad_Id |
---|---|---|---|---|
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx76C9 | 1495383384 | campaignId1 | placementId1 | adId0 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx13H4 | 1495383384 | campaignId1 | placementId0 | adId2 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx8HWE | 1495383384 | campaignId1 | placementId2 | adId1 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx42N4 | 1495383384 | campaignId1 | placementId0 | adId3 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx4U26 | 1495383384 | campaignId1 | placementId3 | adId2 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx433A | 1495383384 | campaignId1 | placementId1 | adId4 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx9H3N | 1499610910 | campaignId1 | placementId1 | adId4 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx2T32 | 1499610910 | campaignId1 | placementId4 | adId0 |
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx43GG | 1499610910 | campaignId1 | placementId2 | adId1 |
Updated over 3 years ago