TalentZoo.com |  Beyond Madison Avenue |  Flack Me |  Beneath the Brand Archives  |  Categories
How Building an Ad Server Saved Timehop
By: Digiday
Bookmark and Share Subscribe to the Digital Pivot RSS Feed Share

Timehop had three months of runway in the bank when it decided its current advertising solution wasn’t going to cut it. The app — a way to reminisce on photos and posts across social media — had raised $14.1 million since its launch in 2010. If it was going to ever return that money to investors, the company had to do something else.

“Millions of people use it every day. We can’t just shut it down. At that point, we had so many ideas of what else to do. Maybe we fail and it still ends but we should not end it here?” said Matt Raoul, CEO of Timehop.

As Twitter knows well, you can just shut apps down. But Raoul, Timehop’s design lead who was promoted to CEO after his predecessor left for Snapchat, decided against a quick demise. Instead, the plan was to boost its programmatic advertising. The 15-person team ended up building its own ad server. A year and a half later, the app’s CPM has grown from $2 to $28. Timehop is currently profitable with 50 percent margins this quarter.

Timehop’s leadership team, seated in a conference room within a Soho office featuring framed photos of the app’s mascot Abe the dinosaur, described a journey of exhausting ad tech solutions from January to October 2017. During that time, Timehop hired David Leviev, who worked in ad tech prior, as director of programmatic and partnerships. They moved from using a bunch of SDKs to trying a third-party ad server, which initially gave them a nine-fold increase in revenue.
 

“We didn’t really understand our own inventory because all we had was the viewability of these two demand partners. We were kinda content with that $2 [CPM] because we thought we were valued at that,” Leviev said.

But after their third-party ad server was down for a weekend, Leviev began to consider moving it all in-house. He declined to name the company’s previous partners.

“Typically reporting is down, and you wait 24 hours. We sent them an email, another email. Three days worth of revenue down the toilet. We got no reassurance we were a priority so we understood the need to have control and viewability in-house,” Leviev said.

In November, Timehop instructed some of its product engineers to begin building an ad server that focused on its own inventory, mobile-only. Leviev said they also wanted to maximize CPM and fill rate, not just choose one or the other. Currently, the system integrates with about 15 SSPs and DSP, the exact number depending on the day.


READ MORE 

 



Bookmark and Share Subscribe to the Digital Pivot RSS Feed Share
About the Author
This article was published on Digiday.com.  A full link to the original piece is after the story. www.digiday.com
Digital Pivot on

Advertise on Digital Pivot
Return to Top