How to Tell If a Website Uses Outbrain

Outbrain is, alongside Taboola, one of the two dominant native-advertising and content-recommendation networks — the source of the "Recommended by Outbrain" grids of article-style links below the content on news and media sites. Because it loads from a distinctive domain and renders branded widgets, detecting it is straightforward: look for the widgets.outbrain.com/outbrain.js loader and the global obApi object. This guide covers every reliable signal, the recommendation model behind them, the look-alikes to rule out (chiefly Taboola), and what Outbrain usage tells you about the site, its scale and how it monetises its traffic.

What is Outbrain?

Outbrain is a content-discovery platform that publishers embed to recommend content and monetise traffic. Its widgets — branded "Recommended by Outbrain" (or "More from the web") — display a grid of article-style links blending the publisher's own content with paid native ads from advertisers. Publishers earn when visitors click sponsored links and use the widgets to circulate their own content. Outbrain is a staple of news, media and large content sites, and it is the primary competitor to Taboola in the native-ad duopoly. (Outbrain also acquired Teads, expanding its video and reach.)

For detection, the key context is that Outbrain is native advertising / content recommendation — a different monetisation model from display ads (AdSense) or search ads (Google Ads). Finding it tells you the site is a content publisher monetising with native widgets, almost always a news or media property with meaningful traffic (native-ad networks partner with established publishers). Because Outbrain loads from its own CDN and renders clearly-branded widgets, it is easy to confirm. Its presence marks the native-ad-monetised publisher segment, much like Taboola.

How Outbrain loads and renders

An Outbrain install loads its library from widgets.outbrain.com/outbrain.js and exposes the global obApi function (used for tracking and configuration, e.g. obApi('track', 'PAGE_VIEW')); some installs also expose an OB object. Widget placements are marked up with container elements carrying attributes like data-widget-id (or data-ob-template, data-src), which identify the specific Outbrain placements configured for the publisher. The library renders the recommendation grid into these containers, showing the "Recommended by Outbrain" branding.

