More and more sites are moving towards native ads instead of avoiding site monetization or relying on annoying pop-up ads. But what is native advertising? Why are it appearing online and in apps?
In this article, we define native advertising and discuss how these ad types can monetize your website/app experience.
Native advertising means integrating ads seamlessly into your feed, homepage, search results, and more. Often, these native ads look identical to your standard content, except with an added “sponsored” or “promoted” tag.
However, other industries are moving towards integrating native advertising into their sites/apps. WeTransfer (a file transfer service), for example, shows skin ads on their homepage. These promotions allow WeTransfer to monetize their free users without disrupting the user experience. Additionally, others — from fintech to marketplaces — have built native ad platforms for sponsored deals, promoted listings, and other featured content.
Overall, native advertising was nearly a $100B market in 2023. More and more advertisers are looking to innovative, native display ads rather than standard banners. Advertisers are demanding these innovative formats because of their high user engagement. And, publishers are looking for true native, server-side ads because of their seamless integration with their existing site and surrounding content. This further engages users, leaving them with a positive site experience and keeping them on the page for longer.
Overall, native ads encompass a variety of formats, like video ads, sponsored listings, in-feed ads, native skin ads, and more. Each of these formats are substantially growing in popularity. Consider Amazon, who scaled their ad business to nearly $47B in 2023 mainly by running native sponsored listings. Clearly, these organic-looking ads are winning advertisers and users over, meaning more publisher revenue.
There are three ways to integrate native advertising into your platform: a homegrown ad product, a third-party ad server, or an ads API solution.
Here, you’d build out a large tech team and design the ad product from scratch. By building it from the ground up, you have full control over its scope and vision. Facebook, Amazon, and Pinterest took this route.
Alternatively, you might consider a third-party ad solution, such as Google Ad Manager’s ad server or a “native” ad network like Outbrain or Taboola. All of these solutions will be client-side and involve JavaScript tags or in-app SDKs.
The final option is building the ad platform yourself, but using ad APIs to speed up the time to launch, similar to building your communications solution on top of Twilio. With these tools, you integrate via APIs to get instant access to the building blocks you need to design a native ad product, including ad decisioning, tracking, targeting, management, and reporting.
For instance, Chairish is a marketplace for buying and selling antique furniture. They created a new revenue stream by letting vendors promote their listings, similarly to Amazon’s and eBay’s ad platforms. These native ads appear simultaneously alongside organic search results.
You may currently use Google Ad Manager (which has 90% of the ad server market) or be thinking about a third-party ad network like Outbrain, Sharethrough, AdBuff, Polymorph, or Criteo.
While these tools allow you to insert native-esque placements, they nonetheless are flawed because the integration is client-side and relies on JavaScript tags or bulky in-app SDKs.
Client-side ad serving involves inserting ad code directly onto the page/app. These tags then ping the ad tech vendor directly, who picks the winning ad and inserts it wherever the code was placed.
The alternative is a server-side integration, enabled by ad APIs. Server-side calls happen outside of the client, via a backend request. You post an API request and get a response containing the winning ad’s details, which you then parse and place directly into your site/app as it loads. No JavaScript ad tags are needed.
Ultimately, the benefits of server-side over client-side integrations include:
Most third-party tools — like GAM and Outbrain/etc. — do not offer a server-side integration. If launching pseudo-native placements quickly is your goal, you can use these tools, but they aren’t advised if you want to build a full-featured, truly native ad product.
Instead, besides building the platform yourself from scratch, your best option is an ads API partner, who is server-side by default.
The United States’ FTC requires publishers to differentiate ads from organic content. Here’s a quick checklist to see if your native ads fit within FTC guidelines:
Are they distinguishable? In this WeTransfer example, the skin ad for American Express is obviously an ad, not standard content.
Did you provide disclosure? If the native ad is not distinguishable, is it labeled using non-ambiguous terms and without any blockage?
For more information, see our article on FTC native ad compliance.
The native advertising sector is expected to be worth $400B by 2025. Advertisers are increasing their native ad budgets, hoping to capitalize on the higher engagement rates of these ad units. Now is the time to build an ad platform that supports this.
Your ad revenue is dependent on many factors, including your traffic size, product, amount of ads, fill rate, etc. Below provides our analysis of average CPMs for various native ad units, as well as educated guesses on the CPMs that major ad platforms drive. (“CPM” stands for “cost-per-mille” and refers to the revenue you make for every 1,000 ad impressions).
It should be noted that these values are all much higher than standard programmatic banner ads -- which can average $0.50 - $1.50 -- highlighting the great opportunity every publisher has in launching or switching to native advertising.
If you’re interested in launching native advertising — and don’t want to wait years — we’d love to chat. Kevel is the industry leader in ad APIs, and we’ve helped other brands like WeTransfer, Slickdeals, and Ticketmaster integrate high-revenue native advertising in just weeks.