Ad revenue analytics

Reconcile ad performance with your content analytics — at the page view level

Revenue per article · RPM per traffic source · Viewability per page · Included with your subscription

Start free trial — 7 days Request a Demo

Editorial analytics and ad performance live in two different worlds. Alke Analytics reconciles them natively, at the page view level — no external yield tool, no spreadsheet workflow, no extra events to instrument.

Why content publishers need a different approach

The challenge:

Your content metrics are in your analytics tool. Your ad metrics are in your adserver, your prebid wrapper, and a yield management tool on top. To answer questions that should be simple — which articles actually generate the most revenue, which traffic source produces the highest RPM, how does a new ad layout affect viewability — you export from both sides, reconcile in a spreadsheet, and hope the numbers line up.

The result: editorial decisions made without revenue visibility, ad ops decisions made without content context, and acquisition strategies optimized on pageviews instead of yield. Ad revenue is the largest line of your P&L, but it sits outside the tool your teams use every day.

What you can finally answer

Native page-view-level reconciliation unlocks the questions your editorial, acquisition and ad ops teams have always had to answer in spreadsheets.

Which content generates the most revenue

Revenue per article, per format, per category, per author — using the same content dimensions your editorial team already works with. Stop optimizing for pageviews when the goal is revenue.

Which traffic sources produce the highest RPM

RPM per acquisition channel — SEO, social, direct, referral, newsletters. Identify the traffic that actually pays, and reallocate effort accordingly. Until now, no standard analytics tool could compute this natively.

How ad layout impacts viewability and revenue

Real viewability and revenue per placement, cross-referenced with content type, device, and audience segment. Understand which placements perform on which content — and where you're trading user experience for yield that doesn't materialize.

What's happening at the session and user level

RPM per session, per user, per page view. Compare engaged users to one-page sessions. See how content depth correlates with monetization, not just with time on site.

Native reconciliation, at the page view level

For every consented page view, Alke Analytics collects the ad metrics alongside the content metrics.

Metrics collected per page view

  • Ad requests sent to the adserver
  • Ads served on the page
  • Viewability measured against Active View standards, aligned with adserver reporting
  • Revenue, categorized by source — prebid, ad exchange / EBDA, and direct sales
  • Ad clicks

Reconciliation is performed next-day, so editorial, acquisition and ad ops teams open the same dashboard each morning with revenue context already attached to every page view from the day before.

Cross with every dimension you already use

Ad metrics are first-class data in Alke Analytics — they work with every filter, group and comparison the platform offers.

Filters, group views and API

  • Filter ad revenue and viewability by content category, format, author, section, or any custom dimension
  • Compare revenue across properties in group view — same one-click switch between group and single-property analysis
  • Build cross-platform comparisons mixing ad metrics with audience, engagement and Core Web Vitals
  • Access all ad metrics through the REST API and scheduled exports — same model as the rest of the platform

The same reports, filters and comparison tools you already use now show what they generate in revenue.

Privacy and compliance, end to end

Ad reconciliation is only performed on page views that have given consent to Alke Analytics as a vendor. The consent-free measurement layer remains unchanged: aggregate audience, engagement and content metrics are still collected across 100% of traffic, just without the ad-level reconciliation that requires consent.

Dual-layer architecture

  • Without consent: aggregate audience and content measurement on 100% of traffic
  • With consent: full reconciliation with ad performance, attribution dimensions, and user-level analysis

End-to-end compliance, with the same vendor, in the same platform.

How it works

1. Authorize API access

Grant Alke Analytics access to your ad management environment through an API client. No code change on your side, no script to add to your pages.

2. Technical setup in hours

Our team configures the connection, validates the mapping with your existing properties, and runs verification on a sample period. The full activation typically takes a few hours.

3. Next-day data, in the same interface

From day one of activation, your ad metrics appear in the existing Alke Analytics reports, alongside your content metrics, with the same dimensions and filters.

Included with your subscription

Ad revenue analytics is part of every Alke Analytics subscription at no additional cost. Reconciled ad metrics don't count as additional events — they enrich the page views you're already collecting.

Compared to running a separate yield or ad analytics tool

  • No duplicate billing — included in your existing volume tier
  • No extra events — the reconciliation enriches existing page views, no impact on your billable volume
  • One interface, one data model, one DPA — same as the rest of the platform
  • No engineering project — API authorization and configuration, not an integration build

Frequently asked questions

Which adservers are supported?

Alke Analytics supports the most common ad management configurations used by European publishers. Contact our team to confirm coverage for your specific setup.

Is there an extra cost?

No. Ad revenue analytics is included in every Alke Analytics subscription. The reconciliation doesn't generate additional billable events.

How fresh is the data?

Reconciliation is performed next-day. Content analytics remain real-time and unsampled — only the ad reconciliation layer is delayed by the inherent constraints of adserver data availability.

Is the revenue net or gross?

Revenue values match what your adserver reports. If net handling is configured in your prebid setup, revenue appears net in Alke Analytics. Direct sales correspond to campaigns served directly from your adserver.

Does this work without user consent?

Ad reconciliation is performed only on page views that have given consent to Alke Analytics as a vendor. The consent-free audience measurement layer continues to operate on 100% of your traffic for content, engagement and technical metrics.

Can I access ad metrics through the API?

Yes. All ad metrics are available through the REST API and scheduled exports, with the same filters and dimensions as in the interface.

How long does setup take?

Typically a few hours of configuration on our side, with no engineering work required from yours.

Ready to see ad revenue in your analytics?

Start your free 7-day trial and reconcile ad performance with your content analytics across your properties — or schedule a demo with our team.

Start free trial — 7 days See all platform features Compare with other solutions