Publisher Case StudyAd TechLatency & PerformanceNative AdvertisingContent Delivery

Wise Publishing Gets Wise To Latency Reduction

AdExchanger
Wise Publishing Gets Wise To Latency Reduction

Frequently Asked Questions

What problem was Wise Publishing trying to solve?

Wise Publishing needed to reduce ad latency because slow-loading ads caused poor user experience and lost monetization opportunities, especially given the spend on paid user acquisition.

What solution did Wise Publishing implement?

They integrated Nativo’s Content Edge, a supply-side ad server hosted on a content delivery network that runs unified auctions and reduces client-side JavaScript to cut latency.

How much did ad load times improve after implementing Content Edge?

Average ad load times improved from about 4.2 seconds to roughly 0.6 seconds after implementing Content Edge.

Did reducing latency affect Wise Publishing’s available inventory?

Yes — Wise increased its overall available inventory by around 20% after adopting the Content Edge approach.

How did this change affect Wise Publishing’s relationship with Google/DFP?

Wise pared down display inventory passed to Google; after the change about 50% of display placements are filled through Nativo, meaning less inventory is reaching DFP.

AI-Generated Summary70-80% of original length
Original Article

AdExchanger | July 23, 2019 - Slow-loading ads are still a perennial problem for publishers.

Wise Publishing, a Toronto-based publisher of personal finance content with around 5 million monthly unique visitors, acquires a significant portion of its traffic through paid channels. But if an ad loads slowly and a visitor leaves, so does that monetization opportunity.

“Dealing with latency is incredibly important to us, because the balance between paid performance and the sums we’ve spent to acquire users can make or break the margin for a campaign,” said Wise CTO Nic Skitt.

Header bidding, for example, increases demand but can also introduce latency, so Wise is always trying to improve page delivery performance.

One tactic has been to integrate with a supply-side ad server developed by Nativo called Content Edge, which hosts unified auctions and ad serving on a content delivery network. It’s a setup that eliminates a bunch of the JavaScript that would normally just get loaded directly onto a client’s page, said Nativo’s CEO and president, Justin Choi.

On average, the publishers Nativo onboards have four to six seconds of latency – and, in some desperate cases, up to 10 seconds – before the content loads and the ads start to come in, which “causes a bad user experience and pushes the content around on the page,” said Tim Cavanaugh, director of publisher development at Nativo.

On its face, it might seem inefficient to have an ad server just for native. But the pitch is to reduce latency for native placements, and then convince publishers to open up their non-native demand, too.

Over the last number of months, Wise has pared down the amount of display inventory it passes to Google. Today it fills around 50% of its display placements through Nativo. “DFP is seeing a lot less of our inventory,” Skitt said.

Since implementing Content Edge, Wise has seen ad load times go down from 4.2 seconds to 0.6 seconds, on average. Wise has also been able to increase its overall available inventory by around 20%.

Read more on Adexchanger.com

adexchanger-logo.png