PWA vs a Keitaro + Landing Page Funnel
The classic setup — a landing page with Keitaro as the redirector — has stayed a working formula for years, so the question isn't whether to drop it, it's what a PWA adds on top. Here's the difference by job-to-be-done: re-engaging an audience, surviving a ban, and getting clean analytics. Keitaro doesn't go anywhere either way — it still works as the tracker alongside a PWA.
What each piece of the funnel actually does
In the classic setup, Keitaro splits traffic across flows and landers, and the lander itself is a one-time page — a user sees it, clicks or leaves, and without retargeting that contact is gone. A PWA is an installed app that stays on the user's device after the first visit, so you can reach that audience again through it. It's not a replacement for Keitaro as a tracker, it's a replacement for a disposable lander with a channel you can revisit.
Re-engagement: push vs paying for another click
After a landing page, the only way to bring back someone who didn't convert is to pay for another ad click. After a PWA install, push is available instead — a reminder about the offer, a new offer announcement, segmentation by activity — none of it requiring new traffic spend. That's the core economic edge a PWA has over the classic setup.
Surviving bans: lander domain vs PWA
A landing page usually runs on one live domain, and a ban on it means paused traffic until you manually swap domains and warm one up again. PWA services like APEX give you custom domains with one-click rotation — the installed app keeps working for users who already have it, even after the serving domain changes, because it's already sitting on their device. That cuts the downtime between a ban and getting the funnel live again.
Cloaking and anti-bot in each setup
In a Keitaro-based funnel, cloaking is usually configured separately — either through Keitaro's own rules or a third-party service. In a PWA builder with cloaking built in, like APEX, filtering by UA, bot signals, datacenter and geo happens at the same layer that serves the PWA, with no separate scripts to set up on the lander. The difference comes down to how many separate pieces you have to administer.
How they work together, not as a replacement
In practice, a PWA doesn't retire Keitaro — you still need a tracker for flow distribution, offer A/B testing, and postbacks to the network. APEX supports S2S integration with Keitaro, so the setup looks like: ad, then Keitaro, then a PWA with cloaking and push instead of a disposable lander. What changes is what happens after the first click, not the tracker itself.
FAQ
- Does a PWA fully replace a Keitaro-plus-landing-page setup?
- No — Keitaro still tracks and distributes traffic. What changes is the endpoint: instead of a disposable landing page, users land on a PWA you can re-engage through push.
- What's the main economic advantage of a PWA over a landing page?
- The ability to bring a user back through push without paying for another ad click — a landing page has no equivalent re-engagement channel.
- What happens when a domain gets banned in a PWA setup?
- You rotate the serving domain in one click, and the PWA already installed on users' devices keeps working for anyone who already has it — less downtime than replacing a classic landing page domain.
- Do I need to reconfigure Keitaro to move to a PWA?
- Core flow logic and postbacks carry over — APEX supports S2S integration with Keitaro, so what changes is the endpoint (a PWA instead of a landing page), not the whole funnel.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free