Data definitions and states

What you need

The intended report’s app, date window, cohort and currency. Definitions differ between general analytics and affiliate ledger reports.

Steps

1. Inspect the source coverage and window before treating a count or zero as complete history.
2. For general analytics use the metric boundaries below; for affiliate reports trace collections, contracts, corrections and original currency.
3. For operations read the state plus its evidence, not the badge alone. Drill into the record’s history when a transition is unexpected.
4. Preserve unknown/stale status when no evidence supports a stronger conclusion.

Expected result

A metric/state interpreted according to its actual source and calculation. Neither a browser observation nor an owner payment report becomes an independent merchant/receipt fact.

Analytics definitions

MRR and its movements describe observed subscriptions, not bank deposits. Estimated ARR, ARPU and LTV use the analytics calculation and are not exact lifetime cash.

Logo churn counts opening paid shops that lose their last subscription through cancellation/uninstall once in the month; freezes are excluded from that churned-shop component. Revenue loss/GRR/NRR calculations include the implemented freeze movements. Retention includes revenue retention, install cohorts and a funnel; use the returned definition with the result.

The funnel uses available installed/ever-subscribed/current-subscribed history and median first conversion timing. Trial reporting includes trackingSince and observed counts; missing older tracking is not zero historical trials.

Affiliate financial definitions

Eligible collections are evaluated under each referral’s saved contract, including rate/basis/collection types/duration/hold. Refunds/corrections produce signed ledger adjustments; bonus rewards are distinguishable. Amounts remain per currency with amountMinor decimal strings; settlement precision depends on currency. Never assume every currency has two decimals.

Partner-quality Collections less referral commission compares net collections with accrued referral commission, not full profit. Unallocated bonuses and unsupported optional usage must retain their stated reporting boundary.

Source states

Identification/browser/backend observation states describe receipt recency. Shopify history and collection/export continuity are separate checks. history_unverified, incomplete, stale and coverage_gap require review before claiming a complete window. Unknown conditions remain unknown; a negation cannot turn missing evidence into a verified fact.

Program and referral states

Programs: draft, active, paused, archived.

Memberships: provisioned, pending, approved, rejected, suspended, archived.

Referrals: requested, accepted, rejected, review, disputed, reassigned.

Commissions: pending, payable, review. Allocation/payment facts are tracked independently from these earning states.

Payment states

Payouts can be requested, approved, awaiting_payment, awaiting_confirmation, partially_reported, partially_confirmed, partially_reconciled, confirmed_paid, admin_reconciled, disputed, resolved, cancelled or rejected.

Individual reports/confirmations may be awaiting confirmation, confirmed received, disputed, void or administratively reconciled. A confirmed partial amount does not confirm an entire payout. An administrative resolution is distinguishable from partner-reported receipt.

See Owner manual payouts and Partner payments.

Troubleshooting

If the app, period or currency differs, compare the underlying records first. See Troubleshooting.

Minor-unit examples

Money objects contain amountMinor and currency; they do not promise a precision field. The supported settlement scale determines the decimal amount: