Missing Telegram Ads statistics: a gap is not zero

A blank interval is not evidence that an ad spent nothing. It can mean that statistics are unavailable. Adtally keeps that distinction visible: unknown totals appear as “—”, gaps are reported and failed requests are not replaced with demo data.

Distinguish three situations

1. A measured zero: the returned interval contains a counter equal to zero.
2. A missing interval: the expected statistics do not contain a complete observation for that interval.
3. A failed request: the ad’s statistics could not be loaded at all.

These situations need different responses. Zero can be analysed as data. A gap needs a completeness check. A failed request needs a retry or an access check before you can interpret the ad.

Why the total can become unknown

Suppose a three-day report has 10 EUR for day one, no observation for day two and 20 EUR for day three. Thirty EUR is the sum of known observations, not a verified total for all three days. Reporting it as complete would understate any spend hidden in the gap.

The same problem affects actions and ratios. A CPA calculation cannot become trustworthy merely because the missing value was replaced with zero. An unknown field should remain unknown until the source gives enough data.

Keep comparison samples equal

If an ad fails to load, the dashboard names it and excludes it from both compared periods. Check the warning and the remaining sample before saying that account performance improved. A comparison of 12 loaded ads with 13 ads in another period would combine a sample change with a performance change.

The period comparison guide covers equal lengths and UTC boundaries. Save the same filters when you export the surviving sample.

Separate today from a missing day

Today’s numbers can be present and still incomplete because the UTC day is not over. Exclude today to read complete-day trends. Hourly or five-minute detail is limited to periods of up to three days; more detail does not repair missing observations.

A practical check before acting

Check the account, range, detail level and warning. Refresh after a temporary API error; if the session has expired, reconnect using the connection guide. Never paste a token into an exported report or a support message.

Deleted ads are another source of disagreement: current per-ad statistics may omit them. Use the monthly report to reconcile a calendar month instead of interpreting the difference as a calculation bug. Only then return to recommendations.