Protect adds exactly one verdict tag to every new order. If an order is processed again, earlier verdict tags are removed first, so the tag you see is always the current one.
The tags
| Tag | Added when |
|---|---|
sd-clean |
The order carries a valid token from an allowed visit, the visit’s behaviour did not look automated, the Suspect Score did not flag it, and the token was not reused from another order. |
sd-suspicious |
Anything else: no token, an invalid token, automated behaviour, a flagged Suspect Score, or a reused token. |
sd-blocked-bypass |
The order carries a valid token from a visit that was blocked. This should not happen; the tag exists so you can audit it if it does. |
protect-risk |
Added alongside a non-clean tag when Checkout origin protection is in risk mode. |
The Suspect Score affects tagging only when Apply Suspect Score to order tagging is on. See Risk weights.
Channels without a token
Orders from Point of Sale, the Shop app, draft orders, a headless storefront and Buy with Prime never pass through your theme, so they carry no token. By default they are tagged sd-suspicious.
Enable each channel you use under Storefront → Settings → Coverage. An order from an enabled channel is then tagged sd-clean unless something else flags it. Treat the tag as advisory on these channels: Protect did not see the shopper.
Use the tags
- Filter reports. Build a Shopify segment on
tag:sd-cleanto leave bot-attributed orders out of a report. - Automate. Shopify Flow and other automation can act on
protect-riskorsd-suspicious. - Reconcile. On the Protect plan, Export reconciliation lists every order that came from a scored session with its verdict. See Exports.
The customer metafield
Protect also writes the verdict to the customer as the app metafield protect.verdict, a JSON value with verdict, confidence and suspect_score. It is readable in the admin and hidden from the storefront.
What tagging does not do
- It does not cancel, hold or refund an order. Use Flow or your own process for that.
- It does not tag orders placed before Protect was enabled.