Checkpoint Docs
Integrations

Integrations

Platform-specific guides for wiring Checkpoint into your framework, storefront, or analytics stack

Pick your platform

Every integration here installs the same detection engine — the difference is only where it runs and how you wire it in. Server-side integrations see every request, including the API calls agents make without ever rendering a page. The no-code options trade that coverage for a faster install.

These all attach Checkpoint to an existing stack. The standalone Marketing Pixel and Gateway work independently of any framework, and are compared alongside these in Choose Your Integration.

Not sure which pillar you need first? Detect identifies agents, Enforce blocks or challenges them, and Govern authorizes them against a delegation policy. Start with Detect.

Server-side

Runs in your application, so it sees API traffic as well as page views.

GuidePlatform
Next.jsApp Router or Pages Router — edge or in-process middleware
ExpressNode.js / Express — in-process middleware with session tracking
.NETASP.NET Core and .NET Framework

No-code and hosted platforms

Install through a tag manager or an app listing, with no server changes.

GuidePlatform
Next.js + Google Tag ManagerPixel install plus user identification via GTM
ShopifyShopify stores, via the OAuth-connected Checkpoint app
  • Choose Your Integration — compare every option, including the Pixel and Gateway.
  • Cookbooks — end-to-end, scenario-based walkthroughs with working code.
  • Middleware — shared config, response headers, and response shapes across Next.js, Express, and .NET.
  • API Reference — the REST surface behind every integration.