How it’s calculated
Built from
POST analytics variation.netRevenuePerVisitor.value
Known caveats
- Canonical scoped POST snapshot; do not sum across variations or dates.
- Rows published before currency retention may lack a currency code; the dashboard renders those amounts without a symbol.
Where this appears
- A/B Test Results widget
- Experiment OS evidence
Grain and identity
Grain and identity
experiment_snapshot; entity: variation; same-day fold: sum; additivity: non_additive.Join and identity keys
- sourceLineageId
- experienceId
- variationId
- snapshotDate
Filters and boundaries
Filters and boundaries
- Organization, store, connection lineage, experiment, and result scope are server-derived.
- Generic metric publication uses only the unfiltered scope; linked custom-event scopes remain in Experiment OS.
- Current variation metrics exclude the control variation unless the field describes the experiment as a whole.
Timezone, currency, and freshness
Timezone, currency, and freshness
Timezone. Result snapshots require a verified IANA Intelligems reporting timezone. Provider-local days are stored with their UTC bucket boundaries.Currency. Currency is supplied by the Intelligems result. Aloftly does not convert currencies.Freshness. Hourly scheduled capture while the experiment is relevant.
Version history
Version history