Shopify
Working
Shopify is the commerce source: it tells wesaw that an order exists. Signed order webhooks, browser observations and destination responses meet in a conversion receipt. You can follow an observed purchase from its order record to the delivery outcome, with missing evidence shown explicitly.
What connects?
You authorise the Shopify app to read orders, install its Web Pixel and read customer events. The app registers the order webhook. You enable the wesaw app embed in the published theme to collect storefront observations. No theme source code needs to be pasted or edited.
The requested scopes are read_orders, write_pixels and read_customer_events. wesaw does not request permission to edit products or prices.
What does wesaw observe?
The order identifier, timestamp, value and currency, available matching signals and recorded consent state. Shopify webhook signatures are checked before an order is accepted. Browser evidence is kept separately from the server-side order record.
What does wesaw send?
Eligible conversions are prepared for Meta Conversions API using the connected destination. Server-side dispatch requires recorded consent to be granted. Missing consent, insufficient identity or an expired acceptance window can prevent dispatch; the receipt shows the recorded reason.
What can wesaw verify?
An observed order, the matching fields present, browser emission evidence when recorded, and destination delivery attempts and responses. A separate Shopify comparison can identify orders missing from ingestion over the measured period; an incomplete comparison stays unavailable.
What remains outside the receipt?
A successful destination response does not prove ad attribution or a browser/server merge inside Meta. A missing browser observation does not prove that no browser event was sent. wesaw keeps those limits visible instead of filling them with an estimate.
Last reviewed: