Overview
AdQuick supports automated proof-of-play (POP) delivery to ensure inventory is measurable and eligible for attribution reporting. When play logs are delivered consistently and in the required format, all applicable units receive the “AQ Verified Attribution” tag on the AdQuick platform. This article outlines the requirements, data specifications, delivery method, and common questions regarding automated play log integration.
Benefits of Integration
Visibility: Inventory appears in filters when buyers search for attribution-enabled units.
Demand: Increased eligibility for data-driven and performance-focused campaigns.
Bookings: Higher likelihood of selection compared to non-measurable inventory.
Integration Requirements
AdQuick requires row-per-play logs delivered automatically to an AdQuick-provisioned S3 bucket.
Required Specifications
Frequency
Daily (Preferred)
Weekly (Minimum)
Delivery Method
Automated upload to an AdQuick AWS S3 bucket
File Format
CSV only (PDF and Excel are not accepted)
Granularity
Row-per-play logs only
Daily/hourly summaries or aggregated counts are not accepted
Data Specifications
Your CSV export must include the following fields:
Required Fields
unit_id – Your internal unit identifier. Must match the ID used in your AdQuick inventory feed.
start_time – Exact timestamp of the play (format requirements below).
duration_seconds – Integer value representing ad duration in seconds.
creative_id – Your internal identifier for the creative asset.
campaign_id – The campaign, order, or contract ID associated with the buy.
Optional Fields
Include when available:
face_id
tab_panel_id
geopath_id
Timestamp Requirements
To ensure accurate ingestion, the timestamp must follow all formatting rules below:
Format:
YYYY-MM-DD HH:MM:SS(24-hour)Leading Zeros: Required (e.g.,
09instead of9)Timezone: UTC preferred
If using local time, include a separate timezone column or latitude/longitude for conversion.
End Time: Not accepted; must provide start_time and duration_seconds.
Examples
✅ Correct:
2025-09-04 02:05:09❌ Incorrect:
2025-9-4 2:5:9 16
How to Deliver Play Logs (S3 Automation)
AdQuick uses Amazon S3 as the secure method for automated file delivery.
Steps to Set Up Delivery
Request Credentials
Contact attribution@adquick.com. AdQuick will create your dedicated S3 bucket and provide access credentials.Automate File Delivery
Configure your system to automatically upload CSV files to the provided bucket. AdQuick can support your team during this setup.
Common Automation Methods
AWS CLI
Schedule recurring uploads using Cron or Task Scheduler.
Custom Scripts
Use Python, Node, or another language with AWS SDK support to push files programmatically.
CMS Native Tools
Some CMS platforms offer built-in export or integration options for S3 delivery.
CMS-Specific Notes
AdQuick can support integrations using data exported from common CMS platforms.
Vistar
Supports POP export workflows compatible with automation. AdQuick can coordinate with Vistar upon request.
Broadsign
Offers real-time POP export APIs capable of automated delivery to external endpoints.
Signagelive
Provides a Network API for automated reporting and export workflows.
Frequently Asked Questions
Can we send files via email?
No. Manual delivery does not qualify for “AQ Verified Attribution” status. Logs must be automated via S3.
Do you accept end_time instead of duration_seconds?
No. AdQuick requires start_time plus duration_seconds. End times are not ingested.
What happens if we miss a week of deliveries?
AdQuick’s Analytics team will contact your team to resolve the issue. Attribution status may be removed if logs are not delivered reliably.
What is an S3 bucket?
An S3 bucket is a secure storage location on Amazon Web Services. AdQuick provisions the bucket and provides you with credentials to upload your files.