For visitor tracking to work, a number of requirements must be met.
- The visitor must have Java Script activated in their browser - this is the standard for most browsers.
- Browser plug-ins such as ad blockers or similar may prevent Quentn's Java Script from communicating with the server.
- The visitor must be identified. By using cookies, a website can recognize whether a visitor with the same browser has been on the site before. However, at this point it is not yet known who this visitor is. Only when the visitor performs an action that identifies them does the website (in this case the Quentn system) know who they are and can assign the behavior to a contact and, if necessary, trigger events.
How does a visitor identify himself?
- By clicking on a trackable link in an e-mail sent from Quentn
- By entering the email address in a form - here the thank you page must lead to the website on which tracking is to take place.
- It is also possible to identify a user based on an email address that a third-party provider attaches as a query parameter to a link on your website. This can happen, for example, if a visitor is redirected to a thank you page after a purchase.
- Cookies must be permitted and should not be deleted. Even if a visitor has identified themselves but does not allow cookies, they can no longer be assigned when a new page is accessed or a new session is started. The same applies if the visitor deletes all cookies from their browser at some point. A new, identifying action is then required.
Note: An event only triggers once per session, even if a visitor fulfills an event condition several times within a session. After 30 minutes of inactivity, a visit is counted as a new session. Under certain circumstances, inactivity cannot be measured correctly due to JavaScript requests in the background.