Glassbox
Glassbox records sessions and analyses the digital experience. Session replay needs the page’s DOM, so Glassbox runs in the browser: this integration is client-only. Glassbox publishes no server-side event ingestion API (its documentation is behind the customer login), and Signal delivers nothing to it server to server.
Signal owns the detector’s lifecycle: its SDK loader injects the Glassbox detector for your tenant only once analytics consent permits, and forwards identity when you call datafly.identify().
Status: needs a live test. The detector URL and the customer-session call (_cls.setCustomerSessionData) come from the Bennetts proof of concept and must be confirmed with Glassbox. The durable-ID bridge described for that proof of concept is not built yet: writing Signal’s first-party _dfid to a Glassbox custom attribute (so a Safari visitor is still recognised after ITP deletes Glassbox’s own _cls_v cookie), setting the detector’s report settings (data-clsconfig), cooperating with a detector a tag manager already loads, and reading _cls_v / _cls_s back into Signal (#1579).
Prerequisites
- A Glassbox account and your tenant slug: the path segment of your detector URL,
https://cdn.gbqofs.com/<tenant>/p/detector-dom.min.js. - Datafly.js deployed on the site with the client-SDK loader module.
- A consent signal reaching Signal (from your CMP or Signal’s consent API).
- The Glassbox detector not also loaded by a tag manager, or it will record every session twice.
Configure in Signal
| Field | Required | Description |
|---|---|---|
tenant | Yes | Your Glassbox tenant slug, substituted into the detector URL. |
- Add the Glassbox integration to the pipeline that serves the site and keep the Default preset.
- Enter your tenant and turn on Client-Side SDK.
- Confirm the consent category that gates the detector (analytics in most CMP configurations) and save.
Delivery
| Property | Value |
|---|---|
| Delivery mode | Client-side (SDK loader) |
| Events forwarded | None: Glassbox observes the page directly |
| Identity | On datafly.identify(), the user ID and the email trait go to the detector’s customer session data |
| Consent | Load gated on the integration’s consent category |
Personal data
The email reaches Glassbox from the visitor’s own browser, in plain text, as the detector’s customer session data, so your team can find a customer’s sessions. Nothing is sent from your servers. If your policy is not to share the email with Glassbox, remove email from the identify traits you pass to datafly.identify() on pages where Glassbox runs. See Personal data by integration.
Verify it’s working
- Load the site with analytics consent denied and confirm in DevTools (Network) that nothing is requested from
cdn.gbqofs.com. - Grant consent: the detector loads and a session appears in Glassbox.
- Call
datafly.identify()and confirm the session carries the user ID in Glassbox.