BrowsersSection titled Browsers
The Contentsquare Tracking Tag is designed to work on these web browsers:
|Chrome for Android||Latest version|
|Android Browser||Latest version|
|iOS Safari||Latest version|
|Microsoft Edge||Latest version|
|In-app browsers and WebViews||-||The tracking is working as long as the app doesn’t restrict required browser APIs, delete or prevent cookies setup and blocks local storage. The Tracking Tag behavior has been validated (pageviews and events tracking, session data collection) on the following in-app browsers, on both iOS and Android: Facebook, Facebook Messenger, Twitter, Instagram, LinkedIn, Slack, Snapchat, Pinterest, WeChat.|
FrameworksSection titled Frameworks
Salesforce APEX Lightning (not supported)Section titled Salesforce APEX Lightning (not supported)
Due to limits on CSP management, there is a high chance of the Tracking Tag not being able to work. Restrictions on window functions preventing to use Tag commands.
ProtocolsSection titled Protocols
The tag works on HTTP and HTTPS.
IframesSection titled Iframes
Contentsquare supports iFrames, including for Zoning and Session Replay.
ImplementationSection titled Implementation
Add the tag to the topmost window and inside each iframe down to and including the one(s) you want to track. Use the same Tag ID.
Your Contentsquare team enables the
iFrameTrackingtag setting to support iFrame tracking. When the flag is enabled, the tag inside the iFrames is not sending any natural pageview.
For Single Page Applications, trigger an artificial pageview inside the iFrame with a condition to execute only in this context to send a pageview.
Session Replay and iframesSection titled Session Replay and iframes
12.0.0 and later, tracking of first and third-party iFrames in Session Replay is fully supported, and activated on demand by Contentsquare.
Web components and Shadow DOM (not fully supported)Section titled Web components and Shadow DOM (not fully supported)
The tracking Tag has 2 separate events trackers, Shadow DOM support is not the same on both streams:
- Session Replay: full support. Each shadow element has a proper listener attached to it and the Tracking Tag doesn’t miss any event.
changeevents are not supported as shadow element children live outside the DOM tree. This is a “by design” limitation factoring in scalability constraints.
HTML Canvas and WebGL (not fully supported)Section titled HTML Canvas and WebGL (not fully supported)
The Tag collects mouse events by attaching them to the canvas but there is no possibility to locate them within the canvas.
Google AMP - Accelerated Mobile Pages (not supported)Section titled Google AMP - Accelerated Mobile Pages (not supported)
Contentsquare doesn’t provide tracking capabilities for AMP yet.
Offline browsing (not supported)Section titled Offline browsing (not supported)
The Tracking tag doesn’t verify if data was received by the server before deleting it locally. All events would be deleted at request sending attempt.
Tracking tag behaviorSection titled Tracking tag behavior
The tag only reads except for the following:
- Adding a
headto call the library;
- Adding a property
__contentsquare_identifierto every element (when the Session Replay is on);
- Overwriting the native function
CSSStyleSheet.prototype.insertRule(when the Session Replay is on).