--- title: "Profiling explained | Darwinium" slug: "darwinium-profiling" description: "Understand browser and mobile profiling, its relationship to CDN request data, and how device and behavioral context contributes to Darwinium assessments." updated: 2026-11-11T04:02:14Z published: 2026-11-11T04:02:14Z canonical: "docs.darwinium.com/darwinium-profiling" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.darwinium.com/llms.txt > Use this file to discover all available pages before exploring further. # Profiling explained Browser and mobile profiling adds device and behavioral context to an interaction. A CDN integration can also observe connection and request data when no client profiling is present. For machine clients, follow [Monitor MCP and JSON-RPC traffic](/docs/monitor-mcp-jsonrpc-traffic). Missing browser profiling alone does not establish malicious automation. This article describes the nature, purpose and considerations of Darwinium's profiling. Suggested next pages: - Javascript profiling overview: [Javascript Profiling](/v1/docs/javascript-profiling) - Javascript profiling via CDN, see [Inserting Darwinium JS Profiling](/v1/docs/inserting-darwinium-js-profiling) - Javascript profiling via Tag, see [Tags Deployment](/v1/docs/tags-deployment). - Mobile SDK profiling, see [Mobile SDK Deployment](/v1/docs/mobile-sdk-deployment) ## Darwinium Profiling Overview Darwinium Profiling collects client side information about the device, behaviour and certain connection. It is performed on: - Javascript profiling via CDN: JavaScript inserted dynamically into GET request via an Edge worker (automatic) - Javascript profiling via Tag: JavaScript Tag added to page - Mobile Application: Native mobile SDK The data collected is essential input to rules and models, contributing to determining risk indicative of fraud or the recognition of a good user. Edge deploy Edge deployments are able to have a basic level of connection profiling without the Darwinium profiling ## Profiling Flow Proxy Step (CDN) Events ![Image](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image(233).png?sv=2026-02-06&spr=https&st=2026-11-19T12%3A45%3A22Z&se=2026-11-19T13%3A45%3A22Z&sr=b&sp=r&sig=y98%2B9XYyv8psS180j81XZfHO9K%2BunWZ6FpmSnBbktm0%3D) API Step Events ![Image](https://cdn.document360.io/db6f7316-640d-4099-b5a1-b01b4dbd17fc/Images/Documentation/image(234).png?sv=2026-02-06&spr=https&st=2026-11-19T12%3A45%3A22Z&se=2026-11-19T13%3A45%3A22Z&sr=b&sp=r&sig=rh29n52Bvv%2B3%2F4%2BV2DmnyAj7PdGKQMjLsBq%2FyD6Z8Q4%3D) 1. **Profiling Start** When a user loads a page, activity or view, the start() method is invoked to begin profiling: - JS CDN: Automatically triggered - JS Tag & Mobile SDK: Your application must explicitly call start() 1. **Profiling Collect** When the user submits a form or triggers an action, the collect() method is invoked to create a base64-encoded profileBlob. - JS CDN: Automatically triggered (controlled by an allow_list in profiling step configuration, Darwinium journey file) - JS Tag & Mobile SDK: Your application must call collect() within the submit handler 1. **Attach profileBlob to request** The profileBlob is included as header: `dwn-profiling` of the submit request - JS CDN: Automatically attached. Controlled by an allow_list in profiling step configuration, Darwinium journey file - JS Tag & Mobile SDK: Your application must add this header directly within the submit handler 1. **Darwinium Processing** Darwinium processes the profileBlob to resolve all collected profiling attributes. The handling differs based on **step type** - Proxy Step (CDN) Events: The Darwinium worker automatically removes the profileBlob from the request directly. This means it is not forwarded to your backend. - API Step Events: Your backend must receive the profileBlob it receives, and include as `dwn-profiling` header when making the Darwinium API call. ## Before you go live Check the site requirements Your site's Content Security Policy, CORS, Permissions-Policy and header size limits can stop profiling working, often without an obvious error. Check [Site requirements for JavaScript profiling](/v1/docs/javascript-profiling-site-policies) during setup and after changing them. The page is private: sign in through the Portal (see [Help & documentation access](/v1/docs/access-gated-docs-links)) or ask your Darwinium contact.