Skip to content
DocsDashboard

Content and mediaAvailable with Expose

Know how much of your ad revenue came from people.

Crawlers, scrapers and AI agents read your pages and load your ads. Label every pageview, so you know the revenue advertisers may question and what your audience really is.

For publishers and media sites earning from display advertising.

Install ExposeSee how it works

Where $80,000 of ad revenue came from

  1. PageviewsPageviews: 10M
  2. Ad revenueAd revenue: $80,000
  3. Automated pageviewsAutomated pageviews: 1.4M
  4. Revenue at risk of clawbackRevenue at risk of clawback: $11,200

Human 86%Agent 2%Bot 10%Unknown 2%

Illustrative example 10M pageviews at an $8 RPM; 14% automated. Hypothetical.

Where money is affected

Automated pageviews earn revenue that may not hold.

Ads on automated pageviews can still pay out, until an advertiser or exchange audits the traffic and claws it back or lowers your rates.

Some automation is welcome, like search crawlers and agents reading for a person. Knowing which is which lets you report an audience you can defend.

The real picture

Your audience, two ways.

Pageviews from peoplePageviews from people: 8.6M−14%
Revenue from peopleRevenue from people: $68,800−14%
Revenue at riskRevenue at risk: $11,200

Illustrative example Hypothetical figures; your own numbers will differ.

Your numbers

What it could mean for you.

Replace the example with your own figures.

Revenue at risk
$11,200
Ad revenue
$80,000
Pageviews from people
8.6M

Revenue = pageviews ÷ 1,000 × RPM. At risk = revenue × share automated.

Illustrative example Your numbers, not a promise. Savings depend on the decisions you make with the evidence.

An example decision

One pageview, labelled.

Illustrative example
Page
/news/rate-decision
Session
bot · scraper
Ad slots loaded
3
Analytics label
bot

The pageview is still served. Your reports now show it as automated.

How it fits

From evidence to a decision.

  1. 01

    Install the script

    Paste the snippet or use the CLI.

  2. 02

    Pick the profile

    data-profile="content" for publishing sites.

  3. 03

    Label analytics

    GA4 and your tools receive the label.

  4. 04

    Report in HQ

    See people, bots and agents per section.

What your team can do

Act on it, your way.

Before you start.

Are all crawlers bad?

No. Legitimate crawlers can still be excluded from billable ad counts, which is why they are labelled, not blocked.

Will this change my ad revenue?

Not by itself. It shows where revenue comes from; what you do with it is your call.

Does it see impressions inside ad iframes?

No. It labels the pageview on your site. Ad-platform measurement is a separate integration.

What about sessions you cannot classify?

They stay unknown, and are not counted as bots.

Set up for Content and media

Readers, crawlers and the agents reading for them.

Count real readership, and see which AI agents read your pages on someone’s behalf.

How profiles work
Default policydata-profile="content"
Every actionTag only

Everything else is tagged, never blocked, unless you say so.

What you get

Where the label goes

Other covers

Available with Expose

See the real picture.

Install Expose

Install guideAd traffic qualityAll use cases