Postscript is paying to sell Shopper, then interrupting the pitch
A current Shopper ad promises an AI sales rep over SMS. The click reaches a broad AI page, where a different guide can cover the offer before the visitor reaches the demo.
Owner brief
We followed a current paid Postscript ad to its exact destination and checked the route toward a demo. Three leaks made the cut. The first can pull paid visitors into a different campaign. The second drops the specific Shopper promise that earned the click. The third adds avoidable friction on phones.
Highest-priority revenue leaks
1. A different campaign takes over the paid landing page
The ad says, "Turn SMS Into Your Best Sales Rep." It describes Shopper finding products, answering objections, and helping subscribers buy over SMS.
On the exact destination, a large popup promotes "Fizzzy Soda's Totally Unsolicited Guide to AI." The page behind it is dimmed. The popup's main action is "Access the Guide," not the demo promised by the landing page.
That interruption asks a paid visitor to choose between two campaigns before the Shopper pitch has had a chance. Some will leave. Others may download a guide instead of starting the higher-value demo path.
Suppress this popup for Shopper campaign traffic. If the guide belongs in the journey, place it after the Shopper promise and demo action rather than over them.
FunnelWatch should keep opening every paid destination in a fresh visit and flag any popup that covers the offer or sends the visitor into another campaign.
2. The page drops the promise that earned the click
The ad makes Shopper tangible: an AI sales rep that finds products and handles objections. The landing page opens with "Drive More Revenue, Faster" and a broad description of Postscript AI. Its first main action is "Book My Demo."
The page is related to the ad, but the sharp reason to click has gone missing. A visitor must keep reading to discover that Shopper is one part of the wider AI suite. That extra work can weaken intent between the ad and the demo.
Give this campaign its own opening screen. Repeat the sales-rep promise, show one short example of Shopper helping someone buy, then lead straight to the demo.
FunnelWatch should compare each live ad with the first phone and desktop screen it opens, then flag changes to the product, promise, or next step.
3. The phone page keeps working after the offer appears
In the measured phone visit, the main offer appeared after 2.8 seconds. The browser then stayed too busy to respond for another 1.1 seconds while handling an 8.4 MB page and 252 requests. The desktop visit did not show the same pause.
Paid phone traffic is impatient. A demo button that looks ready but cannot respond right away can turn a motivated tap into a second tap, a mistaken exit, or no action at all.
Load the opening headline and demo button first. Delay lower-page video, extra page code, and nonessential tags until the first screen can respond.
FunnelWatch should keep timing when the phone offer appears and when its demo action is ready to use.
What we checked
Funnel depth tested: current paid ad → exact Postscript AI landing page → public demo destination page load. We checked the opening desktop and phone views, 20 public links, campaign tags, page loading, and the visible routes to pricing and a demo.
We did not fill or submit the demo form, schedule a meeting, create an account, sign in, or test payment. No block or human-verification page appears in the screenshots used here.
Fix this first
Stop the guide popup from appearing on Shopper campaign visits. Then make the opening screen repeat the sales-rep promise that won the click.
Keep paid clicks on the path to a demo
These leaks can return when ads, popup rules, landing-page copy, videos, tags, or demo routes change. FunnelWatch can keep following the paid path and catch the release that interrupts the pitch, drops the promise, or slows the first action.