Run of Network (RON)
Run of network (RON) is an ad buying option where a campaign can serve across any site, app, or feed in a network's full inventory pool, instead of being limited to hand-picked publishers or placements.

Run of network (RON) is an ad buying option where a campaign can serve across any and all sites, apps, or feeds in a network's inventory pool, rather than being restricted to specific placements, verticals, or hand-picked publishers. It's the broadest targeting setting most self-serve dashboards offer, and it's often the default a new campaign starts on before you narrow anything down.
How RON targeting works in practice#
On most native self-serve platforms, RON sits at one end of a targeting spectrum. At the narrow end you can build a whitelist of specific approved sites, or lean on contextual targeting to match your ad to relevant content categories. RON skips both and opens the campaign to the network's full pool, layered only with basic filters like geo targeting or device type. Media buying for native ads covers where RON fits in a typical campaign build sequence, usually as the starting point for volume before you optimize down to better-performing placements.
The naming isn't universal across networks either. Some dashboards label the broad option "run of network" explicitly, while others simply present it as the default state before you apply any site-level filter, so it's worth confirming exactly what a given platform's default targeting setting actually covers before assuming it means the same thing everywhere.
When RON makes sense, and when it doesn't#
RON's main advantage is reach and, usually, lower CPCs than a tightly whitelisted buy, since you're competing for the network's broadest, least-curated supply. That makes it a reasonable starting point when you're testing a new offer or a new geo and need volume fast to see what converts before you know which specific placements matter. The downside is control: you'll land on a wider mix of contexts, some of which won't fit your brand safety standards, and performance variance tends to be higher than a curated buy.
The practical pattern most media buyers settle into is starting broad with RON to gather data, then excluding poor-performing sites and narrowing toward a whitelist once enough spend has run to see where results actually cluster. A common approach is to run RON for a modest test budget over several days, pull placement-level performance, cut anything with volume but no conversions, and only then decide whether a tighter whitelist is worth the reduced reach. Understanding how much native ads cost at the RON versus whitelisted tier helps set realistic budget expectations before you commit.
Seeing which advertisers and creatives keep running on a given network is a useful shortcut too. OpenAdLibrary's Taboola ad library shows captured creatives and how long they were observed running, which helps you gauge what advertisers sustain before you decide how tightly to target your own buy.







