Capability template for advertising and lead generation
Ad to page check
When a campaign's landing page is ready for a prelaunch check, the acquisition owner gets a findings list that sets each ad beside the captured page: message, offer details, form and next step, on mobile and desktop. Page states nobody captured are marked unknown.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
A visitor clicks an ad, lands on a page and either finds what the ad promised or does not. This capability template puts the ad and the page side by side before the campaign goes live, so the acquisition owner sees the gaps while they are still cheap to close.
For every ad, the check compares four things on the page as captured: whether the page is about what the ad is about, whether each offer detail matches your approved offer terms, how much the form asks of the visitor, and whether the next step the ad names is the next step the page offers. It does this separately for the desktop and mobile captures.
Each difference is a numbered finding that quotes the ad and the page. Anything nobody captured, such as the form's error state or the confirmation page, is marked unknown and never assumed fine. The acquisition owner decides which findings must be fixed before launch. The check changes no page, predicts no conversion and does not judge whether a claim is allowed.
Who starts the work, and when
The acquisition owner, or whoever signs off a campaign for your company or a client, starts it when the ads are written and the destination page is built and captured, before the campaign is switched on. Run it again after the page changes or a term moves.
The page owner answers for the page and supplies the capture. Whoever owns the offer confirms the approved terms.
What they supply
- Check settings: the campaign, the conversion goal, who it is prepared for, who owns the page, the launch date, the page states that must be captured and, if you want one, a limit on form fields.
- The ad copy, one row per ad: headline, body, call to action, destination and the offer details the ad states.
- The approved offer terms: each offer item, its approved value, any conditions and the date the term ends.
- The page capture, one row per element on the page, for each state: desktop, mobile and, where you have them, the form's error state and the confirmation after submitting.
Nothing is opened or connected. The capability never asks for a password, a login code or a key.
What comes out
One findings list in a fixed order. It opens with which page states were captured, then shows a block for each ad with its message, offer, form and next-step results for desktop and mobile, then numbers every finding. Each finding says where it is, what the ad says, what the page shows, what would settle it and who can supply that. A closing count shows how many findings fall under each heading, and a line lists what the check did not look at.
Every finding carries an open decision line for the acquisition owner: fix before launch, or accept.
An invented example
Illustrative example with invented data. The business, the roles, the platforms, the dates and every figure below are invented. Client Q is an invented subscription tea company preparing a spring starter box campaign. The acquisition manager ran the capability after the web developer captured the two landing pages. First come the inputs, in full, then the findings list the capability returned.
The inputs
1. Check settings
Business: Client Q (an invented subscription tea company)
Campaign: Starter box spring launch
Prepared for: Acquisition manager
Page owner: Web developer
As-of date: 2027-02-15
Launch date: 2027-03-01
Conversion goal: Completed starter box order
Required page states: desktop; mobile; form-error; confirmation
Form field limit: 6
Form expected: yes
2. Ad copy (ad_copy.csv)
ad_id,channel,headline,body,call_to_action,destination_ref,offer_claims
A1,Platform A search,Starter tea box for $19,Six teas to try. Free delivery on your first box.,Order now,D1,price: $19; delivery: free on first box; contents: six teas
A2,Platform B social,Try six teas for $19,Cancel any time.,Shop the box,D2,price: $19; cancellation: any time
3. Approved offer terms (offer_terms.csv)
offer_item,approved_value,conditions,end_date,owner
price,$19,first box only,2027-03-31,Acquisition manager
delivery,free,first box only,2027-02-28,Acquisition manager
contents,six teas,,,Acquisition manager
cancellation,any time,,,Acquisition manager
4. Page capture (page_capture.csv)
page_ref,state,order,element_type,content,required,note
D1,desktop,1,headline,Starter tea box for $19,,
D1,desktop,2,subheadline,"Six teas to try, delivered to your door",,
D1,desktop,3,offer,price: $19 for your first box,,
D1,desktop,4,offer,delivery: free,,
D1,desktop,5,cta,Order now,,
D1,desktop,6,form_field,Email,yes,
D1,desktop,7,form_field,Full name,yes,
D1,desktop,8,form_field,Delivery address,yes,
D1,desktop,9,form_field,Phone number,no,
D1,desktop,10,form_field,Tea preference,no,
D1,desktop,11,form_field,Date of birth,no,
D1,desktop,12,form_field,Gift message,no,
D1,mobile,1,headline,Starter tea box for $19,,
D1,mobile,2,cta,Order now,,
D1,mobile,3,offer,price: $19 for your first box,,
D1,mobile,4,form_field,Email,yes,
D1,mobile,5,form_field,Full name,yes,
D1,mobile,6,form_field,Delivery address,yes,
D1,mobile,7,form_field,Phone number,no,
D1,mobile,8,form_field,Tea preference,no,
D1,mobile,9,form_field,Gift message,no,
D1,confirmation,1,confirmation,Thanks. Your box ships within 3 working days and you will get a tracking email.,,
D2,desktop,1,headline,Try six teas for $24,,
D2,desktop,2,offer,price: $24 first box,,
D2,desktop,3,cta,Start my box,,
D2,desktop,4,form_field,Email,yes,
D2,desktop,5,form_field,Delivery address,yes,
D2,mobile,1,headline,Try six teas for $24,,
D2,mobile,2,cta,Start my box,,
D2,mobile,3,form_field,Email,yes,
D2,mobile,4,form_field,Delivery address,yes,
The findings list
AD-TO-PAGE CHECK: Starter box spring launch, Client Q (an invented subscription tea company)
For: Acquisition manager. As of 2027-02-15. Launch date: 2027-03-01. Conversion goal: Completed starter box order. Page owner: Web developer.
PAGE STATES
D1: desktop captured; mobile captured; form-error unknown; confirmation captured. Findings: 1
D2: desktop captured; mobile captured; form-error unknown; confirmation unknown. Findings: 2, 3
ADS
A1: Platform A search, destination D1
Ad: "Starter tea box for $19" / "Six teas to try. Free delivery on your first box." / call to action "Order now"
Message: desktop same ("Starter tea box for $19"); mobile same ("Starter tea box for $19"). Other promises beyond the offer claims: none.
Offer:
price (approved $19, first box only): ad $19. Desktop agrees ("price: $19 for your first box"), condition shown. Mobile agrees ("price: $19 for your first box"), condition shown. Term ends 2027-03-31, after launch.
delivery (approved free, first box only): ad "free on first box". Desktop agrees ("delivery: free"), condition not shown. Mobile page silent, condition not shown. Term ends 2027-02-28, 1 day before launch.
contents (approved six teas, no conditions): ad "six teas". Desktop agrees ("Six teas to try, delivered to your door"), condition not required. Mobile page silent, condition not required. No end date.
Form: desktop 7 fields (3 required, 4 optional, 0 blank labels); mobile 6 fields (3 required, 3 optional, 0 blank labels). Limit 6: desktop over. Labels in one view only: Date of birth (desktop). Error state unknown.
Next step: ad "Order now". Desktop first call to action "Order now", same. Mobile first call to action "Order now", same. Confirmation: "Thanks. Your box ships within 3 working days and you will get a tracking email." Names a next step: yes (a time and a tracking email).
Findings: 4, 5, 6, 7, 8
A2: Platform B social, destination D2
Ad: "Try six teas for $19" / "Cancel any time." / call to action "Shop the box"
Message: desktop same ("Try six teas for $24"); mobile same ("Try six teas for $24"). Other promises beyond the offer claims: none.
Offer:
price (approved $19, first box only): ad $19. Desktop differs ("price: $24 first box"), condition shown. Mobile differs ("Try six teas for $24"), condition not shown. Term ends 2027-03-31, after launch.
cancellation (approved any time, no conditions): ad "any time". Desktop page silent, condition not required. Mobile page silent, condition not required. No end date.
Form: desktop 2 fields (2 required, 0 optional, 0 blank labels); mobile 2 fields (2 required, 0 optional, 0 blank labels). Limit 6: within. Same fields in both views. Error state unknown.
Next step: ad "Shop the box". Desktop first call to action "Start my box", differs. Mobile first call to action "Start my box", differs. Confirmation not captured, unknown.
Findings: 9, 10, 11
FINDINGS
1. Unknown. D1 (A1), form-error state. Ad: not applicable. Page: no rows captured for D1 in state form-error. To settle: a capture of the D1 form after a failed submission. Who can supply: Web developer. Decision: open.
2. Unknown. D2 (A2), form-error state. Ad: not applicable. Page: no rows captured for D2 in state form-error. To settle: a capture of the D2 form after a failed submission. Who can supply: Web developer. Decision: open.
3. Unknown. D2 (A2), confirmation state. Ad: not applicable. Page: no rows captured for D2 in state confirmation. To settle: a capture of the D2 page after a completed order. Who can supply: Web developer. Decision: open.
4. Missing on page. A1, offer, delivery. Ad: "Free delivery on your first box". Approved: free, first box only. Page: desktop "delivery: free" with no condition; mobile has no delivery statement. To settle: the page states the first-box condition on desktop and delivery on mobile, or the ad changes. Who can supply: Web developer. Decision: open.
5. Timing conflict. A1, offer, delivery. Ad: "Free delivery on your first box". Approved: free, first box only, ending 2027-02-28, 1 day before the launch date 2027-03-01. Page: desktop "delivery: free". To settle: the term's end date is confirmed or extended, or the ad and page change. Who can supply: Acquisition manager (term owner). Decision: open.
6. Missing on page. A1, offer, contents. Ad: "six teas". Approved: six teas, no conditions. Page: desktop "Six teas to try, delivered to your door"; mobile has no statement of the contents. To settle: the mobile page states the contents, or the ad changes. Who can supply: Web developer. Decision: open.
7. Form friction. A1, form, desktop. Ad: not applicable. Page: 7 fields (Email, Full name, Delivery address, Phone number, Tea preference, Date of birth, Gift message), 3 required, against the limit of 6. To settle: a decision whether a field comes off the desktop form or the limit stands. Who can supply: Web developer. Decision: open.
8. Differs. A1, form, desktop against mobile. Ad: not applicable. Page: desktop has 7 fields and mobile has 6; Date of birth appears on desktop only. To settle: the two forms are confirmed as intended or made to match. Who can supply: Web developer. Decision: open.
9. Differs. A2, offer, price. Ad: "Try six teas for $19" (price: $19). Approved: $19, first box only. Page: desktop "price: $24 first box"; mobile "Try six teas for $24" with no condition shown. To settle: the page price and the mobile condition are corrected, or the approved term changes. Who can supply: Web developer (page), Acquisition manager (term). Decision: open.
10. Missing on page. A2, offer, cancellation. Ad: "Cancel any time." Approved: any time, no conditions. Page: neither desktop nor mobile states it. To settle: the page states the cancellation term, or the ad changes. Who can supply: Web developer. Decision: open.
11. Differs. A2, next step. Ad: call to action "Shop the box". Page: desktop and mobile first call to action "Start my box". To settle: the acquisition manager accepts the difference or the wording is aligned. Who can supply: Web developer. Decision: open.
Findings in all: 11. Unknown 3; Missing on page 3; Differs 3; Timing conflict 1; Form friction 1.
Not checked: page speed, tracking, accessibility, whether any claim is allowed,
and how the page will convert.
Next step: the acquisition manager decides, finding by finding, which must be fixed before launch. No page, ad or account has been changed.
Every statement traces to the check settings, the ad copy, the approved offer
terms and the page capture supplied. Nothing marked unknown was assumed to be fine.
Where it fits
- Advertising and lead generation, where the last check before spend starts is whether the page keeps the ad's promise.
- Marketing and content, where the ad copy and the page are often written by different people.
- Design and user experience, where the mobile and desktop views of the same page have to agree.
- Marketing and advertising, where an agency checks pages it did not build.
- Ecommerce and retail, where prices, delivery terms and end dates change often.
- Software and technology, where trial and sign-up pages carry the offer.
- Growth & scaling, when campaigns multiply faster than anyone can click through each one.
It does not set the campaign up (campaign build sheet), review each form field's purpose (lead form field review) or tie each claim to its evidence (campaign claim evidence register). It compares the ad with the page and stops there. It is also not the audit of a campaign taken over from someone else (inherited campaign audit); this check comes before launch, on ads and a page you are about to switch on.
What has to change for your company
- Your page states. List the states you can capture: desktop and mobile at least, and the form's error state and confirmation if the page has them.
- Your offer items. Name the offer details you advertise, such as price, delivery, trial length and cancellation, with the wording of each approved value.
- Your form limit. Set a number of fields if you have a house rule, or leave it blank.
- Your owners. Decide who owns the page, who confirms the offer terms and who decides at launch.
- Your files. Use the column names your tools export, or rename them once to the defaults. When a header does not match, the assistant stops and asks.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried once on its invented example, in Claude on 10 November 2026, and the record is published with it. It has not been tested in a client environment or as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a campaign whose page you already know, with cases written in advance: a price that differs between ad and page, a delivery term that ends before launch, a mobile view that drops an offer, a form with more fields than your limit, a state nobody captured. The acquisition owner checks every finding against the live page before relying on it. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: