In order for us to begin setting up your ID Passback campaign, please provide the information listed below to your Cuebiq representative. The guidelines below provide help on the information requested for each field.
Table of Contents
- General Details
- Billboard File Format
- Programmatic Postings File
The start and end dates of the campaign
List of Billboards
The number of billboards from the campaign that will be monitored
Exposure File (Digital Only)
Allows us to create an impression log of the devices exposed to a programmatic campaign
Billboard File Format
In order to provide the ID Passback file, Cuebiq needs to understand which billboards we will be monitoring. The boards must be provided in the format below in order to be accepted.
The format of the file should be .csv (comma-separated file), including the following columns:
• DISPLAY_ID – unique identifier of the billboard.
• LATITUDE, LONGITUDE – precise location of the billboard > > decimal number.
• FACING – direction of billboard facing > > one and only one of these cases: N, NW, W, SW, S, SE, E, NE.
• RADIUS – visibility radius of the billboard > > scalar in meters (determined by Cuebiq based on the type of board).
• START_DATE – start date of billboard for the campaign > yyyy-MM-dd.
• END_DATE - end date of billboard for the campaign > yyyy-MM-dd.
• TYPE - type of billboard > Static or Digital.
Programmatic Postings File
In addition to the campaign overview and static billboards file, Cuebiq also will need a postings file. The postings file allows us to create an impression log of the devices exposed to a programmatic campaign.
Postings will be sent by the client to an S3 bucket with the credentials provided by a Cuebiq representative. Postings files should be a CSV files in the following format:
• DISPLAY_ID – unique billboard identifier used in billboards.csv.
• DATE – date of the programmatic display > yyyy-MM-dd.
• LOCAL_START_TIME – local start time of the programmatic display on the billboard > HH:mm:ss.
• DURATION – duration of the programmatic display > scalar in seconds.
Q: What will my ID Passback file look like?
A: It will include all of the IDs who saw the OOH campaign during the given time period. You will receive a list of the IDs that were exposed and a timestamp for which they saw the ad.
Q: What’s the level of frequency I can receive an ID Passback file?
A: We typically send ID Passback files on a post-campaign basis. However, if requested, we can provide the files on a daily basis or weekly basis.
Q: If I’m running a Digital OOH campaign and want to see IDs on a daily basis, what do I need to do?
A: In order to receive the files on a daily basis, we will need a daily postings file from you. For example, if you wanted to see the users who were exposed to the campaign on 12/4, we would need the postings file from you following a YYYYMMDD.csv convention by 12/5 at 2 PM EST named 20221205.csv. After the postings file has been dropped in the S3 bucket by 2 PM EST, we will send your ID Passback file by EOD on 12/5.
Q: Can you send back cookies?
A: No, we only send back device IDs directly. If you were interested in a cookie-based audience, we could send the list of device IDs through to Liveramp and you could target these users as a custom audience. Additional fees will apply.
Q: What other fields are available in ID Passback?
A: If the ID passback goes through Liveramp for delivery, we can only provide device ID. If delivered through S3, we can provide these additional fields if requested: Timestamp (Unix or ISO), Billboard ID, Latitude, Longitude, Zipcode, City, DMA, State, Carrier (if available), Device Type (if available), Model, Manufacturer.
Q: Is there a limit to how long displayID string can be OOH?
A: It's recommended to keep the length to within 25 characters and to avoid any special characters (i.e - %@#$&*).
Q: Where will Cuebiq deliver the ID Passback file?
A: Cuebiq will deliver the IDs via Cuebiq’s S3 bucket or via Liveramp for our client’s retrieval. Credentials will be provided for easy accessibility.
Please sign in to leave a comment.