Interactive Analytics at MoPub (Twitter): Using Druid and Imply to Query Terabytes of Data in Seconds

Jul 05, 2019
Rick Bilodeau

MoPub, a Twitter company, provides monetization solutions for mobile app publishers and developers around the globe. They operate at a massive scale. The MoPub platform addresses over 1.7 billion monthly unique devices, 1 trillion monthly ad requests, 52,000 apps, and 180 demand side partners.

MoPub has just launched a new solution called MoPub Analytics based on the Apache Druid real-time analytics database and using Imply Pivot as the drag-and-drop UI. The solution allows MoPub customers to answer business questions, troubleshoot issues and optimize revenue. Users can determine the root cause of new data trends by interactively analyzing the data across many different time slices, dimensions, and metrics.

Every day, MoPub runs over 30 billion ad requests, which generate over 150 terabytes of raw logs. Even after aggregation they ingest over 9 billion rows into the analytics engine each day. Queries on MoPub Analytics return in seconds.

You can find the MoPub Analytics post on the Twitter Engineering blog.

A great way to get hands-on with Druid is through a Free Imply Download or Imply Cloud Trial.

MoPub Analytics Architecture

architecture-diagram-mopub-analytics-twitter

Other blogs you might find interesting

No records found...
Feb 25, 2026

Imply Lumi Product Preview:  Removing the Cost–Performance Tradeoff in Observability

If you caught our recent product update, you’ve already seen the pace of development on Imply Lumi has been relentless. Last quarter, we delivered major performance and usability improvements to data...

Learn More
Feb 03, 2026

Imply Lumi product update: what’s new

Since releasing Imply Lumi in September 2025 as a decoupled data layer for observability, the Imply R&D team has been hard at work to make it easier and more economical to retain, query, and analyze observability...

Learn More
Dec 19, 2025

The Most-Read Imply Blogs of 2025 (and what they signal for 2026)

Before we take on 2026, let’s rewind. 2025 was the year observability teams stopped asking, “How do we reduce data?” and started asking the real question: “How do we build an architecture that can keep...

Learn More

Ready to decouple your observability stack?
No workflow changes. No migrations. More data, less spend.

Request a Demo