Native Ad Widget Placement: Test Visibility and Revenue

A useful native widget position depends on the page, device, reader behavior and network implementation. Compare allowed positions using visibility, total revenue per pageview and reader experience; this article does not establish a universal highest-earning location.

Compare positions in the page context#

Recommendation inventory can use different commercial arrangements, and a click alone does not determine total page revenue. Inspect which visitors actually see and interact with each position.

Below-article, in-article and other supported positions reach readers at different points. Check the network’s allowed implementation, how much of each page readers see and whether the unit interferes with content. Do not assume a single ranking applies across templates or devices.

Sizing and layout#

Choose a supported responsive layout and test tile count against page revenue and reader experience. Four, six or eight tiles are examples of layouts, not measured universal optima.

Use the network’s image and implementation specifications and check the actual rendered quality. The previous claim that image quality automatically improves fill or CPC through an auction score is not established.

Mobile-specific placement notes#

Test the actual mobile layout, viewport, loading and scrolling behavior. A desktop sidebar may reposition or disappear responsively; do not assume every mobile page has no alternative placement. No universal dwell-time penalty or below-article advantage is established here.

One widget vs. stacking multiple positions#

Compare one supported widget with any permitted additional placement using total page revenue and experience measures. Added impressions, cannibalization and net benefit must be measured rather than assumed.

Common placement mistakes that quietly cost RPM#

Check pagination, layout shifts, load order, disclosure, visibility and interference with the content. Keep ads identifiable as advertising. Test after a redesign because the page and traffic context may change; there is no fixed 80% scroll cutoff that determines the correct placement.

How placement guidance differs by network#

Use each network’s current publisher implementation instructions and contract. Taboola documents flexible placement and recommends account-specific guidance; do not assume all networks prescribe the same position or spacing.

What changes for AMP and app-embedded pages#

For AMP, in-app views and other constrained environments, verify the current integration supported by the actual network and host. Do not assume a desktop tag or an old AMP-specific implementation remains supported.

Testing placement changes properly#

Define revenue per thousand of the stated denominator, such as pageviews, and compare aligned traffic. Use a concurrent randomized test when feasible and monitor visibility and user experience. Sample size, variability and conversion or revenue delays determine the useful test duration; two to four weeks is not a universal minimum.

Keep the date, page template, layout change, experiment assignment and metric definition in the test log. Compare templates and devices where behavior differs, without treating word count as a rule for placement.

How OpenAdLibrary fits in#

OpenAdLibrary can provide captured creative examples and available advertiser context. These do not establish fill, eligible demand, bids or expected RPM on your own property; request those terms and measure your implementation.

FAQ#