wesaw
FRJoin the waiting list

THE CONVERSION RECEIPT

Every observed conversion gets a receipt.

An order, its event and the destination response, connected in one readable journey. Explore what a wesaw conversion receipt can and cannot prove.

wesawConversion receipt / 1042
Shopify → Meta

Order #1042

✓ Accepted
  1. ✓
    Shopify order recorded14:32:14
    Observed
  2. ✓
    Recorded consentRecorded state
    Granted
  3. ✓
    Event createdRecorded state
    Observed
  4. ✓
    Matching signals preparedRecorded state
    Available
  5. ✓
    Sent to MetaRecorded state
    Observed
  6. ✓
    Destination answered14:32:17
    Accepted
Final Meta mergeNot observable
Open the technical evidence
Event identifier
demo_purchase_1042
Destination response
HTTP 200 · events_received: 1
Delivery attempts
1
Ad attribution
Not observable
Product illustration · fictional data

Start from the order.

Find a Shopify order in the Ledger, then open its journey. The signed order webhook is separate from a browser observation. Missing evidence stays visible.

Read the delivery evidence.

Follow consent, available identity signals and server attempts. A recorded response tells you how the destination answered; a blocked attempt tells you why it was not sent.

Keep the boundary in view.

The browser emission attestation and server acceptance can be observed. Meta's final merge and event-level ad attribution cannot be verified by this receipt.

Request access