Once the setup checks pass, Protect starts recording. Nothing is blocked at checkout until you change a rule, so the first day is for looking.
What fills in
| Where | What you see |
|---|---|
| Dashboard | Total sessions, Allowed, Blocked, Blocked checkouts and the traffic classes for the selected range. |
| Storefront → Sessions | One row per storefront visit that was scored, whatever the verdict. |
| Orders in Shopify | A verdict tag on every new order: sd-clean, sd-suspicious or sd-blocked-bypass. |
| Brand → Incidents | Verified copies of your products, once the first brand scan finishes. |
Orders placed before you installed are not tagged retroactively.
Check these first
- Place a test order from a normal browser. It should be tagged
sd-clean. If it is taggedsd-suspicious, the checkout block or the embed is probably missing; recheck Setup Storefront in the setup guide. - Open Storefront → Sessions and confirm your own visit is listed as allowed.
- If you sell through POS, the Shop app, draft orders, a headless storefront or Buy with Prime, enable those channels under Storefront → Settings → Coverage. Orders from those channels carry no token, and without this setting they are tagged
sd-suspicious. See Order tags.
Then decide what to enforce
After a few days of data, review Storefront → Settings → Rules. A reasonable order is:
- Set Checkout origin protection to risk. Orders still go through, and non-clean ones gain the tag
protect-risk. - Check the tagged orders against what you know about them.
- Switch to block when the tags match your judgement.
Rules lists every setting and its default.