Outbrain for Publishers: Requirements, RPM & Payment Terms
Outbrain (now Teads) monetizes publisher sites with recommendation feeds. How onboarding works when no traffic minimum is published, what drives RPM, the documented $50 monthly payment threshold, and contract points to check.

Outbrain, which completed its acquisition of Teads in February 2025 and now operates under the Teads name, monetizes publisher sites with recommendation widgets placed below and within articles. Publishers earn revenue from the paid recommendations shown on their pages, under the terms of their agreement. Teads says publishers must meet its terms to be approved and that its vetting uses third-party credibility ratings, but the public pages reviewed here list no traffic minimum; onboarding starts with a contact request, and implementation uses widget IDs supplied by an account manager. Revenue is usually reported as RPM (revenue per thousand pageviews) and moves with your geo mix, audience, placement and paid density. Outbrain's publisher help center says payments are sent once an account earns at least $50 in a month and follow the payment terms in your contract. This guide covers what the feed offers, the onboarding bar, what drives RPM, the contract terms worth negotiating, and a due-diligence step that is easy to skip: reviewing the ads that will run on your pages.
What Outbrain offers publishers#
Outbrain's core publisher product is the recommendation feed — the grid of sponsored and editorial content cards that appears when a reader reaches the end of an article, historically branded Smartfeed. Each card is a content recommendation widget item: an image, a headline, and a source label. Some cards are paid recommendations from advertisers; some can be recirculation links back into your own content. Outbrain's self-serve advertisers buy on a cost-per-click model, and the publisher is paid under the terms of its agreement.
Since the merger, the combined company operates under the Teads name, and Teads now presents its media-owner offering as a single access point to its demand across premium publishers, CTV and apps, with formats that include in-article video alongside recommendation units. Confirm which placements and formats a given agreement covers. If you are catching up on the corporate history, the Outbrain–Teads merger explained covers what changed and what kept its name, and our overview of the Teads platform covers the combined product from the advertiser side.
In practical terms, a publisher integration usually includes some combination of:
The below-article feed: the recommendation unit placed after the article body. In-article units: recommendation or high-impact modules placed within the article. Video: Teads' in-article video formats, where your agreement includes them. Recirculation: organic cards pointing at your own articles, which Teads says can increase pageviews and session length; measure the effect on your own site.
The strategic appeal is simple: the space after an article ends can otherwise go unused, and a feed that mixes paid and organic recommendations monetizes it while keeping some readers on your site.
Requirements: what it takes to get accepted#
We found no published traffic minimum on Teads' media-owner page or in Outbrain's publisher help center. Teads says publishers must meet its terms and conditions to be approved, its account managers monitor approved properties, and its vetting uses independent third-party ratings to identify low-credibility sites. The specific criteria are not public, so treat the following as preparation rather than official requirements:
Real editorial content. Original articles, named authors or a credible masthead, and working about and contact pages make a site easier to assess; scraped, spun or thin aggregator content is unlikely to pass a credibility review. Consistent traffic. Be ready to show steady traffic and its history; if your site is small, compare other recommendation partners' onboarding terms as well. Clean traffic sources. Be ready to explain where visitors come from, including any paid acquisition (traffic arbitrage), because advertisers pay for the engagement your audience provides. Content categories. Teads applies brand-safety filters to categories such as adult content, online piracy and hate speech for campaigns it manages, and screens publishers for low-credibility content; ask which categories are acceptable before applying. Article templates. Outbrain recommends placing footer widgets as close as possible to the end of the content with no other elements above, and says low viewability reduces CTR and RPM.
Before you approach, assemble the numbers a partner manager will ask for: monthly pageviews, share of traffic on article pages, top geos, audience topics, and current monetization setup. A clean traffic profile and a clear geo story make that first conversation more productive.
How publisher revenue actually works#
Your earnings are a function of three variables: how often readers click the feed (feed CTR), what advertisers pay for those clicks (CPC), and your revenue share.
Feed CTR depends heavily on placement. Outbrain recommends placing footer widgets as close as possible to the end of the content with no other elements above, and says low viewability reduces CTR and RPM. Check your own analytics for how much feed traffic comes from mobile, and test the mobile layout. Advertiser CPCs move with your audience. Advertisers set CPC bids for the audiences and countries they target, so geography and topic can change the demand your pages attract; this article has no data showing how large those differences are. Deal shape. Revenue share, guaranteed RPMs, flat guarantees and hybrids are possible structures, but terms are negotiated privately; ask what any guarantee is conditioned on, such as traffic floors or exclusivity.
This article has no reliable RPM benchmark: published figures rarely state their sample, geography or date, and any single number describes someone else's audience. Model your own case instead: RPM is roughly paid clicks per 1,000 pageviews times average advertiser CPC times your revenue share. With invented inputs of 5 paid clicks per 1,000 pageviews, a $0.40 average CPC and a 50% share, RPM would be $1.00. Then validate the model with a trial period before committing to exclusivity.
One framing mistake to avoid: comparing feed RPM to your premium display CPM as if they compete. The feed monetizes the space after the article, which may not compete directly with your display units. Evaluate it as incremental revenue per session, alongside whatever recirculation lift the organic cards produce.
What actually runs in the feed: the demand behind your RPM#
Your RPM depends on advertiser demand, and part of that demand is visible. OpenAdLibrary captures Outbrain placements from public pages without clicking live ads. Captured examples show what kinds of cards can appear in the feed; they do not measure advertiser spend, bids or the revenue a given site will earn.
In OpenAdLibrary's June 2026 Outbrain captures, the classified examples included insurance, finance, health, ecommerce, software and home-and-garden advertisers. Counts are not given here because no reproducible extract is available and other June 2026 figures on this blog differ; category labels describe collection coverage, not market share or demand.
Regulated categories such as insurance, finance and health appear in the captured examples. This article has no bid or revenue data showing that audiences reading about those topics earn more, so test rather than assume. If you publish money, insurance or wellness content, check how those ads look next to your editorial and whether they meet your standards.
The mix is broader than performance offers. In captures before this guide was published in August 2026, Outbrain placements included a corporate sustainability content series from an industrial brand observed over more than a month, a skincare advertorial observed over 30 days, and curiosity content, including a pet-behavior story and a home-and-garden story each observed over a 38-day span. An observed span is the time between captures, not continuous runtime or evidence of results. Brand content, direct response and curiosity-driven advertorials can all appear in the same kind of widget.
Why this matters to you: those cards render on your pages, under your masthead. The ads are public when served, so you can review captured examples, from brand explainers to aggressive advertorials, before you commit. Review the Outbrain ad library for the geos and verticals your audience matches; filtering by geo and vertical requires OpenAdLibrary's Founders plan ($29.99/month), while the free plan shows the 20 newest ads.
The RPM levers you actually control#
Once live, it is easy to leave revenue on the table by treating the feed as set-and-forget. The levers worth working:
Position and prominence. The feed should start immediately after the article body ends; Outbrain recommends no other elements above a footer widget. Paid density. More paid cards per screen can raise revenue, as Outbrain's own guidance notes, but also raises the cost to readers. Test density rather than accepting the default; the revenue-maximizing setting is rarely the reader-experience-maximizing one, and churn is a real cost. Mobile layout. Card size, image cropping and scroll behavior matter wherever a large share of your traffic is mobile; check your analytics. Content blocks. Outbrain's publisher help describes a Filtered Content tab for blocking paid or editorial content by URL, advertiser domain, headline keyword or image, and warns that blocks on paid content restrict demand and may reduce RPM. Ask whether category-level controls are available in your agreement, and weigh the RPM cost of each block against its brand safety value; narrow blocks remove less demand than broad ones. Audience mix, long term. Commercial-intent topics may attract more advertiser demand; check that on your own pages rather than reshaping your editorial strategy around it. Page speed and viewability. The feed earns nothing if it loads after the reader leaves; Outbrain says low viewability reduces CTR and RPM, and its implementation guide covers lazy-loading setups.
Payment terms and the contract points that matter#
Payment follows the terms in your agreement. Outbrain's publisher help center says payments are sent once an account generates at least $50 in monthly revenue, through its Tipalti payment portal; in some regions publishers receive a monthly purchase order and invoice against it, and payment is due according to the contract terms. This article has no reliable data on typical payment periods, so confirm the term, threshold and process for your region in the contract.
The contract points worth actual negotiation:
- Exclusivity scope. Feed deals may include exclusivity for the recommendation slot. Understand exactly which placements are exclusive and for how long — this determines whether you can test a competitor side-by-side later.
- Guarantee conditions. Guaranteed RPMs come with traffic floors and sometimes clawbacks. Know what happens in a soft traffic month.
- Term and termination. Shorter initial terms with renewal options beat long lock-ins while you validate real RPM against the pitch deck.
- Block rights. Confirm you can block categories and advertisers without penalty, and how fast blocks take effect.
- Reporting granularity. Per-placement, per-geo reporting is what lets you optimize; monthly lump-sum reporting is what lets problems hide.
- Widget control. Who can change the feed's design, density, and organic/paid mix — you, or the partner's optimization team?
How Outbrain compares with other feed monetization partners#
Outbrain is one of several recommendation-feed monetization options. The right one depends on your audience, geography, content and the terms each partner offers. OpenAdLibrary's capture counts describe collection coverage, not the advertiser demand or revenue a network will bring to your site, so the comparison below lists what to check rather than ranking networks by volume:
| Partner | What to check |
|---|---|
| Taboola | Current publisher requirements, demand in your geos and categories, exclusivity and payment terms |
| Outbrain (Teads) | Which recommendation and video formats the agreement covers, content controls, the $50 monthly payment threshold and contract payment terms |
| MGID | Current publisher requirements, the advertiser categories that appear in your geos, and content controls |
| Revcontent | Current publisher requirements, the advertiser categories that appear in your geos, and content controls |
Creative counts do not measure revenue, and a smaller network with demand concentrated in your geo and vertical could monetize better than a larger one. Compare offers with a trial on your own traffic; the head-to-head comparison covers the advertiser-side differences between Taboola and Outbrain, and the MGID or Revcontent comparison covers those two networks.
Integration and the first month: what to expect#
Technical integration is light: Outbrain describes its JS widget code as a two-line snippet placed where the widget should appear, with widget IDs supplied by your account manager, plus an ads.txt update. How quickly you go live depends on styling and testing. The work that determines whether the deal performs happens in the first month:
- Establish a clean baseline. Capture your pre-launch metrics: revenue per session on article pages, scroll depth, bounce rate, and pages per session. The feed's real contribution is measured against these, not against zero.
- Run a holdout if you can. Serving the feed to a percentage of traffic while holding the rest back for two weeks tells you the true incremental revenue and the true engagement cost. Without a holdout, it is hard to tell whether the feed cannibalized an existing unit.
- Watch engagement metrics, not just revenue. A feed configured too aggressively lifts this month's RPM and quietly taxes return visits. If bounce rate on article pages moves more than noise, revisit density before anything else.
- Use the trial period deliberately. If you negotiated a trial before exclusivity hardens, treat it as an experiment with an end date and a decision rule — a target RPM at acceptable engagement cost — agreed internally before launch.
Expect reported RPM to move around in the first weeks as the optimization systems learn your audience; judge the deal on the settled level, not the launch week.
Audit the demand before you sign#
It is easy to sign a feed deal without systematically reviewing what runs in that feed. The ads are public when served: use the Outbrain spy tool to review captured Outbrain creatives, filtered by geo and vertical on the Founders plan ($29.99/month), and look at the geos your audience actually lives in. Captures are a sample, and the ads on your site will depend on your agreement, blocks and audience, so treat them as a preview rather than a guarantee. For the official partner-side process and current product names, check Outbrain's publisher documentation directly.
A publisher's decision checklist#
- Does your traffic profile (scale, geo mix, source quality) support a direct deal, or is a mid-tier network the realistic starting point?
- Have you browsed live Outbrain ads in your top geos and verticals, and are you comfortable with that register under your masthead?
- Have you modeled RPM from your own feed CTR and geo/vertical assumptions instead of a benchmark number?
- Do you understand the exclusivity scope, guarantee conditions, and termination terms in the draft agreement?
- Do you have block rights, per-placement reporting, and a defined trial period before exclusivity hardens?
- Is the feed positioned directly after the article body, with mobile layout tested?
Get those six answers right and you can judge Outbrain on your own data rather than on the pitch. Get them wrong and you will spend a contract term discovering what the trial period should have told you.





