01 · The lever
The landing page is the top of the install funnel.
For a consumer app, the marketing site has one commercial job: turn attention into installs. That makes the primary CTA the highest-leverage element on the page, and I treat it like one. A visitor can arrive on any page, on any device, and the distance between that moment and an install in the right store is the conversion I own.
So I set the bar deliberately: one obvious action on every surface, zero wrong-store friction, and a number I can defend. Anything short of that leaves installs on the table and stays quiet about it, which is the part I refuse to ship.
02 · The work
Device-aware routing, one source of truth, measured by default.
I designed the CTA around intent. On click it resolves the visitor's device and sends them straight to where they convert: iPhone and iPad to the App Store, Android to Google Play, desktop to the store badges. The visitor never has to think about which store they need, and that invisible friction is exactly what quietly costs installs.
I governed it from a single shared header, so the CTA, navigation, and mobile menu stay consistent across all 10 pages and change in one place. Consistency at the top of the funnel is a growth decision, not a cosmetic one.
Then I made it provable. Every Download click is a tagged GA4 event carrying its source and page, so the CTA has its own attributable number instead of vanishing into site traffic. On top of that I stood up a weekly click-through-rate report that delivers itself, turning "is this working" into a standing metric. The lever shipped with its measurement attached, not bolted on later.
03 · Outcome
An install path that routes every device and reports on itself.
04 · Behind the work
How I think about it.
Most CTA work fixates on the button. The leverage is upstream: decide the single action the page should drive, then remove every gram of friction between the visitor and that action. Device-aware routing is the expression of that decision, not the point of it.
I also won't claim a lift I can't show. Designing the event, isolating its click-through rate, and putting it on a weekly cadence means the next call on this lever gets made on evidence. Shipping the change is the easy half; building the loop that proves it is the work.