AlloyAttribution
Closed-loop sales attribution · SAMPLE DATA

A media buy you have to believe in, turned into a performance line item with a receipt.

These are verified enthusiasts. Here is the interaction, here is the VIN, here is the invoice. Everything below is running live on seeded demo data — click any step to walk the real system.

Influenced sales
2
Attributed value
$1,000.00
Est. influenced LTV
$80,000.00
Members
10
Events
1
Codes issued
7

The loop

1
Interaction
activity
2
Rebate code
issued
3
Proof of sale
submitted
4
Validation
validated
5
Ledger
attribution
6
OEM invoice
settled

Every stage is an immutable record with the actor and timestamp on each transition — the audit trail is the product, not a feature of it (N1).

Walk the loop

Capture an attendee at an event

A QR at a live drive or cars-and-coffee. Consent-gated email capture that counts as a qualifying interaction (R3).

Open →

A member qualifies and generates a code

The eligibility engine checks their activity against the campaign, then issues a rebate code bound to that decision (R2/R4).

Featured: Dana Whitfield — qualified, no code yet · click Issue
Open →

The buyer redeems with proof of sale

A public, no-login page: VIN + bill of sale. Under two minutes, no dealer involvement (R5).

Try code RAV4-RORY-1A9F
Open →

Alloy validates the sale

NHTSA decodes the VIN, duplicate and anomaly checks run, and a human approves — writing the immutable ledger (R6).

Open →

The attribution ledger becomes a report

Influenced sales, cost per sale, and lifetime-value framing — the receipt an agency can paste into their own reporting (R7).

Open →

Alloy invoices the OEM

Validated sales bill the OEM per the commission model, with a dispute path that hands back the evidence bundle (R8).

Open →

What the OEM sees

A read-only portal — their own influenced sales, each traceable to a VIN and an interaction (R10.4).

Open →

Demo mode — figures run on seeded sample data (N6). Reset anytime by re-running supabase/seed.sql. Developer index →