BotShield_Gate__c record, and your page or automation acts only on that verified row.
How it works
1
The guest verifies
The widget shows a human check: the person confirms with their passkey on their phone, by scanning a code or following a link. No login, no personal data. A gate always asks, so every check is a fresh confirmation.
2
The verification is pushed to your org
On success, BotShield pushes a
BotShield_Gate__c record into this org (keyed on the request ID) for every gate you selected under Pushing to Salesforce. Change Data Capture is enabled on the object, so Flows and LWCs can react the moment it lands.3
You act on the verified row
Your checkout or form completes only against that verified row — the booking, order, or record is created only when a real human is present.
Add the widget
1
Open Experience Builder
Edit your community page and drag the BotShield Verify (Human Verification) component onto the cart, checkout, or form page.
2
Set the site key
In the component properties, paste your Site Key (
pk_…, from Settings → Developer Tools → Site Keys in the BotShield Console) and set Scope to your gate’s key. The site key is publishable — it’s safe in the page. Result transport defaults to salesforce, which waits for the row BotShield pushes into the org.3
Allow the origin
Add your Experience Cloud site’s origin to the site key’s allowed origins in the Console. If the origin isn’t listed, verification requests are rejected. A production (
pk_live_) key’s origins must sit under a domain your organization has verified.The package ships the required CSP Trusted Sites for the BotShield CDN and QR endpoints, so the widget loads in both LWR and Aura communities without extra configuration.
Read the result
Each verification lands as aBotShield_Gate__c record with the outcome (never PII):
Watch verifications in the BotShield → Verifications tab, filtered by gate and status.
Commerce Cloud checkout
The same gate on a Composable Storefront / Storefront Next checkout using the BotShield SDK.
