# Web Tracking The CrossEngage Web Tracking gives the opportunity to track users website behaviour with or without being logged in and properly identified, with the help of a cookie (given consent) that serves as the identifier for the CrossEngage system. If at a later point in time the user does get properly identified, the CrossEngage system merges the tracked behaviour of the anonymous user to the already exististing user. {% hint style="info" %} This cookie is considered a **First Party Cookie** because it is set to the domain of the website the tracking is inserted in and not some third party outside service. It has a lifetime of 13 months. {% endhint %} There are different ways to integrate Website Tracking: * Web Tracking v1 is deprecated and will not be setup anymore * [Web Tracking v2](/data-and-engagement-platform/web-tracking/web-tracking-v2.md) is the currently supported version of the CrossEngage Web Tracking. It can be setup using the [Google Tag Manager](/data-and-engagement-platform/web-tracking/web-tracking-v2/setup-using-google-tag-manager.md) or [without GTM](/data-and-engagement-platform/web-tracking/web-tracking-v2/setup-without-a-tag-manager.md). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.crossengage.io/data-and-engagement-platform/web-tracking.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.