Requests and selected ads
A recorded request represents a delivery request stored for eligible reporting inventory. A selected ad means the request found a creative that matched the delivery rules. Publisher reports can include requests without a selected ad; advertiser reporting is scoped to deliveries associated with that advertiser.
A gap between requests and selected ads can reflect a lack of eligible creative. Check placement dimensions, review and activation states, and audience restrictions before drawing conclusions. These counts describe the delivery workflow; they are not an estimate of unique people or guaranteed reach.
Rendered impressions and clicks
A rendered impression is recorded when the ad's impression event reaches KaloAds with a valid delivery token. It is not verified viewability: the event does not establish that a person saw the creative or that it was visible on screen for a particular duration.
A click is recorded through the KaloAds click endpoint before redirecting to the reviewed destination. One impression and one click are counted per delivery. Signed, expiring tokens and deduplication help limit replay, but they do not establish that traffic is human or billable.
Click-through rate in context
Click-through rate, or CTR, is clicks divided by rendered impressions, multiplied by 100. For example, 5 clicks from 200 rendered impressions gives a CTR of 2.5%. This is an illustrative calculation, not a KaloAds performance claim.
When there are no impressions, there is no meaningful denominator for CTR. Read counts alongside the percentage, particularly for small samples. CTR does not measure revenue, a completed purchase, or the quality of a visit; those are different questions.
Check the period and the measurement limits
Reports show the last 30 days, including the current UTC day, with the time the report was generated. Daily delivery counts use delivery dates, while impression and click counts use event dates. An event arriving after midnight can therefore appear on the next day.
Advertisers can also configure server-side conversion goals and inspect deduplicated events in Conversions. An event needs a valid clicked delivery token for click attribution; without it, the event is unattributed. Conversion events do not create person-level audience profiles. Preview reports do not show advertising charges, publisher earnings, or billable results.