The problem this solves
Competitor ad monitoring usually stops at the creative. The ad libraries make it easy to see what rivals are running, so teardowns fill up with screenshots of their ads and speculation about their strategy, while the half of the funnel that actually converts, the landing page behind each ad, goes unexamined. The click experience is where competitors reveal their real offer architecture: what they promise to cold traffic, what they show first, what they gate, and what they charge for it.
Examining it properly is tedious in a specific way that ensures it rarely happens. Someone has to visit each competitor page fresh, scroll it end to end, check it on a phone, and document everything before the page changes, multiplied by every active ad worth studying. Done by hand it produces a folder of inconsistent screenshots assembled over a week, by which time half the ads have rotated.
This mission runs the whole funnel study in one pass. It pulls each competitor's active ads from the libraries, follows every distinct destination in a real browser, records the scroll-through a visitor would make, captures the phone rendering, and assembles the teardown as a deck: the ad's promise, the page's delivery, and the gap between them, competitor by competitor.
How the mission runs
- Pull the active ads. The ad libraries supply each competitor's currently running creative across platforms, with the destination each ad points to. Duplicate destinations are collapsed, so the study covers every distinct click experience rather than every ad variant.
- Record each landing page. The rendered browser visits every destination fresh and records a smooth scroll-through, preserving the page as a visitor experiences it: load behavior, content order, offer placement. The recording outlives the campaign, which matters because competitor landing pages change without notice.
- Capture the phone rendering. Each page is captured again in mobile emulation, where most paid social clicks land. Competitors' mobile experiences are frequently worse than their desktop ones, and knowing exactly where theirs break is directly actionable for your own bids and pages.
- Score promise against page. Each ad's claim is read against what its landing page delivers: the offer restated or abandoned, the first screen's message, the form length, the price shown or hidden. The gap between promise and page is scored, because that gap is where a competitor's funnel leaks.
- Assemble the teardown deck. The findings become a deck organized by competitor: their ads, their recorded pages, the phone captures, and the promise-to-page verdicts, closing with the patterns across rivals and the openings they leave you. Evidence and interpretation travel together.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A teardown deck covering every competitor's active click experience: the ads, a scroll recording and phone capture of each distinct landing page, promise-to-page scores, and a closing read on the patterns and the openings. The recordings double as a dated archive of rival funnels as they stood this quarter.
Make it yours
- Rerun monthly and lead the deck with what changed: new offers, killed pages, and repositioned funnels are the intelligence, and the recordings make the comparison exact.
- Narrow it to one competitor before a launch that targets them, turning the teardown into the brief for your counter-positioning.
- Feed the strongest rival patterns to the landing-page review playbook, so your own pages are scored against the best click experience in the market rather than only against their ads.
Frequently asked questions
Why record the pages instead of screenshotting them?
Because the click experience is sequential. What a visitor sees first, how far the offer sits below the fold, and where the form appears are facts about order and distance that a static capture flattens. The recording preserves the experience being sold; the screenshots complement it.
Is following competitor ad destinations acceptable?
The mission reads the ad libraries, which platforms publish for transparency, and visits public landing pages the way any curious buyer would. It never clicks the paid ads themselves, so no competitor budget is spent, and it never logs in or probes anything nonpublic.
What decisions does the teardown actually inform?
Offer architecture and page strategy first: what rivals promise cold traffic, what they gate, and where their funnels leak on mobile. Teams typically leave the read with two or three concrete page tests and a clearer sense of which competitor claims to attack directly.