Why reporting is daily, not real-time.

Open the Skrypte dashboard and you can view a site's numbers over the last 7 days, 30 days, 90 days, or all time since it joined the network. What you won't find is a live counter ticking upward as impressions come in. That's on purpose.

What happens between an impression and a number

When an ad is served, the event doesn't land directly in the number you see. It's written to a queue first, then processed and checked, for viewability and for traffic quality, before it's aggregated into the day's totals. That processing step is what lets us filter out impressions that were never actually visible or that came from clearly automated traffic, before they ever count toward your numbers.

A live, second-by-second counter would either have to skip that check, which means showing you numbers before they're verified, or constantly revise itself downward as bad traffic gets filtered out after the fact. Neither is a number you can trust while you're looking at it.

Four windows, chosen for what they're used for

7 days is short enough to catch a sudden drop or spike. 30 days, the default view, is long enough to see a trend without last week's noise dominating it. 90 days smooths out weekly and monthly patterns. All time gives you the full history of a site since it was approved. We picked these four because they map to the actual questions publishers ask: "did something just break," "is this growing," "what does a normal quarter look like." That's more useful than an open-ended date picker that mostly gets used to answer the same handful of questions anyway.

Daily, not hourly

Every one of those windows is built from numbers aggregated once per day. We don't currently offer an hourly breakdown. For most publishers, day-level data is enough to answer "is this working," and it's a simpler, more stable number to build a business around than a feed that's still being corrected as the day goes on.