How do I prove a revenue number is true?

Open Conversions, click Verify on any row, and the evidence page lays out the full proof: the recorded value next to the Order ID in your store, the click that earned the credit, and the Raw event (immutable) exactly as Decisa received it.

Before you start

• A workspace with the Attribution module active and at least one conversion recorded (from a checkout webhook, a connected store, or the server API).
• The order ID from your store or payment platform, if you want to cross-check a specific sale.

Steps

1. Open Conversions

   Use Sidebar → Attribution → Conversions. The page is a "Live sales feed": a "Live" dot and an "Auto-refresh interval" selector ("Refresh off", "Every 5s", "Every 10s", "Every 30s", "Every 60s") let you watch sales land in near-real time. Each row shows When the event happened, its type, the External ID (the order ID from your store), the Value, whether it is Attributed (a green Yes means Decisa found the click that earned it), and Pushed to platforms.

2. Filter to the event you care about

   Use the Type filter (defaults to All types) and the Attributed filter (defaults to Both), plus the date picker at the top right.

3. Click Verify

   Every row has a Verify button. It opens the evidence page, titled Verify against your store.

4. Match the number against your store

   The first card, The match, shows Decisa recorded (the value), the Order ID in your store, and the Source (which webhook or API sent it). If the original event was kept, it says Raw event stored — see below.

5. See why the revenue is credited

   Why it's attributed here shows the matched click — its URL, UTM tags, and capture time. Visitor journey lists every click from that visitor, oldest first, with the winning one marked Credited. Multi-touch credit shows how other attribution models would split the same revenue.

6. Inspect the raw event

   Raw event (immutable) shows the Provider, Mapper version, Received and Processed timestamps, and the Payload — the exact body your platform sent, stored verbatim and never editable. Expand Request headers (sensitive values redacted) if you need delivery details.

What happens next

• Nothing changes — the evidence page is read-only. You can paste the Order ID in your store into your store admin and confirm the value matches to the cent.
• Refunds arrive as their own conversion events with the type refund, tied to the original order. The ROAS report subtracts their value from revenue, so a refunded sale stops inflating your numbers.
• With auto-refresh on, new conversions appear at the top within seconds of the pixel or webhook firing — leave it on a small interval during a launch to confirm sales are landing.

Gotchas