Status and scope
| Field | State |
|---|
| Contract status | Current master |
| Implementation status | Mixed across connector and ledger paths |
| Last source review | 2026-08-26 |
| Runtime verification | Required for health, completeness, and values |
| Owner | Not recorded in this public document |
This master consolidates connected-commerce attribution, historical Hyros plan/status, and attribution-remediation work. Current architecture/migrations are authoritative; dated probes are evidence only.
Data planes
| Plane | Responsibility |
|---|
| Commerce/CRM source | Orders, transactions, refunds, line items, customers |
marketing_sales | Normalized transaction and lifecycle facts |
marketing_crm_order_events | Event-grain order lineage |
marketing_attribution_events | Direct-attribution evidence and resolution state |
| Latest-state attribution views | Replacement/tombstone-safe reporting state |
| Paid-acquisition facts | Platform metrics and paid hierarchy |
Source and denominator rules
- Platform purchases, CRM orders, unique customers, initial transactions, upsells, and attributed purchases are distinct.
- Zipify native offer conversion requires offer views; order-based take rate is separate.
- Click IDs/UTMs support attribution but do not prove offer views, declines, or viewer-device counts.
- Direct-attribution connectors retain source identity and event grain.
- Empty source, unavailable credentials, and valid zero activity differ.
Identity, resolution, and latest state
Commerce/attribution facts use connector-specific stable identities. Latest-state views prevent retries, re-resolution, and tombstones from double-counting. Explicit client CRM configuration wins; incompatible active CRM sources are ambiguous and fail closed. UI configurability is not proof of production health.
Verification
- Pin client, connector, window, currency/timezone, and deployment.
- Reconcile source transactions to normalized identities.
- Verify classification/refunds without collapsing event types.
- Verify retry/re-resolution/tombstone behavior.
- Compare attributed and full-ledger metrics under their own denominators.
- Record unavailable coverage explicitly.
Provenance