JSON Ads Are the Key to Fully Integrated Native Advertising
Let's be real— publishers want simple advertising solutions that let them spend more time on creating content and building their business. They want to be able to implement tags without a hassle, offer their inventory to buyers without jumping through hoops, and maximize their inventory's value.
But simple doesn't always translate to effective. In the real world, publishers have to pick two out of the three: maximum ease of set up, maximum value, or maximum availability.
JSON native ads offer the latter two.
The problem with "faux native"
Still, implementing these should build revenue in ways display ads can't, right?
Not exactly. There are two problems with these "faux native" units:
Most of the time, their content isn't actually native. For example, the network will serve the same testosterone-boosting ads regardless of their audience or the vertical of their site. This is little better than tapping into the most generic of ad networks with the lowest CPMs.
Not only is the content not native, but neither is the form of the ads. Web users aren't stupid. They are learning to recognize which part of the page is content and which is text-based advertising. Font changes and eye-popping images distract them from the experience of browsing the page, and in time these ads are as glossed over as any of the standard banner units.
The key to good native ads has always been the right fit between why a user is on a page, and what the ad is able to offer. But the central challenge to native advertising has been scalability, which is what the "faux native" units are trying to solve.
Scalability can only happen through JSON ads
That JSON doesn't render ads in a browser makes it the ideal format for native. A publisher's CMS can ingest the ads any way it sees fit, and more importantly, an advertiser can buy native inventory across hundreds of sites and let publishers style the ads in ways appropriate for their content.
This is the key to native scalability— ads that can be displayed across the web in a variety of contexts, all thanks to a versatile data format.
JSON ads are already here
OpenRTB responses are returned as JSON, which not only delivers the ad contents to a publisher in real-time but gives access to bid data and other metadata from the transaction. This happens for both display and native.
Some of our customers at Adzerk use JSON metadata to serve ads stored hosted on their local servers. They use the metadata from the ad response to determine which ad to serve, which keeps the ad rendering 100% local (and thus prevents it from being blocked by ad blockers).
Ad servers must support JSON ads
JSON support is already a requirement for publishers looking to use an ad server for native RTB or home-grown native ads, and it will become even more essential in the months to come. The ad industry is becoming more data-driven and more focused on native, and an ad server has to keep up with the industry's demands, preferably leading the charge.
Adzerk supports all the latest native standards from the IAB, and our publishers demand the best performance and analytics from their native ads. By developing an infrastructure-building platform for publishers and their developers, we are prepared for the future of native ads, whether it continues down the JSON route or takes a new direction.
Want to Learn More?
Adzerk is an API-based platform for building your own JSON server-side ad platform. If you'd like to learn more, get in touch with us.