Integrate Darwinium with your CDN to observe and act on requests across your website and API endpoints. This is our recommended starting point when your traffic uses a supported CDN.
Coverage can be extended through journey and route configuration, helping you add more touch points without a separate application integration for each one. Start with Edge architecture to understand the request flow and deployment components.
Choose your provider
Each provider guide describes its prerequisites and setup. Confirm the domains, routes, and environment you intend to cover before deploying.
Configure the journey and profiling
Use the Journey Recorder to discover website interactions by browsing, or Create a journey manually. Then use Create & configure steps to define the interactions to process. For browser profiling, see Insert JavaScript profiling at the edge.
If you already run workers or multiple proxies, review Existing workers & multi-proxy deployments. Check the CDN deployment FAQ for additional guidance.
The CDN deployment connects your traffic to the configuration; the journey defines which interactions to process and which data to extract. Use Marketplace packages for reusable profiling and service integrations. A saved journey must still be reviewed, built and deployed before its changes affect traffic.
Validate and extend
Follow Deployment confirmation, then inspect your test interactions in Investigations. Confirm coverage of the intended routes before expanding it.
For ongoing operation, use Deploy & maintain. To add native mobile profiling or a separate API integration, return to Install & collect.