Agent Intelligence can be deployed using any method that loads and initializes the Platform SDK so it can capture browser and action signals.
The diagram below illustrates the recommended CDN integration flow, where an edge worker injects the SDK before the page reaches the browser. Once the page loads, the SDK captures telemetry in the background and sends those signals to Mosaic for backend processing. Mosaic then correlates the activity, analyzes agentic patterns, and surfaces the processed results in Agent Intelligence.
The available approaches fall into two categories:
CDN integration: deliver or inject the Platform SDK through your CDN or edge compute platform, such as Cloudflare Workers. The SDK loads alongside your existing pages without embedding it in your application code. You can also add it through tagging with a tag manager, such as Google Tag Manager (GTM).
Client-side SDK-only integration: embed the Platform SDK directly in your application code for full control over initialization and performance.
CDN/edge integration is the recommended approach because it requires little to no changes to your application code. To explore which option best fits your architecture, contact your Transmit Security technical team.
Use the following comparison to choose between client-side SDK-only and CDN integration:
| Criterion | Client-side SDK | CDN |
|---|---|---|
| Time to first signal | Fast to integrate, live once the SDK is added to the application | Fastest—zero code change, SDK is injected automatically at the edge; live the moment CDN routing is configured |
| Engineering lift to start | Low-moderate | Minimal—no engineering sprint, code review, or release cycle required to get started |
| Security posture | Telemetry is collected in the browser; the SDK and its configuration are exposed client-side | Same client-exposed model as client-side; the SDK is injected at the edge, but telemetry is still collected in the browser |
| Latency | Low latency, minimal client impact | Lowest—injected inline at the delivery layer, no added round trip |
Use one of the following guides to implement the approach that best fits your stack: