Tracking Configuration per Use Case

Depending on your application, deployment and disclosure requirements, you will find different implementations more suitable.

Depending on implementation and jurisdictions your business operates in, you will find different approaches generating different disclosure requirements.

In this chapter, we will highlight common scenarios with our risk assessment. Your individual case might differ, so it is paramount to do an accurate risk and compliance assessment specific to your business.

Modern Single Page Application

A single Page Application is an application that makes heavy use of JavaScript and processing on the client side. The benefit to the end user is such that after initial load, the subsequent experience is very smooth and devoid of page reloads.

Because the user is rarely required to refresh the browser window, a default deployment of Wide Angle Analytics script is very effective. Our script will generate a visitor's session identifier and use it to observe the user's journey through the online property.

It is reasonable to assume that tracking is efficient even without cookie setting being enabled.

Depending on your jurisdiction, it is very likely that no further disclosures are necessary.

• Weak Session Identifier or an optional in-Browser fingerprinting takes place, but its outcome is obfuscated. User cannot be identified after no more than 24 hours.
• No tracking information is stored on the client side.
• No Personal Data is stored.
• The data processed, when classified as Personal Data (such as IP and full User Agent) is obfuscated and stored in a non-reversible manner.

Multi-SPA or Traditional Web Application

Large applications or legacy, transformed deployments sometime consist of multiple Single Page Application stitched together to deliver a comprehensive user experience. A user moving across such an application might encounter a single being reloaded. From a web analytics perspective, this makes these deployments similar to more traditional Web Applications.

By traditional, we understand web applications where users' browser window is partially or fully reloaded based on user interaction.

The default Site setting in Wide Angle Analytics will perform very well with these kinds of applications.

Depending on your jurisdiction, it is very likely that no further disclosures are necessary.

• Weak Session Identifier or an optional in-Browser fingerprinting takes place, but its outcome is obfuscated. User cannot be identified after no more than 24 hours.
• No tracking information is stored on the client side.
• No Personal Data is stored.
• The data processed, when classified as Personal Data (such as IP and full User Agent) is obfuscated and stored in a non-reversible manner.

Users with long sessions

If you are interesting is analysing your traffic over a long period of time, assuming your users use the web application in the span of multiple days, or it can be beneficial to enable cookies setting for your Site.

In this mode, the Wide Angle Analytics will create a cookie in the visitor's browser. That cookie will be refreshed with each visit and will be voided after 24 hours of inactivity.

With the cookie approach, a user who visits your online property, using the same browser but from different locations, e.g: office, home, mobile on the train, will be re-identified. The IP address is not relevant.

Depending on your jurisdiction, it is very likely your website will need to disclose the use of cookies.

• Browser fingerprinting takes place and that fingerprint is stored on the client side.
• The fingerprint and IP address are stored in by Wide Angle Analytics in an obfuscated and non-reversible manner.

Web Application with registered users

Wide Angle Analytics provides you with a mechanism to analyse the behaviour of your registered users. This technique requires neither cookies nor browser fingerprinting.

When initializing the tracking script, you can pass the Customer ID. That ID will be recorded verbatim with each event.

Assuming you can integrate your desired ID (customer ID, client ID, visitor ID), derived from your system, you can reliably follow your visitors regardless of which device or browser they use.

Disclosure requirement will depend on the jurisdiction and the type of Customer ID. If Customer ID is a customer's name, email, IP or similar Personal Data, you will have to make proper disclosures to your users.