If you are an existing Content Ignite publisher, you will have made the up-front choice to go down the plug-and-play (P&P) route, where you use our demand, or the SaaS route, where you connect in your own Google Ad Manager account.
Both are great options, with SaaS opening out our full tech offering to use as you see fit and P&P offering easy and quick monetisation.
But what about those times when you’d like our help with demand while running your own direct campaigns through your own GAM?
Or perhaps you have your own strong demand in some regions, but would be happy to have some help in others?
Previously, addressing these scenarios wouldn’t be possible. The choice of P&P vs SaaS was made at the top organisation level, and that was that. Well, not anymore!
With Publisher Cloud v4.0, we move the ad server choice from the highest level to the lowest. Ad servers can now be chosen per tag config.
Let's go back to the basics for those unfamiliar with Content Ignite; our system is made up of organisation, user, publishers and tag configs:
Tag configs are the place where ad unit choice, targeting and behaviours are chosen. Mix and match as many configs as needed to achieve your desired outcome.
Now with the inclusion of ad server within tag configs, all the targeting you previously had available such as geo, device type and URL path, can now be combined to decide which ad server is responsible for serving to that unit. You can use ours, just as you could with P&P, but you can also use your own; connecting to multiple GAM accounts for the first time.
With a tighter integration to GAM, connect to your account once and select it at the tag config level, and choose the target ad unit from a pre-populated list (or allow us to make a new one for you!).
Have a direct deal come in that you want to serve from your GAM to a single unit on page? Just switch the ad server for that unit, hit save and suddenly you are in control of demand, while everything else continues to run as before. Ultimate ease for a powerful and complex setup.
Our integrations can go even further still, drop in your ads.txt requirements for your ad server, and our system will check your publishers daily and inform them of any missing lines as well as email out a weekly report. No more missed opportunities because of missing lines, your ad server is a first-class citizen inside our platform and has the same features available to it as our own which powers our P&P offering.
A number of other useful changes were made in this rollout, dig into them over on our changelog: https://docs.contentignite.com/change-log/.
Content Ignite has unveiled the Publisher Hub—a comprehensive platform consisting of three key areas: Ads.txt Insights, Core Web Vitals monitoring, and Revenue Analytics.
View ArticleContent Ignite, the publisher-first advertising technology and monetisation platform, is delighted to announce its certification as a Google Certified Publishing Partner (GCPP).
View ArticleContent Ignite’s advanced experiment technology now offers a powerful platform for publishers to test, refine, and perfect their ad revenue strategies
View ArticleAs no clear path or definitive solutions have emerged, it is vital that publishers explore new areas, test new partners and experiment with new technologies to maintain their revenue streams.
View ArticleDemand Path Optimisation (DPO) and Supply Path Optimisation (SPO) are two strategies in digital advertising, specifically in the programmatic ecosystem, aimed at improving the efficiency and transparency of the ad supply chain. Both focus on optimising different parts of the ad transaction process, but from different perspectives.
View ArticleA guide of wow to improve your Ads.txt file and 5-step overview of understanding our Ads.txt Insights tool
View ArticleWe only need your email and domain to complete each healthcheck