![]() The Tracking Tag will retrieve Contentsquare cookies on every domain configured for the project. There are two possible implementations of cross-domain tracking: It is possible to configure the tag so that a session started on a domain stays alive on another one. Activating Cross-domain analysisĬross-domain tracking does not work on Safari and Firefox.Ĭross-domain tracking will only work if HTTPS is enabled. This is because Contentsquare doesn't use third-party cookies. For example, a web user going from to will be identified as a "site exit" on and identified as a "new visitor" on. It is possible to associate several domains on a same account.īy default, a browsing session on a domain doesn't continue on another domain. ![]() The visitors inclusion percentage for every collected data.Ī project ID corresponds to only one instance on this configuration.Ĭonsequently, if you want different inclusion percentages following sections of the site, you will need several tag IDs, meaning that data will be aggregated in several accounts separated on the Contentsquare interface.IP addresses to exclude from the collection,.The authorized domains (and subdomains if authorized),.Each ID is a tag instance for which are notably setup: Your subscription to a Contentsquare contract gives you access to a tag ID composed of 13 characters. This chapter covers global notions clarifications on each aspect will be detailed in further chapters. You will also find all information on the way the library works, and indications on every available command to pass information on correctly. This document will give you all required notions to understand the collection tool. ![]() ![]() It requires the setting up of the Contentsquare Tracking Tag to collect data. The Contentsquare solution provides all indicators necessary to precisely analyze web user experience. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |