Debug ContentSquare in Chrome DevTools

What ContentSquare traffic looks like

ContentSquare splits a tag load, light analytics beacons, and an optional session-replay module across its contentsquare.net hosts.

Endpoint pattern

Tag from c.contentsquare.net (commonly a path like /uxa/<tagId>.js); analytics collection goes to t.contentsquare.net: pageviews, interaction batches, and replay traffic all hit the same collection host

Transport

Mostly compact GET beacons with numeric, coded query strings: no readable event-name parameters. The session-replay module loads as an additional script and produces heavier, more frequent recording payloads; a site can run analytics without replay

Key parameters

pid project ID · page and session numbers · screen dimensions · encoded interaction data

Cookies

_cs_id visitor ID with creation timestamp · _cs_s page count and session state. Session-continuity questions are answered in the cookies, not the URL

Debugging ContentSquare with Event Watcher

• No dedicated parser: the extension names the platform from its hostnames, applies the Session Replay category badge, and shows parsed query parameters plus the Cookies section per request.
• The useful signals are structural: does the tag load on the pages it should, and do t.contentsquare.net beacons follow?
• The heavier replay-module traffic (or its absence) confirms recording versus analytics-only mode.
• Grouping by Endpoint splits the tag host from the collection host; grouping by Cookie surfaces the _cs_id/_cs_s identity picture.

ContentSquare and consent

The extension checks ContentSquare against analytics consent. It is common on European enterprise sites where CNIL-style rules apply, and supports an opt-in deployment where the tag loads but collection waits for consent.

The pattern to verify is therefore not "is the script present" but when t.contentsquare.net beacons started and when _cs_* cookies were written. Beacons before the CMP resolves are marked pre-consent and totaled by the violations counter.

If the replay module is in play, apply the stricter session-replay standard: pre-consent recording payloads mean user behavior was captured without permission, a materially worse finding than an early pageview.

Common debugging scenarios

• Data missing for a page or journey. Confirm the c.contentsquare.net tag request fires there and that collection beacons follow. A tag present without beacons suggests consent gating or sampling.
• Replay expected but not recording. Look for the replay module's script load and its heavier payloads; analytics-only beacons alone mean the recording module never armed.
• Sessions splitting. Inspect _cs_id and _cs_s in the Cookies section across pages. A missing or rotating visitor cookie breaks journey stitching.
• Collection before consent. Check the consent state on the first t.contentsquare.net event; opt-in configurations should show zero beacons pre-banner.
• Who deployed the tag? The Script Tree view attributes the loader to site code, tag manager, or third party.