Campaign operations
A checklist before you send traffic
Walk the live page on a phone, from the ad to the stored submission, before you pay for clicks.
The hour before traffic is cheaper than the week after. A landing page can look finished in the editor and still fail in the only sequence that matters: a person taps the real ad, on a phone, reads the offer, submits a form, and a teammate finds a row that matches what the page promised. This checklist walks that sequence. It assumes you have already written a repeatable offer, a form you can defend, consent language you have read aloud, and a privacy notice that matches the fields. If those pieces are still mush, stop and use the earlier guides. A checklist cannot rescue an offer you cannot say out loud.
Do the walk on the live address, not in a preview pane. Previews lie about certificates, about which script is installed, and about what a partner’s tracking link does to the URL. Use a phone that is not logged in as the site administrator if you can, so you see the page a stranger sees. Use a test identity that your follow-up team will recognize as a test, and agree in advance that they will not treat it as a real request. Then throw the test away or flag it according to your own retention rules.
The click
Open the ad, email, or partner link that you are about to fund. Confirm the visible words and the destination address. The headline on the landing page should match that click in the way the headline guide describes. If a wrapper or short link sits in the middle, follow it. You are checking the path a stranger gets, including every redirect. If the browser warns about the connection, stop. A warning before the form is not a branding issue. It is a broken front door. The page should load with a certificate that matches the name in the address bar, on the domain you intended, not on a look-alike host someone configured once and forgot.
Read the first screen without scrolling. You should be able to state the offer, the reader, and the next step. Close the page and open it again on a slow connection if you have one. Note whether a late banner shoves the form. Note whether a chat box or a cookie layer covers the button. Fix coverage problems before you buy visits. They will not become less annoying under load. They will become more frequent.
The form
Complete every field as a careful stranger, then try to submit something a careless stranger would submit: a too-short phone number, a ZIP code you do not serve, a double tap on the button. The page should fail gently where it must fail, and it should not create two confusing rows where a single request belongs, or if it does, your team should know which row is the duplicate. Confirm the consent control starts unchecked if agreement is meant to be a choice, and that the privacy link opens the notice for this campaign. Read the button label. It should be the same next step the headline named.
Submit a valid test. The thank-you screen should restate the window and the channel. “We will call on weekdays within one business day” is a restatement. “Success” is not. If the thank-you screen contradicts the headline, you have two offers and you will be held to the more generous one by anyone who is annoyed. Make them identical in substance.
The row your team sees
Open the submission in the place the follow-up team will work. Check the name, the number, the campaign or page identity, and the time. Confirm you can tell which page produced it. If you keep a copy of the consent text or a visual record, open that too and compare it with the phone you just used. A mismatch means the record is capturing the wrong template. Repair it before traffic, while the only person in the system is your test. This is also the moment to confirm that a person who should not see the campaign cannot see the test row. Access is part of the launch, not a cleanup for later.
Tell the follow-up team the offer, the window, and the hours in a few sentences, and point them at the live page. They should not learn the promise from the first angry caller. Agree on the quality mark you will use in the weekly review, even if the mark is as simple as “in area, and we reached a person.” A campaign that launches without a definition of a good submission will invent one later to justify the spend. Invent it now, while you are still calm.
The paperwork around the page
Save the mobile view, the consent paragraph, and the privacy-link destination with the date and the URL. File the headline next to the ad that points at it. Confirm the address is dedicated to this offer and is not a recycled name. Confirm who is allowed to edit the page during the flight, and who is not. Unattended editing access is how a helpful colleague “freshens” a headline on day two and destroys the comparison you thought you were running. If you intend a real headline test, fill in the test card before the first paid click, not after the first ambiguous week.
Check the money path only at the level of “where do we turn this off.” You should know which person can pause the ads the same day if the test submission fails in production, if the team is overwhelmed, or if the page starts saying something you did not approve. A campaign with no pause switch is not ready. Scale is a later decision. The ability to stop is a launch decision.
Launch card
- The live ad destination was opened on a phone and the connection was clean.
- The first screen states an offer the follow-up team can keep.
- Consent, labels, and the privacy link were read on that phone.
- A valid test produced one understandable row in the working system.
- The stored page record matches the phone, and the test is flagged or removed.
- The team knows the window, the channel, and the quality mark.
- A named person can pause the traffic the same day.
- The address, headline, and consent version are filed with today’s date.
If a line on the card fails, do not launch “just to see.” Seeing is what the test submission was for. Repair the line and walk the card again. The guides on this site are here so that walk is specific: offer, fields, phone layout, headline, consent, notice, record, counts, and address. Traffic is the last step, not the way you discover what the page says.