Profiling explained

Prev Next

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. Missing browser profiling alone does not establish malicious automation.

This article describes the nature, purpose and considerations of Darwinium's profiling. Suggested next pages:

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

API Step Events
Image

  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 during setup and after changing them. The page is private: sign in through the Portal (see Help & documentation access) or ask your Darwinium contact.