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.
Server-side
Runs in your application, so it sees API traffic as well as page views.
Next.js
App Router or Pages Router: edge or in-process middleware.
Express
Node.js / Express: in-process middleware with session tracking.
.NET
ASP.NET Core and .NET Framework.
Java
Servlet containers and the JDK HttpServer, on JDK 21 or later.
No-code and hosted platforms
Install through a tag manager or an app listing, with no server changes.
Next.js + Google Tag Manager
Pixel install plus user identification via GTM.
Shopify
Shopify stores, via the OAuth-connected Checkpoint app.
Related
- 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.