Introduction
How to deploy Centinel Analytica on your site and customize protection settings.
Before you begin
- Create your account in the Centinel Analytica dashboard.
- You'll need:
- your site key (public, used by the browser script)
- your secret key (server-only, used for
/validate)
How it works
Centinel has three parts:
- Server validation (required): your backend, or a platform integration, calls the validation API for each protected request and acts on the decision (
allow,block, orredirect). The validator issues the_centinelsession cookie, and your response sets it. - Policy rules: rules select bot detection and actions for matching requests. A new organisation's Default rule is in monitor mode, so nothing is blocked until you change it. See The Default rule.
- Browser script (optional): collects browser and network signals that server-side data alone cannot see, and mirrors the
_centinelcookie. Detection works without it, with a smaller signal set.
Next steps
Copy your keys from the dashboard. Review the default policy. Add and order path-specific rules where you need different behavior.
Go to: Dashboard and Policy Rules
Wire up validation: use a platform integration, or call /validate from your backend.
Go to: Platform integrations or Validation
Add the browser script for stronger detection on pages visitors load.
Go to: Scripts
New to the decisions and block reasons in the dashboard? The Glossary defines them.
Getting help
Contact support with:
- the URL you're protecting
- the
request_idfrom the/validateresponse, which is also in itsX-Request-IDheader - a sample
/validaterequest payload (redact secrets) - the decision you received and any
crawlermetadata (if enabled)