Quick answer
Launch QA should establish that the approved campaign is the campaign about to publish. Compare the final asset, destination, market, tracking, disclosure and run sheet against their accepted versions. Test important failure paths, assign an incident owner and record the go or no-go decision. Unresolved critical dependencies should block the affected placement rather than disappear in a general readiness score.
Campaign leads coordinating production, analytics, compliance and creator teams at launch.
Freeze the exact launch package
Create a manifest containing asset identifiers, publishing accounts, destination URLs, campaign identifiers, planned windows and approval references. Give it a version and name the person who can change it. The manifest should point to final materials rather than a folder containing both drafts and approved files.
Our editorial recommendation is to freeze the package early enough for a meaningful rehearsal, with a controlled exception process for late changes. A changed link can alter the operator, language, market or tracking path even when the visible text is identical. Treat those changes as reviewable events. The launch lead needs a record of what was tested, not merely a statement that somebody tested something last week.
Verify eligibility and creative approval separately
Check that the intended product, creator, market and channel match the scope reviewed by the qualified owner. For UK-facing gambling advertising, ASA guidance on youth appeal and creator suitability illustrates why a generic adult-audience label is insufficient. Record the actual decision and conditions rather than assuming an old campaign’s approval still applies.
Then compare the final creative with the approved version. Confirm that the destination, offer language and supporting claims have not drifted during editing. If a material condition is unresolved, block that placement and identify the owner needed to resolve it. Production readiness cannot substitute for eligibility, and a deadline should not turn an unreviewed change into an accepted one.
References: ASA — Odds are your gambling post is an ad
Test destinations and measurement without real customer activity
Open the approved destination on relevant device sizes and confirm its language, branding and expected behavior. Verify that campaign parameters survive the authorized redirect path. Use the operator’s approved test method for tracking events, with test identifiers clearly excluded from commercial reporting. Do not generate real gambling activity simply to produce a convenient conversion screenshot.
Capture the test time, observed result and limitation. A successful page load does not prove every later attribution step works. If an event cannot be tested in the available environment, mark it unverified and obtain an explicit measurement decision from the responsible owner. Keep QA observations distinct from real campaign performance so synthetic events do not inflate launch results.
Rehearse the audience-facing presentation
Preview the whole rendered scene: audio, overlays, captions, disclosure, link placement and any moderator messages. FTC guidance makes sponsorship transparency an audience-facing question; the production team should therefore inspect what a viewer encounters rather than relying solely on an approval document. Confirm that the approved message is still accurate in the final composition.
Check the handoff between host, producer and moderator. Each person should know their cue, the current asset and the backup contact. Include a short failure drill, such as a destination becoming unavailable. The purpose is to reveal coordination gaps before publication, not to rehearse a perfect sequence that assumes every dependency behaves exactly as expected.
References: FTC — Endorsement Guides: What People Are Asking
Use severity and ownership to make the launch decision
Classify issues by their effect on the specific placement. An unapproved product or materially misleading statement is different from a cosmetic spacing problem. Assign each issue an owner, next action and decision deadline. Avoid a percentage-complete score that suggests several minor successes can cancel out one critical failure.
Synthetic example: all creative checks pass, but the final destination redirects to a different market version. The launch lead holds the affected placement until the correct destination is restored and retested. An unrelated approved asset may proceed only if it is genuinely independent. This is a recommended decision pattern, not a universal rule about contractual cancellation or the legal consequences of a delay.
Monitor the launch and preserve the tested state
Name the person watching publication and the person authorized to stop an affected placement. Record actual publication times, final URLs and any deviation from the manifest. Continue monitoring long enough to catch the handoffs that matter for the agreed scope, and specify when responsibility transfers to ordinary campaign management.
After launch, preserve the manifest, test evidence and issue resolution record. If a later report reveals an attribution discrepancy, these records help distinguish a launch configuration problem from a subsequent change. The worksheet below provides a compact decision log. Adapt its checks to the platform and campaign instead of treating a completed template as a guarantee that every possible defect has been eliminated.
| Decision | Required record | Owner |
|---|---|---|
| Manifest | Final asset and URL versions | Producer |
| Eligibility | Scope matches approval | Reviewer |
| Destination | Device, language and redirects | QA owner |
| Measurement | Authorized test and limitations | Analytics lead |
| Rendered content | Audio, visuals and disclosure | Brand approver |
| Go or no-go | Open issues and decision | Launch lead |
| Monitoring | Stop authority and backup | Incident owner |
Working template
| Decision or check | Campaign value | Responsible owner | Evidence or due date |
|---|---|---|---|
| Manifest | — | Producer | Final asset and URL versions |
| Eligibility | — | Reviewer | Scope matches approval |
| Destination | — | QA owner | Device, language and redirects |
| Measurement | — | Analytics lead | Authorized test and limitations |
| Rendered content | — | Brand approver | Audio, visuals and disclosure |
Frequently asked questions
Who makes the final go or no-go decision?
Assign one launch lead who can see the required approvals and unresolved issues. Specialist reviewers still own their decisions; the launch lead coordinates them rather than overriding missing eligibility or creative approval.
Can launch proceed with tracking uncertainty?
That requires an explicit commercial and measurement decision about the affected scope. Record what cannot be measured and do not later present unverified attribution as complete.
Should every small change trigger full QA again?
Retest the affected dependencies. A destination or claim change may need substantial review; a minor visual correction may need only a rendered check. Document the reasoning and the tested version.
Sources and scope
Sources checked September 22, 2026. Numerical examples are illustrative unless explicitly identified otherwise.
- ASA — Odds are your gambling post is an ad — UK gambling advertising guidance on youth appeal and creator suitability; checked September 22, 2026.
- FTC — Endorsement Guides: What People Are Asking — US endorsement guidance, including advertiser responsibilities and disclosure; checked September 22, 2026.
Related reading
Plan your next campaign with us
Tell us the market, platform and decision you need to resolve.
Discuss your campaign with Octo Media