The widget IDs identify the placements (and thus the publisher's configuration), and the branding is the visible front end. Outbrain fires impression and click tracking to its domains. So an Outbrain site shows the widgets.outbrain.com/outbrain.js loader, the obApi/OB global, and the branded recommendation widgets. Knowing these — the outbrain.js loader, the obApi/OB global, the data-widget-id attributes, and the "Recommended by Outbrain" widgets — makes detection quick and placement-identifiable.

How to tell if a website uses Outbrain

Confirm at least one strong signal.

1. Check the Network tab. Filter for outbrain. The loader from widgets.outbrain.com/outbrain.js is the definitive signal.

2. Use the console. Type obApi (or OB) and press Enter. A returned function/object confirms Outbrain's library is present.

3. Look for the widgets. Scroll below an article and look for "Recommended by Outbrain" (or "More from the web") recommendation grids.

4. View the source. Search for outbrain or data-widget-id. The outbrain.js reference and widget container attributes are usually visible.

5. Read the widget IDs. The data-widget-id attributes identify the Outbrain placements configured for the publisher.

What the Outbrain signals look like

<script type="text/javascript" async src="https://widgets.outbrain.com/outbrain.js"></script>
<div class="OUTBRAIN" data-src="https://example.com/article" data-widget-id="AR_1"></div>
window.obApi = function() { … }   // obApi('track', 'PAGE_VIEW')
// Widget shows "Recommended by Outbrain" below the article

The combination of the widgets.outbrain.com/outbrain.js loader, the obApi/OB global, and the "Recommended by Outbrain" widgets is conclusive.

Outbrain versus other ad networks — avoiding false positives

Match the domain, global and branding to keep native-ad networks distinct. Outbrain uses widgets.outbrain.com/outbrain.com, the obApi/OB global and "Recommended by Outbrain" branding; Taboola (its closest rival) uses cdn.taboola.com, the _taboola array and "Sponsored Content"/"Around the Web" branding; AdSense is display ads on googlesyndication.com; Criteo is retargeting display. Because Outbrain and Taboola widgets look so similar, the domain (outbrain.com vs cdn.taboola.com), the global (obApi vs _taboola) and the branding text are the discriminators. A publisher may run both Outbrain and Taboola, or run native recommendations alongside display ads — these monetisation methods coexist.

How reliable is each Outbrain signal?

The widgets.outbrain.com/outbrain.js loader is definitive, as is the obApi/OB global. The "Recommended by Outbrain" widgets corroborate (the branding is characteristic), and the data-widget-id attributes identify placements. The weakest situation is a widget that lazy-loads on scroll, so check below the article — but the loader and global are present from page load. As a rule, the outbrain.js loader or the obApi global settles it, and the widget IDs identify the placements.

What Outbrain usage reveals about a site

Finding Outbrain signals a content publisher monetising with native recommendation widgets — almost always a news or media site with meaningful traffic, since Outbrain partners with established publishers. Its presence tells you the revenue model includes native/recommendation advertising and that the site is a substantial content property. If you sell publisher tools, content, audience or ad-optimisation products, an Outbrain site marks an established publisher. The widget placements and whether Outbrain runs alongside Taboola or display ads indicate the breadth of monetisation. As with other ad scripts, Outbrain's widgets affect performance, a relevant consideration. The choice of Outbrain over (or alongside) Taboola is a small competitive detail in the native-ad market.

What finding Outbrain means for sales, agencies and competitive research

For sales and prospecting, Outbrain marks an established content publisher monetising with native ads — a fit for publisher infrastructure, content, audience and ad-optimisation tools, and a signal of meaningful traffic.

For agencies and consultants, finding Outbrain tells you the client is a serious publisher with native-ad revenue, so engagements can address monetisation, content strategy, audience growth, or the performance cost of recommendation widgets.

For competitive and market research, Outbrain (versus Taboola or display-only) reveals a publisher's native-ad partner and strategy. Spotting it across a media segment maps the native-ad-monetised players and the Outbrain-versus-Taboola split, useful when benchmarking publisher monetisation.

Outbrain in the wider publisher stack

Outbrain sits in the monetisation layer of a content publisher's stack, much like Taboola. It accompanies a CMS (WordPress or a custom/enterprise publishing platform), editorial and traffic analytics (GA4 plus often comScore or Chartbeat), display advertising (Google Ad Manager/AdSense), and a consent-management platform. Large publishers run Outbrain alongside header bidding and multiple ad partners. For an auditor, the valuable details are the Outbrain widget IDs, the placements, whether Taboola or display ads also run, the editorial analytics, and the consent setup; together these reveal an established content publisher and the breadth of its monetisation strategy. It is also worth remembering that Outbrain acquired Teads, expanding into video and broader reach, so on some publishers an Outbrain relationship may extend beyond the recommendation widget into video advertising — a hint that the publisher's monetisation with Outbrain is deeper than the visible "Recommended by Outbrain" unit alone suggests.

A quick Outbrain confirmation walkthrough

Open the site (ideally a news or article page) with developer tools on the Network panel and filter for outbrain. Look for the loader from widgets.outbrain.com/outbrain.js. In the console, type obApi (or OB) to confirm the global. Scroll below the article content to find "Recommended by Outbrain" recommendation grids. View the source for outbrain and data-widget-id attributes. The widgets.outbrain.com/outbrain.js loader or the obApi global confirms Outbrain, and the widget IDs identify the placements.

A quick Outbrain detection checklist

• Filter the Network tab for outbrain; the widgets.outbrain.com/outbrain.js loader is conclusive.
• Type obApi (or OB) in the console to confirm the global.
• Look for "Recommended by Outbrain" widgets below articles.
• Read data-widget-id attributes to identify placements.
• Distinguish Outbrain (outbrain.com, obApi) from Taboola (cdn.taboola.com, _taboola).
• Note accompanying display ads and editorial analytics for the full picture.

Detecting Outbrain at scale

Checking one site is quick, but mapping native-ad adoption across many domains — to find and segment content publishers — calls for automation. StackOptic detects Outbrain and thousands of other technologies from a real browser, reading scripts, globals and widgets. Like Taboola, Outbrain partners mainly with established, higher-traffic publishers, so finding it across a media segment flags the more substantial properties, and the widget IDs help group placements that belong to one publisher. The most useful market-level insight is the Outbrain-versus-Taboola split: tracking which network each publisher in a sector has chosen, and where they overlap, maps how the native-advertising duopoly divides the content landscape — valuable context for anyone selling tools, content or audience services to publishers, or benchmarking how rivals monetise their traffic. For related reading, see our guide to finding out what analytics a website uses and the full Outbrain technology profile.