In-Article Native Ads: Earnings and Reader Impact
In-article native units appear between paragraphs and take on the fonts and colours of your page. Some are ordinary ads dressed in your styling, others are recommendation blocks listing sponsored stories. Either way, they sit exactly where the reader is already looking.
Updated · Every figure on this page is an estimate from our benchmark tables, not a quote from any network.
Every web network in our tables offers some kind of native or in-content placement, and in our model it accounts for 22% of the reference RPM. It is the format that trades reading comfort for revenue most directly, so spacing matters more than anything else.
What this format contributes on a website
Estimated monthly revenue for a general site with 50,000 sessions, with and without this format, by network.
| Network | With | Without |
|---|---|---|
| Google AdSense | $266 | $207 |
| Ezoic | $359 | $280 |
| Media.net | $212 | $165 |
| Monumetric | $396 | $309 |
| Mediavine | $640 | $499 |
| Raptive | $677 | $528 |
Adding this format lifts the estimate by about 28% on networks that support it.
How it earns
Native earns from its position. A unit inside the text is much more likely to be seen than one in a sidebar, so viewability is usually higher and buyers pay for that. On an AdSense Tier 1 reference RPM of about $7.00, native contributes roughly $1.54 per 1,000 pageviews. On Mediavine's reference of about $17.00 it contributes about $3.74.
Longer articles offer more natural break points, which is why in-content revenue grows with depth. A long guide can carry several well-spaced units without feeling crowded, while a short news item may only suit one.
What it does to the experience
The price is paid in rhythm. A reader who meets an ad every couple of paragraphs starts to skim, and skimming readers leave sooner and see fewer ads overall. Units placed straight after the opening paragraph, or between a heading and its text, are the most jarring of all.
Clear labelling is a well-established rule across ad networks and advertising regulators: a native unit must be recognisable as an ad, usually through a visible 'Advertisement' or 'Sponsored' tag. Disguising ads as editorial risks policy action and your readers' trust. Check your network's current native policy and any advertising rules that apply where you publish.
Best practice
- Hold back the first in-article unit until the reader is past your introduction.
- Space units by paragraphs or screen heights rather than a fixed count per page.
- Keep ads clear of images, tables and headings so key content stays in one piece.
- Style the label so it is easy to read, and never remove the network's attribution.
Common mistakes
- Inserting the same number of units into short and long articles alike.
- Matching the ad so closely to your own links and headings that readers tap it by mistake.
- Piling a recommendation widget and several display units at the end of a post until the footer is all ads.
All figures come from our benchmark tables: Android eCPMs by tier, category or niche multipliers, modelled fill and the iOS multiplier. They are estimates for planning, not quotes.
Questions people ask
Is in-article the same as native?
Not quite. In-article describes any ad placed inside the text flow, while native means the ad adopts your styling. Many networks combine the two, which is why our model treats them as one format.
Do in-article ads hurt search rankings?
Not directly, but they can change how long readers stay and how quickly the page loads. Reserve space for each unit and read our comparison of website ad formats to weigh them against the alternatives.
How can I tell if I have too many?
Compare scroll depth and time on page for the same articles before and after a change. If readers stop earlier, the extra units are probably costing more than they bring in.