The in-page push playbook for iOS-heavy markets

Why in-page push exists

Classic push depends on a subscriber opting in and on the operating system delivering the notification. On iOS, that chain is fragile. In-page push removes both dependencies: the ad renders inside the page, so reach is available wherever the page loads.

Treat it like a notification, not a banner

Users recognise the notification pattern. That gives you about one second of attention. Keep the icon clean, the headline under eight words and the CTA explicit. Avoid vague promises such as “learn more” when a number or a verb would do more work.

• One benefit per creative.
• A number in the headline where possible.
• A CTA that describes the next screen.

Where it wins

In-page push performs best for sweepstakes, crypto, utilities and mobile offers in markets where push subscriber lists are shallow. It also works as a second touch after popunder: the user has seen the offer once, and the card brings it back without another full-page interruption.

Measure like push, not like display

Set the same optimisation event you would use for classic push, and compare cost per event across formats. Because there is no opt-in, volume arrives quickly; give each source enough clicks before judging it, and keep frequency caps tight enough to avoid fatigue.

A practical starting structure

One campaign per market, two creative angles, three sources. Run for five days, cut the weakest source, then add a second market. The format scales quickly when the landing page matches the promise — and badly when it does not.