In-Page Push Campaign Management for iOS and Safari Reach

In-page push is where the iOS audience actually is. On our travel and wellness accounts iOS runs between 55 and 70 percent of in-page volume against under five percent on classic push, and that one fact should decide whether you buy the format at all. If your offer converts on Android and dies on iOS, this is the wrong format, and you will hear that on the first call rather than after the first flight. Why it is bought differently: Classic push has a subscriber base, so subscriber age is a lever. In-page push has none. It is a widget rendered inside a session on a publisher's page, so the levers are placement position, session depth and viewability. We buy on visible impressions or we do not buy. A widget impression that never entered the viewport is trivially manufactured and it is the largest single source of waste in this format. PropellerAds, RichAds, Adsterra, Evadav and Clickadilla all carry the inventory, and none of them police it to the standard your budget assumes. Fraud checks run before anything scales: Time-to-click distribution first. A click arriving under 400 milliseconds after render was not made by a person, and a source whose distribution clusters there is cut regardless of what it appears to convert. Then device and browser consistency between the network's reported user agent and the tracker's, session depth on the publisher's own page, and repeat-IP concentration. These four account for most of what gets blacklisted in the first ten days, and they run before a budget increase rather than after a bad month. Placement and creative: Widget position on the page is the second-largest variable after viewability, and networks report it inconsistently, so we infer it from performance and then test it deliberately. Copy is short and written to look like what it is. We do not build the format's standard slop: no imitation of an iOS or Android system notification, no fake messaging interface, no counterfeit comment or like icon, no sound trigger, no widget stacked on an interstitial. Those formats convert, and they burn the publisher, the network and your brand in that order. What is not included: No landing page development. We will critique yours against the traffic and be specific about what is costing you, but we do not build it. No classic push inside this engagement; that is separate work with a different method, and we do not blend the two into one report because the blended number hides which format is paying. No app install campaigns unless a mobile measurement partner is already in place and passing subid. Who this is not for: Advertisers who want classic push volume at classic push prices. In-page inventory is smaller and the effective cost per visible impression is higher; what you buy with the difference is iOS reach and an audience that did not opt into a subscriber list eight months ago and forget about it. Also not for anyone whose conversion sits more than two steps from the click, because the format's attention window does not survive a form and a confirmation email. What you get: A network-by-network read on which sources hold up under the four checks, campaigns built in accounts you own, creative in English and Arabic, a source blacklist as CSV, and a written recommendation at the end on whether to keep spending in the format at all. That document occasionally says no. It has said no three times in the last two years, with the reasoning attached each time so you can check it.