In this guide
Before launch, compare the campaign setup with the approved brief. Check the dates and time zone, budget, audience, ads, landing pages, and measurement. Record who checked each item and what still needs a decision.
Use the checklist below as a starting point. Each item needs evidence: a setting checked against the brief, an approved asset version, or a recorded test result. A checked box by itself does not show what was verified.
Before launch
Tick the items as you work. Checks stay on this page until it is reloaded; they are not saved. Print the page to keep a copy with the campaign record.
- Approved brief: the objective, budget, currency, audience, placements, and primary success measure are agreed.
- Dates and time zone: the start and end times match the brief, including the platform's reporting time zone.
- Budget and delivery: spend limits and delivery goals are correct; any platform fees are understood.
- Creative versions: every required placement has the approved ad file, offer, language, and destination.
- Creative behavior: the ad renders correctly, controls work, and video or audio has been reviewed in full.
- Click path: the actual ad link reaches the approved page after redirects; required tracking parameters survive.
- Targeting and exclusions: geography, devices, audience rules, and exclusions match the plan.
- Frequency and eligibility: required limits are set, and restrictions have been checked for unintended conflicts.
- Measurement: the team agrees what counts as an impression, click, or conversion and which reports will be used.
- Second review: another reviewer has compared the setup with the brief and recorded unresolved issues.
- Launch decision: the responsible person has approved launch or accepted specific, documented limitations.
- Monitoring handoff: someone owns the first delivery check and knows when to escalate an issue.
Decide what blocks launch
A wrong landing page, an unapproved offer, an incorrect budget, or a missing required measurement setup needs resolution before launch. If the primary campaign result cannot be measured, that changes what the campaign can prove.
Some issues may be acceptable to the person responsible for the campaign. Record the impact, approval, owner, and deadline. “We'll fix it later” is not a handoff.
Use a record like this. The examples are illustrative; assign the actual owners for your campaign.
| Check | Expected result | Owner | Evidence / decision |
|---|---|---|---|
| Landing page | Approved product page opens on desktop and mobile. | Trafficking owner | Tested link, device, and test time. |
| Offer | Creative and landing page show the same approved offer. | Creative approver | Asset version and approval reference. |
| Budget | Platform limit matches the approved media budget. | Campaign owner | Setting and cost basis checked. |
| Measurement | Primary event can be observed in the agreed test process. | Measurement owner | Test result and known limitations. |
Check the live campaign
Agree the first monitoring checkpoint before launch. Its timing depends on expected delivery, reporting delay, and the consequences of a fault. A high-volume campaign may reveal problems sooner than a narrow campaign with little early activity.
- Confirm delivery has started in the intended placements or environments.
- Check the live ad and landing-page experience where testing is permitted.
- Compare spend with the campaign plan; investigate unexpected gaps.
- Confirm that expected measurement signals are arriving, allowing for reporting delay.
- Record changes, remaining issues, and the next review time.
Low volume can make percentages unstable. Look at the underlying counts before deciding that performance has changed. Use the pacing calculator for an even daily budget comparison; use the actual plan if spend is intentionally weighted by day.
Leave a usable handoff
Keep the approved brief, campaign IDs, asset versions, test evidence, launch decision, and monitoring owner together. Record later changes with a timestamp and reason.
For the asset checks, use Creative QA. If the reports disagree after launch, follow the reporting discrepancy guide.
Put this guide to work
Bulk UTM builder & checker →Campaign naming generator →Ad tag inspector →AdOpsNow Editorial
Examples use illustrative data. See our editorial standards or report a correction.