Constructor collects a limited set of browser and device information to tell automated browser sessions apart from real users. Automated sessions include AI agents that browse sites like real users, as well as testing tools. Identifying them helps keep the behavioral data that powers Constructor's learning algorithms and reporting accurate.

What information is collected?

Constructor's JavaScript beacon sends the following information in a client_environment tracking event:

• Whether the browser reports that it is controlled by automation software
• Whether common automation tools, such as Playwright, Selenium, or Cypress, have left markers on the page
• Time zone
• Screen size and color depth
• Browser window size and pixel density
• Number of processor cores
• Approximate device memory, when the browser makes it available
• Graphics card vendor and model, when the browser makes it available

Like other behavioral tracking events, the event also includes the random, anonymized browser ID, the session number, the referring URL, and, optionally, the obfuscated user identifier passed by the customer. For the full list of data collected by the Constructor platform, see What behavioral data does Constructor collect, and how is it used?.

This information describes the browser and the device. It does not include page content, text typed by users, or contact information.

How is the information used?

Constructor uses this information to identify sessions that are likely automated, so that their activity can be measured separately from the activity of real users.

Constructor does not combine this information into a fingerprint and does not use it to identify or track users across sessions.

When is the information sent?

The client_environment event is sent at most once per browser session. Constructor's JavaScript beacon stores a record of the last session that sent the event in local storage, so that the event is not sent again during the same session. For more information, see What data does Constructor store in the browser?.

The event is not sent when behavioral tracking is deactivated. For more information, see Deactivate tracking.