Find your study below, supply what its entry asks for, by the date the entry names. Most delays come from the approval rather than from the work.
What each study needs from you
Web attribution: the AdQuick pixel installed on your site, as a JavaScript tag or an image tag through your tag manager. Live before launch, and allow two weeks. Your development team or agency signs off.
App attribution: a connection to your mobile measurement partner, for example AppsFlyer, which needs the app ID plus authorization and no SDK work. Device IDs have to arrive in standard IDFA or AAID format. Hashed device IDs cannot be matched, because our exposure dataset does not use the same hash, so a hashed file returns zero matches. Before launch. Whoever owns your MMP signs off.
Footfall attribution: a location list and a radius, as addresses or coordinates uploaded to store attribution. Before launch where possible. Marketing signs off.
Causal and sales lift: daily events by market, plus at least five markets with no OOH running, as a CSV of date, event name, number of events, and market. Six months of history is the minimum and twelve is preferred. The study can start mid-flight, with the final upload roughly two weeks after the campaign ends. Your performance or analytics team signs off.
Search lift: brand terms that have had search activity in the past two months, plus competitor terms, as a list. Any time, including after the flight. Marketing signs off.
Halo effect: view or read access to Google Ads, Google Analytics, and Facebook, through OAuth authorization or a manual export. Before launch, with twelve months of pre-period preferred. Anyone with account access signs off.
Brand lift: a brief with your KPIs and survey questions, plus creative. The brief goes in the platform and the creative is sent separately by email. At least one week before launch, ideally two. Marketing signs off, along with whoever owns the creative.
Sales lift has no connector, so that handoff is an upload rather than an integration. The CSV template is not linked in the product either, so ask us for it rather than building your own file.
The three things that actually slow this down
Development resource for the pixel: two weeks of notice, and it is still the most common cause of a late start. Where tag manager access already exists, the path is much shorter.
Internal approval for the events export: causal lift needs data that usually lives with a performance or analytics team rather than with the person buying the media. Start that request early, because the file itself takes minutes.
Account authorization: halo effect needs view or read access to the ad accounts, which is a smaller ask than people assume and worth raising directly when the request stalls.
What needs nothing from you
Search lift, beyond a term list; the run itself is initiated on our side rather than by you. Device ID passback, which is included and used by the large majority of customers. Attribution reporting itself, once the pixel is in.
Exposure reporting begins populating around five days after launch, with digital units lagging further while operator play logs arrive.