Removing Contentsquare implementation
We are sorry to see you go.
Find below the list of elements to be removed.
Should anything be left behind after the removal process, be assured that your site data will not be collected anymore and your site’s performance won’t be impacted. We automatically stop data collection for all former clients, meaning that the code in our tags doesn’t get executed if your site still requests it.
List of elements to be removed
Section titled List of elements to be removedRemoving the main tag
Section titled Removing the main tagThis is a JavaScript code that makes a call to the Contentsquare library.
Unless it is self-hosted, in which case you should ask internally for the procedure to remove any third-party libraries, it should contain the definition of an src
attribute with //t.contentsquare.net/uxa/
.
Removing the e-commerce tag
Section titled Removing the e-commerce tagThis is a JavaScript code that is pushing to the _uxa
array the ecommerce:addTransaction
and ecommerce:send
values.
It is usually fired only on your confirmation page and it’s tied to the transaction revenue and ID variables.
Removing artificial pageviews
Section titled Removing artificial pageviewsThis is a JavaScript code that is pushing to the _uxa
array the trackPageview
value.
It is usually tied to AJAX calls or button clicks which trigger actions to display popup windows or significant page changes (URL routing, popup windows).
Removing dynamic variables
Section titled Removing dynamic variablesThis is a JavaScript code that is pushing to the _uxa
array the trackDynamicVariable
values.
It is usually tied to AJAX calls or button clicks which trigger actions to push data to third parties, scrape the HTML source of a page or connect the Contentsquare session data with a third-party tool (analytics/AB testing)
Removing data attributes
Section titled Removing data attributesThere are 2 HTML attributes that may have been added to the HTML code of the website:
data-cs-override-id
, where the HTML tags ID structure wasn’t either compatible with the Contentsquare tracking method or not spread throughout the whole sitedata-cs-mask
, where the HTML source of the page was displaying Personal Information (Personal Data) outside of input fields.
Test that nothing was left behind
Section titled Test that nothing was left behind- Go on the page you want to test using Google Chrome.
- Open the Developers Tools (Ctrl+⇧+I)
- On the Network tab, filter the list with
contentsquare
and reload: the list should be empty. - On the Search tab (it can be hidden in a menu), look for
_uxa
: no result should be found. - On the Search tab, look for
data-cs-
: no result should be found.