Shown but not credited

A line can render without crediting you, and every reason is deliberate. Here they are in the order worth checking, each one an honest rule rather than a leak.

The checklist, in order

1. The threshold was not met. A credit requires 5 cumulative seconds of genuine visibility: window focused, agent actually thinking. Glance away to another app, or the agent stops on a permission prompt, and the clock pauses. The full rule is in What counts as an impression.
2. It was a house line. In a quiet market Awaitful serves its own line, which pays nothing and says so in its tooltip - see House ads and quiet markets.
3. It was a duplicate. Every event carries a unique identifier and the server drops replays, so a flaky network can never double-credit - which also means a re-sent event never shows up as a second earning.
4. A per-device earning cap was reached. Each device has hourly and daily earning caps as fraud protection. Over the cap, the ad still shows and the advertiser still pays, but the capped device does not earn - the platform keeps that share rather than crediting an implausible machine.
5. It was your own campaign. If you advertise and code on the same account, your own ads viewed by you move no money in either direction. No one may bill themselves - see The 70% split.
6. The device was revoked. Events that straggle in from a machine you revoked are not credited to anyone. Revoking stops future earning; it never touches earnings already booked - see Turning it off.

What is always credited

Everything that passes the rule, immediately, at your share of the charge - and you can watch it happen per impression in the dashboard's earnings page, broken down by surface. If a credit you expected is not explained by anything above, the panel's account view and the dashboard should agree with each other; when they do not, that is worth reporting from the feedback control at the bottom of this page.