What budget should I test a new funnel with?

There's no fixed number — start with an amount you can afford to lose entirely while reading the click → install → deposit signal, and only scale up once the trend is confirmed positive.

What should I check first right after launch?

In this order: whether clicks are converting to installs, whether installs are reaching the target action, and whether conversion postbacks are actually landing in the tracker and CAPI.

Do I need a backup domain ready even if I haven't been banned yet?

Yes — a warmed backup domain attached in advance saves time exactly when it's scarce, instead of scrambling to find and buy one under pressure.

Can I launch without split-testing the witrina?

You can, but testing two or three variants at the start usually finds a working funnel faster than swapping the witrina one guess at a time.

PWA Campaign Launch Checklist

Every item skipped before launch is either budget burned in the first few hours or data lost that can't be recovered after the fact. Here's the checklist across five blocks: domain, cloaking, tracking, push, and the launch itself.

Domain and witrina

Your own domain is connected with automatic HTTPS, and one or two warmed backups are already in place for an instant rotation if needed. The witrina has been tested loading on a throttled mobile connection, not office Wi-Fi, and is localized to the target audience's language and geo, down to details like currency format and phone masks.

Cloaking and antibot

Filters are configured and cover bots and crawlers by user-agent, datacenters and proxies by IP intelligence, and geo mismatches. The white page is actually prepared and genuinely loads, not just sitting there in theory — confirm this with a separate test visit from an off-target IP.

Tracking and postbacks

The campaign and stream are set up in Keitaro, and subid is passed into the PWA link and correctly survives through to conversion — worth checking with a test click before launch, not after the first real money moves. The S2S postback to CAPI is configured, statuses are mapped to the right events, and at least one test conversion is confirmed in Events Manager.

Push and prelanding

The subscription prompt and a first welcome or triggered send are set up and tested on a real device, not just in the dashboard. If a prelander is part of the funnel, a wheel of fortune, say, what it promises needs to match what's actually waiting on the next step, or the warm-up works against conversion instead of for it.

Budget, roles and the first hours

Starting budget and bid are set conservatively — a test amount you won't mind losing entirely before the funnel proves itself on numbers. Team roles are assigned in APEX (who can pause the campaign or rotate the domain without waiting on a team lead), and there's a monitoring plan for the first hours: clicks, then installs, then first postbacks, in that exact order.

FAQ

What budget should I test a new funnel with?: There's no fixed number — start with an amount you can afford to lose entirely while reading the click → install → deposit signal, and only scale up once the trend is confirmed positive.
What should I check first right after launch?: In this order: whether clicks are converting to installs, whether installs are reaching the target action, and whether conversion postbacks are actually landing in the tracker and CAPI.
Do I need a backup domain ready even if I haven't been banned yet?: Yes — a warmed backup domain attached in advance saves time exactly when it's scarce, instead of scrambling to find and buy one under pressure.
Can I launch without split-testing the witrina?: You can, but testing two or three variants at the start usually finds a working funnel faster than swapping the witrina one guess at a time.

Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free