Redesigning an Ad Measurement & Verification Platform: A Technical Case Study

The Scenario

A leading European independent ad-verification and insights platform — founded in 2009 and deeply integrated with demand-side and supply-side technologies — needed a full redesign of its measurement and reporting interface. The organization's platform already handled more than 500 million daily tracked ads, integrating with major DSPs including Google Display & Video 360 (DV360), Xandr, and Adform. It was also subject to annual Media Rating Council (MRC) audits, meaning any changes to measurement and data-processing methods had to remain aligned with MRC specifications and current industry standards.

The core objective was to deliver a best-in-class reporting dashboard: one capable of displaying ultra-granular data and offering maximal measurement flexibility for advertisers, agencies, and publishers.

The Approach

Rather than rebuild the platform from scratch internally, the organization chose to partner with an external development team specializing in programmatic technology and UI/UX design. This allowed their own engineering resources to remain focused on proprietary verification technology — the competitive core of the product — while the interface overhaul was handled in parallel.

The redesign was also used as an opportunity to migrate the platform to Google Cloud Platform (GCP). This infrastructure shift, combined with the new interface, was designed to deliver faster and more in-depth insights to end customers while reducing the time the internal team spent on infrastructure management.

The full project combined domain expertise in ad verification with practical experience in AdTech platform development, with particular attention paid to the communication layer between backend and frontend systems and how data surfaces in the user interface.

Implementation

Scoping and Planning

The project opened with a structured scoping phase: identifying the main technical challenges, selecting the key features for the minimum viable product (MVP), and locking in the technology stack — programming languages, frameworks, and libraries.

A two-week sprint routine was established early to keep delivery aligned with the internal team's workflow. This cadence made it possible to list, contextualize, and iterate on functional specifications in a manageable and predictable way.

Joint workshop sessions were held to sketch and design the future interface collaboratively. These sessions produced a complete set of mockups alongside all expected functional specifications. Only after the designs were approved did development move into the MVP build phase.

MVP Development

The MVP development phase focused on three parallel workstreams:

• Frontend development: Building the reporting dashboard UI according to approved designs. To accelerate delivery, existing frontend libraries were matched against the new dashboard designs, avoiding unnecessary custom component development.
• Feature development: Building out platform features including a user management component and an account access management tool.
• Backend-frontend integration: Establishing the connection between the frontend and the backend data layer.

The most significant technical work was the creation of an API system connected to Google Cloud Platform's BigQuery data warehouse. This integration enabled the interface to consume and display the enormous volume of data processed daily by the platform. Infrastructure cost containment was a stated priority: no additional services were introduced beyond what was strictly necessary.

Throughout this phase, both teams maintained constant feedback loops, with regular joint monitoring sessions to track progress against schedule and budget. Improvements were delivered in ongoing bi-weekly sprints.

Platform Components

The completed reporting interface consists of several key components:

• Homepage with monitoring panels covering reporting, viewability, brand safety and suitability, invalid traffic filtration, and geography
• Ultra-customizable reporting tool for end users
• Account and access management tool

Outcomes and Considerations

The MVP was delivered within the required timeframe and successfully launched at the beginning of 2022. Following launch, the internal team tested the MVP and fed back requirements for a post-MVP development phase in which the platform was extended with additional features.

Beyond the immediate launch, the platform was architected for maintainability: the internal team is able to make cosmetic changes independently without requiring external involvement. The resulting interface is designed to be clean, accessible, and current with industry expectations.

A few tradeoffs are worth noting for organizations considering a similar approach:

• Outsourcing UI/UX during a migration requires exceptionally tight communication between the external frontend team and the internal backend engineers. In this case, the external team actively supplied technical information to the internal engineers to improve frontend-backend communication, which was critical to keeping the integration clean.
• Leveraging existing frontend libraries instead of building custom components was a deliberate decision to compress timelines. This works well when the design can accommodate library constraints, but requires upfront alignment between design and engineering.
• MRC compliance adds a layer of audit readiness to any measurement platform's architecture. Changes to data-processing and measurement methodology must be documented and defensible, which affects how the backend data pipeline and reporting logic are designed and validated.

For organizations running high-volume ad measurement infrastructure, this kind of platform redesign — timed alongside a cloud migration and structured around short sprint cycles with clear MVP milestones — represents a pragmatic way to modernize without disrupting the core product.