Buyer readiness
Landing page launch QA worksheet
A campaign can have strong inventory, clean creative, and useful tracking, then lose the reader at the destination. This worksheet checks whether the landing page is ready to receive paid traffic before response data becomes a campaign judgment.
Use it after creative acceptance and tagging QA, but before trafficking begins. The worksheet is built for publishers, buyers, agencies, analysts, and revenue teams that need a shared pass, revise, or hold decision on the destination page.
What the worksheet decides
The destination page should be judged as its own part of the campaign, not treated as background plumbing. A page can pass creative review and still create unreadable results if it loads slowly, changes the offer, strips source IDs, or hides downstream quality.
| Decision | Use when | Reporting consequence |
|---|---|---|
| Accept | The page matches the ad promise, loads reliably, preserves source fields, and captures the needed action or quality signal. | The campaign can launch with normal destination reporting. |
| Accept with limitation | The page is usable, but a field such as downstream lead status, form error logging, or comparison design is unavailable. | State the limitation before launch and keep the readout narrower. |
| Revise | The page fit is plausible, but speed, copy, form behavior, mobile layout, redirect handling, or routing needs correction. | Hold final trafficking until the corrected destination is checked. |
| Hold | The destination is broken, mismatched to the creative, difficult to use, unable to preserve IDs, or too incomplete to evaluate fairly. | Do not launch the campaign against that destination. |
Launch QA worksheet
| Check | Pass condition | Hold or revise if |
|---|---|---|
| Message match | The page headline, offer, brand, resource, form action, and confirmation path match the approved creative. | The ad promises one task while the page asks for a different action or sends the reader to a generic page. |
| Page speed | The desktop and mobile page load without long blank states, broken assets, blocked scripts, or delayed form access. | Slow or unstable loading could make placement quality look weaker than it is. |
| Mobile usability | Primary copy, call to action, form fields, disclosure text, and confirmation state are readable without horizontal scrolling. | The mobile page hides the action, overlays the form, clips text, or makes completion error-prone. |
| Form friction | Required fields are justified by the offer, validation messages are clear, autofill works where relevant, and errors can be corrected. | The form asks for avoidable fields, fails silently, rejects normal inputs, or loses progress after an error. |
| Tracking fields | Campaign ID, placement ID, creative ID, destination ID, UTM values, device class, and page version survive redirects and form submission. | Traffic or leads cannot be tied back to the correct source trail. |
| Consent or preference state | Analytics, form capture, and routing behavior are known for the major consent or preference states the page supports. | A reader choice changes measurement or submission behavior in a way the report cannot explain. |
| Confirmation event | The thank-you page, event, or submitted-record state is stable enough to identify completions without double counting refreshes. | The conversion fires on page view, form start, duplicate submission, or a page state that cannot be audited. |
| Lead routing | Submitted records have owner, timestamp, source fields, qualification rule, duplicate rule, and follow-up status where relevant. | Lead quality will be judged without knowing whether records were routed, contacted, accepted, or rejected. |
Fast field packet
Before launch, record the fields that make the destination auditable. The packet should be short enough for the traffic manager, buyer, and analyst to use the same names.
Destination fields
Final URL, redirect URL if any, page version, page owner, offer ID, form ID, confirmation event, and fallback mobile URL if different.
Source fields
Campaign ID, package ID, placement ID, creative ID, destination ID, UTM values, device class, flight dates, and approved click URL.
Quality fields
Engaged visit, form start, form completion, duplicate flag, invalid flag, qualification status, routed owner, first response time, and accepted status.
Failure modes to name early
| Pattern | What it can distort | Before-launch fix |
|---|---|---|
| Redirect drops source IDs. | Creative, placement, or package performance can be pooled under direct or unknown traffic. | Test final URLs through every redirect and confirm fields appear in analytics or form capture. |
| Page variant changes mid-flight. | A campaign readout may mix destination effects with media, creative, or audience effects. | Version the page and note the active dates for every destination change. |
| Form accepts easy volume. | Raw completions can rise while useful demand falls. | Define qualification, duplicate, invalid, and disqualification rules before launch. |
| Confirmation fires too early. | Form starts, page views, or duplicate submits may be counted as completed actions. | Confirm the event fires only after a completed, accepted submission or clearly label the weaker signal. |
| Follow-up coverage is uneven. | Lead quality may be blamed on media when routing or sales coverage caused the drop-off. | Record routing owner, first response time, contact status, accepted status, and rejection reason. |
Launch handoff note
Use this note in the final handoff so destination readiness travels with the creative and tagging record.
Destination decisionState accept, accept with limitation, revise, or hold. Name the page version, final URL, launch owner, and any reporting limits that should appear in the readout.
Measurement boundaryState whether the destination can support delivery reporting, traffic-quality reporting, lead-quality reporting, a matched outcome readout, or an incrementality claim.
First readout questionWrite the first question the campaign report should answer, such as whether qualified visits arrived, whether the page converted them, whether leads passed filters, or whether follow-up was complete.
Pair with
Use this worksheet after the creative asset acceptance checklist confirms display or native assets and before the campaign tagging QA checklist verifies URL parameters and IDs. Pair it with the contextual campaign brief template for launch ownership, the campaign data-layer spec for source fields, the landing page and lead quality checklist for readout interpretation, the creative and destination troubleshooting matrix when response patterns point to page friction or message mismatch, the campaign reporting sample for finished tables, and the campaign readout QA checklist before the result becomes a budget decision.