Compatibility
Browsers
Section titled BrowsersThe Contentsquare Tracking Tag is designed to work on these web browsers:
Browser | Version | Issues/Warning |
---|---|---|
Chrome | Latest version | |
Chrome for Android | Latest version | |
Android Browser | Latest version | |
Firefox | Latest version | |
Safari | Latest version |
|
iOS Safari | Latest version |
|
Microsoft Edge | Latest version | |
Internet Explorer | 11 |
|
Opera | 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. |
Frameworks
Section titled FrameworksThe Contentsquare Tracking Tag is compatible with all JavaScript frameworks for single-page application, including Angular, React, Vue, Ember…
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.
Protocols
Section titled ProtocolsThe tag works on HTTP and HTTPS.
Websites overriding native JavaScript function and browser APIs (not supported)
Section titled Websites overriding native JavaScript function and browser APIs (not supported)The Contentsquare Tracking Tag uses common web browser APIs and native JavaScript API. Overriding any of these APIs can prevent the Tag from functioning normally.
Iframes
Section titled IframesContentsquare supports iFrames, including for Zoning and Session Replay.
Implementation
Section 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
iFrameTracking
tag 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 iframes
Section titled Session Replay and iframesIn version 12.0.0
and later, tracking of first and third-party iFrames in Session Replay is fully supported, and activated on demand by Contentsquare.
Custom elements and shadow DOM
Section titled Custom elements and shadow DOMThe tracking Tag has two separate event trackers: Session Replay and Analytics.
Both provide full support for custom elements and the shadow DOM.
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 behavior
Section titled Tracking tag behaviorThe tag only reads except for the following:
- Adding a
script
into thehead
to call the library; - Adding a property
__contentsquare_identifier
to every element (when the Session Replay is on); - Overwriting the native function
CSSStyleSheet.prototype.insertRule
(when the Session Replay is on).