In-App Bench
In-App Bench
@InAppBench

<b>In-app vs web inventory: viewability is not measured the same way</b>

<b>In-app vs web inventory: viewability is not measured the same way</b>

Buyers port web viewability assumptions into in-app and get burned. The MRC 'pixels-in-view for one second' rule exists in both, but the measurement plumbing is completely different.

Web
✓ JavaScript tags measure the actual viewport in real time
✗ Easily spoofed by stacked iframes

In-app
✓ Open Measurement SDK (OMSDK) reads native view geometry — harder to fake
✗ Requires the SDK to be integrated by the publisher; many small apps skip it
✗ Without OMSDK, you're trusting the exchange's self-reported number — basically unverified

So in-app viewability is potentially more honest but less universally instrumented. Demand OMSDK coverage figures before buying, not blended viewability percentages.

Verdict: trust in-app viewability only where OMSDK is live — otherwise it's a vanity number.
Best for: brand buyers extending display budgets into apps.
Этот пост опубликован в Telegram-канале In-App Bench. Подписаться можно по ссылке: @InAppBench.
traffic

Свежие посты в категории «Traffic Sources»

Все каналы категории →

start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @dumay. Быстрый тест: $20 за канал, $1000 за пакет по сети.