Measure how much an event table changed after the first snapshot

A daily export is not necessarily a final daily total. This lab compares two snapshots of the same reporting date and quantifies their difference. It keeps arrival completeness separate from business growth so a backfilled event does not become a newly acquired player.

Define the calculation before using it

Freeze the event definition, date boundary and filters before taking the first snapshot. Re-run the same query at a later timestamp, keeping both counts and the extraction times. Compute the added count and its share of the later total. When the count falls instead, investigate deletion, deduplication or changed query logic rather than forcing a late-arrival explanation.

Work through the synthetic example

The synthetic early snapshot contains 900 events and the later snapshot contains 1,000. One hundred additional rows represent 10% of the later total, while growth relative to the first snapshot is 11.11%. These denominators answer different questions. The lab names both rather than calling either number a universal late-event rate.

Use the artifact and preserve its assumptions

Open the editable calculator to change the inputs and inspect the sensitivity view. The CSV records synthetic inputs and expected outputs; the JSON fixture keeps the equations available for reproduction. These calculations have been checked against the stated example. No measured campaign data is included.

The sensitivity rows vary only later by 20% below and above the entered value. They are scenarios, not confidence limits or a forecast distribution. A row outside the model’s constraints is labelled rather than turned into a plausible-looking result. Save the chosen inputs with the decision so another reader can distinguish a changed assumption from a changed formula.

Evidence and limits

Google documents that daily export tables can be updated with late events for up to three days after the event date. That provider-specific rule motivates snapshot comparison; it is not a universal deadline for every analytics system. See Google Analytics BigQuery Export schema, especially “event_date, event_timestamp, event_value_in_usd and event_params fields”.

Two snapshots do not prove final completeness. Query changes, duplicate repair and deletions can also move a total; preserve query version and extraction time with any real evidence.

Background: UA metrics explained: CPI, ROAS, LTV and payback and Reading an MMP dashboard without fooling yourself. These existing articles provide context; the present calculation does not verify every archived claim.