Lifesight requires this data in the exact format per the instructions below in order to compute exposed audiences using the DOOH site location and ad play time-stamp data.
1. For Programmatic DOOH campaigns, Adlogs are sourced from a DSP.
2. For DOOH Direct IO, Adlogs are sourced via Media Owner Content Management System or Seedooh. Once collated and formatted in the required format, the client then needs to supply the Adlogs to Lifesight.
The DOOH ad log file format must be a csv file with the headers below :
oohid, latitude, longitude, radius, ad_start_time_utc, ad_play_time, ad_duration_in_seconds, creative, lineid
oohid: Unique screen ID
latitude : Of Screen location
longitude : Of Screen location
radius: Radius around the screen (recommended: 50m if not predefined)
ad_start_time_utc: Ad start time in epoch format
ad_play_time: Actual ad play time in epoch format (same as ad_start_time if unavailable)
ad_duration_in_seconds: Total seconds the ad ran/booked
creative: Specific creative name
lineid: Specific line ID/name
Example of the ad log file :-
Please note:
ad_start_time_utc and ad_play_time need to be in epoch date format. epoch date time is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), not counting leap seconds (in ISO 8601: 1970-01-01T00:00:00Z). To convert to the epoch time format please use this link
Data must be provided for all headers & fields. All fields are mandatory
Files must follow the header format provided with no blank values or rows. Headers are case-sensitive. Do not use any caps. If there is any missing/blank values, our system will not be able to process the file and will send an alert (once processed on Thursdays) which will be passed on to clients
Make sure to cross-check if the adlog files have data of ALL dates included in your campaign along with respective ad time play
oohID should be unique to a particular latlong
Billboard name in our report will be a concatenation of oohID, creative & line ID
Please follow the steps to one of these source types to integrate your Ad log data source.
Cloud Storage (Recommended) | File upload |
If your CSV data file is residing in a cloud storage location, you can integrate this source type to securely extract your data from the location. | If your Ad log data resides in a csv file, you can upload the file with our File Upload source option in a CSV format.
|
If there are multiple DSPs/media owner, the client or agency should upload separate files for each DSP/media owner into the cloud storage bucket.
Ensure that adlogs from all DSPs/media owner cover the same campaign duration - please refer to the example in point 4
| If there are multiple DSPs/media owner, the client/agency is to collate the data into one file |
Files can be greater than 50MB | Combined file should be lesser than 50MB |
Should be uploaded fortnightly with adlogs from each media owner/DSP for the previous two weeks. Adlogs should be new/incremental and not include adlogs from prior transfers.
Ex: If the campaign is running on DSP 1 & DSP 2, on the 15th day of the campaign, adlogs from each DSP is to be uploaded with data from Day 1 to Day 14 in the bucket
All adlogs to be added within the attribution window
| Should be uploaded only once after the campaign has ended |
Campaign insights will be viewable after our processing job occurs on Thursday every week | Campaign insights will be viewable only after the campaign ends |