Orders & attribution
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
Orders
Section titled “Orders”The Orders tab lists recent purchases with the order number, time, total and each platform’s result:
| Status | Meaning |
|---|---|
| Sent | Delivered |
| Test event | A test code is set, so it went to the platform’s test tool |
| Retrying | Temporarily failed and backing off for a retry |
| Failed | The platform refused and it won’t be retried |
| Not verified | The purchase failed verification: stored, not sent |
| No consent | The visitor didn’t allow marketing |
| Not enough data | Too little matching information to send |
Choose Inspect on an order to see every event that led to it, which identifiers and consent it carried, and each delivery’s status with the platform’s trace id. You can also search by order number or checkout token.
Why a purchase shows “Not verified”
Section titled “Why a purchase shows “Not verified””A public key means anyone could forge a “purchase completed” event. Hydrogen stores send only verified purchases by default: your storefront server asks Gosper to sign a proof against the real cart, writes it into the cart’s attributes, and the checkout pixel brings it back. Common reasons:
| Reason | What it means |
|---|---|
| The cart was not registered by the storefront | No proof in the checkout attributes — usually server.ts isn’t wired up, or the Storefront environment variables are missing |
| The cart proof did not match | The proof is invalid |
| Shopify did not confirm the cart | Gosper couldn’t read that cart |
| The currency differs from the cart’s | Currency mismatch |
| The amount is far above the cart’s total | The total is implausible for that cart |
| The cart was already purchased under another order | That cart already belongs to a different order |
Theme stores can’t register carts, so verification is off for them by default. You can toggle it under Settings (Send only verified purchases).
Health
Section titled “Health”The Health tab shows the last 7 days per platform: sent, failed, not verified and no consent, plus the last success and last error, how many batches are waiting to retry, and any alerts worth attention.
Failures retry on their own, backing off from one minute to a day. A 4xx from the platform (other than rate limiting) is not retried.
Live events
Section titled “Live events”Live events shows the last 100 events: whether they came from the storefront or the checkout pixel, the event type, the value, which platforms the browser was told to call, and the visitor’s consent. Use it right after installing to confirm events arrive.
Attribution
Section titled “Attribution”Attribution groups orders and revenue by channel, source and campaign, over the last 7, 30 or 90 days, with a model (last touch, first touch, linear) and a lookback window. With a Meta ad account configured it also shows spend, attributed revenue and ROAS.