1. Define the observation window
Record start and end timestamps, timezone, attribution window, order statuses, currencies, refunds, cancellations, and whether reporting uses order time, click time, or platform conversion time.
2. Identify eligible signals
Discount codes may associate an order without a click. Tracked links and UTMs depend on identifier persistence and matching. Affiliate records depend on platform eligibility and rules. Post-level association depends on available platform data. A signal is included only when its source and matching rule are known.
3. Deduplicate
When more than one identifier is present, apply a documented precedence rule rather than adding every claim. Keep platform-reported and independently matched values distinguishable so teams can reconcile differences.
4. Report coverage and limitations
State which connections were active, which identifiers were configured, what data was unavailable, and whether totals were reconciled to the source system. Do not describe unattributed revenue as creator-free revenue.
5. Separate attribution from causation
An attributed order satisfies the selected matching rule. It does not prove the creator caused the order or reveal every contributing touchpoint. Incrementality requires an experimental or counterfactual design beyond routine attribution reporting.
Recommended reconciliation checklist
Compare a fixed date range and timezone; align gross versus net revenue; align paid, fulfilled, refunded, and cancelled statuses; verify currencies; inspect duplicate identifiers; review window settings; and retain the query or export date.