Skip to content

Troubleshooting

Fixes for the problems merchants meet most often.

Updated

Storefront and checkout

The dashboard shows blocked visits, but checkouts still go through

Blocking a checkout needs both of these:

  1. The cart validation rule is enabled (setup step 3).
  2. Checkout origin protection is set to block under Storefront → Settings → Rules.

With it set to none or risk, orders go through and are only tagged. Also confirm the checkout block is installed (setup step 2).

Real customers are being blocked

Add the customer’s IP address to IP whitelist under Rules → Blocklists & Whitelists. The whitelist overrides every other rule.

If many customers from one country or network are affected, check Geography and ASN blocklist. The Suspect Score never blocks anyone; it only changes order tags.

Orders from POS or the Shop app are tagged sd-suspicious

Those channels carry no verdict token. Enable them under Storefront → Settings → Coverage. See Order tags.

A setup check turned red

Reopen the step from the Dashboard setup guide. The embed is enabled per theme, so check it again after you publish a different theme.

I cannot see why a session was flagged

Storefront → Sessions shows Status, and Confidence and Suspect on the Protect plan. There is no per-session list of signals. To see how the signals combine for your traffic, use the preview under Storefront → Settings → Rules → Risk weights.

Checkout monitor checks keep ending incomplete

Open Storefront → Scans and read the reason shown on the check. If a selector no longer matches your theme, update the Journey.

Brand protection

Brand → Settings → Detection says Access needed

Protect lacks the read_products permission. Approve it from the prompt; the catalog import starts once it is granted.

No detections after the first scan

On the Free plan only 10 products are checked each month, so a copy elsewhere in the catalog can be missed. On the Protect plan, confirm that products are selected: with none selected, nothing is scanned. See Choose products to monitor.

A product cannot be selected for monitoring

Only active products with a usable primary image can be selected. Activate the product, or give it a primary image.

A finding is marked unverifiable

Protect could not load the page, or the platform blocked the request. It is not a clean result. Open the listing yourself; on Brand → Scans, use Verify now to try again.

I cannot confirm a case against a seller

The seller matches an entry in your authorized sellers. Remove the entry under Brand → Settings → Profile → Authorized sellers if it is wrong.

My approval disappeared

The evidence, your rights details or the notice template changed after you approved, which cancels the approval. Read the new notice and approve again.

A managed filing came back as owner action required

The platform accepts complaints only from the rights owner’s own account. Use the package and link on the detection to file there. You are not charged.

Notifications and API

A webhook delivery failed

Open the delivery under Brand → Notifications to see each attempt. Check that your endpoint is on a public HTTPS address, answers within ten seconds, and does not redirect. Then retry the delivery.

An API request returns unauthorized

Check that the credential has not expired or been revoked, that the path names the store the credential was issued for, and that the credential includes the scope the endpoint needs. A credential bound to an agency user stops working when that user’s grant is revoked.

Type to search…

↑↓ navigate↵ selectEsc close