Raydar free tools · Link decoder

Decode a link with obOrigUrl in it

The slug here is lowercase, but the parameter Outbrain actually sets is obOrigUrl, capital O twice. In real links its value is usually just true.

Example: https://www.example.com/news/story-headline?obOrigUrl=true

Case matters here

The slug on this page is lowercase for readability, but the parameter Outbrain actually sets on a link is obOrigUrl: capital O on Orig, capital U on Url. Query parameter names are read literally by most servers, so a lowercase rewrite like oborigurl is a different string as far as the redirect logic is concerned. If you are rebuilding or testing a link by hand, rather than just reading one someone sent you, keep the camel case exactly as it appears.

What the value actually holds

Most tracking parameters on links like this are opaque tokens, a string of letters and numbers that only means something inside the ad network's own database. obOrigUrl is different. In real links its value is usually just true, sitting on the article URL you landed on, not a token.

Set during the widget click

Outbrain sets obOrigUrl at the moment you click a thumbnail inside one of its recommendation widgets, the "around the web" or "you may also like" boxes under a news article. Clicking sends your browser first to an Outbrain tracking domain. In archived real links, obOrigUrl sits on the destination page URL itself.

What happens if you strip it

For the visitor, removing obOrigUrl from a link you already landed on does not change the page, since its value is usually just true.

For the publisher, the most it can lose is a flag Outbrain's own scripts may read; a value of true cannot identify a specific placement on its own. Compare this to Taboola's tblci, a unique opaque click id, or to Yandex's yclid from its own ad network. More parameters are indexed at the link decoder hub.

No public specification, and why that matters here

Outbrain has not published a formal, versioned specification for obOrigUrl the way Google documents gclid or TikTok documents ttclid. What is verifiable is the parameter as it appears in real links: obOrigUrl=true on the article URL a reader lands on. Treat any specific claim about its internal handling, including on this page, with the same caution the absence of public documentation warrants.

A worked example, decoded

Paste https://www.example.com/news/story-headline?obOrigUrl=true into the decoder above. obOrigUrl comes back as true, a flag sitting on the article URL itself rather than an address.

Common mistakes

  • Rewriting the case of the parameter name. obOrigUrl with its exact capitalization is what Outbrain's redirect server expects. Lowercasing it to build or test a link by hand risks the parameter going unrecognized.
  • Assuming it behaves like an opaque click id such as tblci. Taboola's tblci is a lookup key with no readable content. obOrigUrl usually carries just the value true.

Questions

Is obOrigUrl officially documented by Outbrain?

Not in a public, versioned specification the way Google documents gclid. What's verifiable is how it appears in real links: obOrigUrl=true on the article URL a reader lands on. Treat specific behavioral claims about it, including elsewhere on the web, with some caution given the lack of a public spec.

What does the value inside obOrigUrl actually contain?

Usually just the value true, a flag rather than an opaque token or an address.

Is it safe to edit or strip obOrigUrl before a click finishes?

Its value is usually just true, not the destination. After the click has already resolved and you're just tidying a link before sharing it, removing it is safe and only affects Outbrain's own attribution reporting.

Related parameters: yclid · mkt_tok · _hsenc · ScCid

Give your bio link a brain.

Build your page, watch who converts, free to start.

Get started free

No card required.