What counts as an ad impression in a terminal
How Tokenbreak decides an ad in Claude Code was seen: one per turn, a continuous second on screen, server-issued tokens, daily caps. And what it can't know.
- ad impression
- viewability
- ad measurement
- tokenbreak
- advertise to developers
Advertisers pay Tokenbreak per impression, and developers earn per impression, so the definition of one matters more than anything else we publish. This post explains how we arrived at it and what it can and can't tell you. The definition itself, word for word, with an example of every request the mod sends, is on the tracking page.
What the web counts
On a website, an ad server usually counts an impression when the ad is requested or starts to load, whether or not anyone could see it. The industry's answer to that is viewability: the Media Rating Council's display standard counts an ad as viewable when at least half its pixels are on screen for one continuous second. Video needs two seconds.
That standard exists because a web page is tall, ads sit below the fold, and a tab can load in the background. Half the pixels for a second is a compromise between "the ad loaded" and "someone looked at it".
Why a terminal is different
A terminal ad doesn't scroll into view by halves. The Prompt Banner is a single line drawn above the prompt box; it's either on screen or it isn't. The Theater pane is either open or closed. So "half the pixels" doesn't mean much here, and time on screen is what's left to measure.
The other difference is that the mod can't see you. It never reads your keystrokes, prompts or the conversation, by design. So the signal that a person is present is the one thing it does know: a turn started, because someone sent Claude a prompt.
The rules
An impression is one ad on screen during one Claude turn. It counts only when all of these hold:
- One per turn, per format. A turn starts when you send a prompt and ends when Claude finishes. Each turn can count at most one Prompt Banner and one Theater impression. If more than one ad of a format showed during a long turn, the one that stayed on screen longest is the one counted.
- On screen long enough. The banner must stay on screen for one continuous second, the same threshold as the web's display standard. Theater, the bigger and pricier slot, needs two. The mod measures the longest unbroken stretch and doesn't report anything shorter.
- A turn our server issued. When a turn starts, the mod asks our server for a signed turn token. A paid impression without one earns nothing and costs nothing. One device gets at most one turn every ten seconds, and one account at most 600 a day, which is more than a person sends.
- An ad we actually served. Each paid ad comes with a serve token for that account and device. An impression has to carry the matching one.
- Fresh. A report that reaches us more than 24 hours after the ad was shown doesn't count.
- Inside the daily caps. One developer is credited for at most 120 banner and 20 Theater impressions per UTC day. Past a cap, impressions are filtered: the developer isn't credited and the advertiser isn't charged.
When we aren't sure, we don't count it. We'd rather under-count than bill for a view that didn't happen.
Why it's built this way
One per turn ties impressions to something a person did. A banner that sits on screen through a five-minute refactor is still one impression, not three hundred. That keeps the price honest for advertisers and makes the number hard to inflate by leaving a terminal open.
The tokens mean the server, not the mod, decides what counts. The mod is open source and runs on someone else's machine, so anyone could change it to report whatever they like. A report that doesn't match a turn and an ad our server issued to that account and device is simply ignored. The server also checks the time on screen against when the turn began, so a report can't claim a minute on screen for a turn that started five seconds ago.
The caps put a ceiling on what any single account can earn or cost in a day. They're the backstop for anything the other rules miss.
The 30-day hold on developer earnings exists for the same reason: refunds and invalid traffic found later can be netted out before anyone is paid.
What it can't know
Some people switch windows while Claude works, and the mod can't tell. It doesn't detect window focus, and it has no way to see your eyes. So an impression means the ad was drawn on a screen, during a turn a person started, for long enough to read one line. It doesn't mean the person read it. The web's viewability standard has the same limit; it just doesn't say so as often.
Clicks
Clicks go through a short redirect on our site, which records the click per ad and sends the visitor on with UTM tags (utm_source=tokenbreak, the medium, campaign and format). There's no pixel and no cookie. Advertisers see two numbers: every click, and a filtered count without known bots, link previews, clicks less than a second after the ad was served, and repeat clicks from one network on the same day. Nobody pays per click.
Checking our work
You can read every request the mod sends on the tracking page, and the mod's source is on GitHub. If you're an advertiser deciding whether this is worth $25, our comparison with Carbon, EthicalAds and newsletters covers what you get and don't. The words used here, from turn token to fill rate, are in the glossary.