AI Traffic counts say when they are partial

AI Traffic and Referrals counts in API v2 and MCP now say how complete they are, the same way the app does. A count from a window we only partly covered is a lower bound, shown in the app as 1,234+. A zero from a partly covered window is unmeasured, not 0.

New fields

Each status is measured, lower_bound or unmeasured.

• GET /projects/{projectId}/traffic/summary and devtune_get_traffic_summary: totalEventsStatus, botEventsStatus, referralEventsStatus, uniqueSessionsStatus, botSessionsStatus and referralSessionsStatus, beside each window total.
• GET /projects/{projectId}/traffic/referrals and devtune_get_ai_referrals: currentStatus and previousStatus on engines.items[].sessions, engines.items[].conversions, engines.totals.sessions, engines.totals.conversions, overview.metrics.humanReferralSessions and overview.metrics.humanConversions.

comparisonAvailable stays, and is true only when both statuses are measured. Conversion rates stay null unless both of their counts are measured.

Values that change

Fully covered windows return the same numbers as before.

• A zero from a partly covered window is now null, with status unmeasured. This applies to the six traffic summary totals when that count's coverage.coveredDays is below coverage.windowDays or coverage is null, and to the Referrals engine counts, engine totals and overview counts when their coverage flag for that window is false.
• Engine totals keep what was counted. engines.totals was null whenever any platform's count was missing. It is now the sum of the counts that were recorded, with status lower_bound, unless every platform is fully measured. It is null only when nothing was counted.

If your code treats 0 as "no traffic", check the status first: only a measured zero means none. The API migration guide lists what to change.