Data Layer
A data layer is a layer of your site that contains all of the data that gets generated when users engage with your site.
How does it relate to your Contentsquare project?
Your site's data layer provides a reliable place for the CS tag to collect data as its generated.
Contentsquare Tag (CS Tag)
The CS Tag is a code snippet implemented on your site pages that is used to collect data from your site's data layer. When the tag is loaded, Contentsquare will pick up most interactions happening on the page (e.g. mouseovers, clicks, hovers,...)
How does it relate to your Contentsquare project?
Our implementation team (with the help of your deployment manager) will install the CS Tag on your site to collect UX data to meet your analysis needs.
Read more about how to deploy our tag
Pageview
A pageview is tracked when a user visits a page on your site where the main CS tag has loaded.
How does it relate to your Contentsquare project?
You'll identify your site pages where you want pageviews tracked and our implementation team will help you install the tag to track them.
Single Page Application (SPA)
When your site interacts with the user by dynamically rewriting the current web page with new data from the web server, instead of by loading entire new pages.
How does it relate to your implementation?
You'll identify SPAs on your site and our implementation team will work with you to configure them for data collection using artificial pageviews (APV).
Artificial Pageview (APV)
An artificial pageview is when the CS tag is configured to track and send a 'pageview' event when no new page has actually been loaded into the user's browser.
Why set up an APV during implementation?
So you can track tab changes, pop-up opens, and iFrame views as pageviews.
Ex: Setup an APV for your site's 'Add-to-Cart' pop-up to accurately analyze your checkout funnel.
How does it relate to your Contentsquare project?
During implementation, you'll identify pop-ups and iFrames you want to track as unique 'pageviews' and our implementation team will configure them.
Personal Data Blocking
Personal data is any information that relates to an identifiable living individual (e.g. name, email address,...) masking that information helps to conceal it while you analyze your site.
How does it relate to your Contentsquare project?
Contentsquare will help you conceal personal user data. During implementation, you will browse each page tracked by the CS tag and identify and list every element displaying personal data.
Content Security Policy (CSP)
Your site(s) might have a CSP to help protect against cross-site scripting, clickjacking, and other code injection attacks caused by malicious content.
How does it relate to your Contentsquare project?
For our tracking tag to still work on your site(s), you need to add to your trusted sources of script execution, the sources used by the tracking tag. There is a minimal CSP configuration the CS tracking tag needs to function.
Learn the technical details here
Mapping
The CS tag collects data from your site’s pages. Mappings help you organize this data.
In other words, mappings are visual site maps that help you decide how to use the collected data according to your analysis needs.
How does it relate to your Contentsquare project?
A detailed implementation process will help you generate more enriched mappings to better analyze your site later.
Custom Variables (Cvars)
Key pairs found in your site's data layer that can be used to track information on a page, user, or session. Sent the moment the pageview is sent.
** You can provide up to 20 Cvars.
Ex: Use the Cvar 'page_type' to create a mapping of only your Product pages.
Use case: Create segments or enriched page grouping for mappings, where the URL would not be enough.
Dynamic Variables (Dvars)
Key-value pairs found in your site's data layer that can be used to track user traffic at a session-level. Sent at a later point, not when the pageview is sent.
** Up to 40 distinct Dvars per pageview
Ex: Use the Dvar 'NumberOfSearchResults: 34' to analyze users who had >20 results on page.
Use Case: Create segments to run A/B tests.
Custom Page Events
Single value tags found in your site's data layer that can collect information about user events at a session-level.
** Up to 40 distinct page events per pageview
Ex: Use the Page Event 'PageShowedSearchResults' to analyze a session where a page showed users' search results.
Use Case: View user behavior (interactions with specific elements etc.) in Session Replayor segment users by that same behavior.