What a Native Ad Server Offers that a CMS Doesn't

If you're new to the native ads game, you are probably learning a lot about native ad servers and how they differ from a CMS. Chances are that you're using a CMS already, and it's likely been highly customized to meet your site's needs.

So is it possible to configure your CMS to serve native ads?

Not really. While there is some overlap between a CMS and an ad server, they are intended for different uses:

A CMS is designed to serve content that doesn't need to change with each request.

By request, we mean each time a browser reaches out to a server to get the content and render it as a page.

In most cases, a CMS serves HTML pages and related content like images, HTML5 videos, etc. and it will have built-in tools that make it easy to manage the content. The big three— WordPress, Drupal, and Joomla— all do a great job at this, and they are also specialized to deliver specific types of web content: blogs, landing pages, large, complex enterprise sites, etc.

But no CMS is specialized at serving ads, no matter if those ads are banners, native units, or full-out sponsored content.

Ads have different requirements than static web content.

Advertisers need to track metrics that most CMS' won't offer: clicks, conversions, impressions for individual units on a page, viewable impressions, and more.

Even more importantly, ads aren't served the same way to all users.

In the simplest ad serving scenarios, a website might sell an ad unit and use their CMS to add a banner to the page, creating a placement. When that sponsorship expires, they will sell another ad and update their CMS accordingly.

But most sites want to sell more than one unit at a time, which requires rotation. And nowadays most ads are precisely targeted to users through retargeting, behavioral targeting, location targeting, and ad sold via real-time bidding. A CMS cannot support that— either for banners or native ads.

Why not add use an add-on to my CMS to serve ads?

Most add-ons that enable a CMS to serve ads (like WordPress plugins) are actually just interfaces for an ad server. For instance, Adzerk has a plugin for Drupal developed by that community. However, using the plug requires an Adzerk account, so ad servers never leave the equation.

Also, plugins are limited in their functionality. An ad server that includes an API (like Adzerk) can offer more options for integration with your CMS than a third-party plugin. You can serve ads via Javascript tags, Python or Ruby libraries, mobile SDKs, or write your own code to ping the API directly.

The advantage for native content

The right native ad server for you will let you serve the type of native content you want (such as sponsored content, in-feed units, or interactive ads) with minimum set up time and difficulty to maintain. For example, if you are only serving sponsored articles, choose a native ad server that specializes just in that.

But if you need a more complete solution (like a combination of banners and native units, or custom native units) then you should consider a more robust ad server like Adzerk. Please get in touch with our solution engineers if you aren't sure which native ad server is right for you— we'll be happy to point you in the right direction.