Call tracking cookies are the small pieces of data that let Infinity work out where a visitor came from and which tracking number to show them. Infinity stores this data in local storage where the browser supports it, and falls back to first-party cookies where it does not. This guide explains the cookie types and storage Infinity uses, and how to classify Infinity for consent.
First-party cookies are cookies that belong to the same domain that is shown in the browser's address bar (or that belong to the subdomain of the domain in the address bar).
It is important to understand what type of cookies your website relies on when it comes to call tracking, as this may affect the way your tracking works.
Third-party cookies are cookies that belong to domains different from the one shown in the address bar. Web pages can feature content from third-party domains (such as banner ads), which opens up the potential for tracking the user's browsing history.
Local storage is a robust and efficient way to store data within a user's browser. Unlike cookies, which are limited in size (typically around 4KB per domain) and are sent with every HTTP request, local storage can handle larger data sets, usually in the range of 5-10 MB. Importantly, this data isn't sent with every request, resulting in a smoother and more responsive user experience. These advantages make local storage our top choice for data storage.
Our tracking library is configured to use local storage where available, with a fallback to use cookies in the event that the visitor's browser does not support local storage.
Our cookie lasts 10 years by default when we use local storage, but can be configured by amending the Javascript client-side code.
Local storage uses the same names and collects the same data as described in the cookies section below for the first-party cookies. We use local storage or first-party cookies, depending on browser support, to ascertain where a visitor came from and what number to display to them. Many of these cookies are stored on a per-installation basis and so will be suffixed with the Installation ID (denoted by).
When dealing with cookies, it's essential to differentiate between first-party and third-party cookies. We exclusively use first-party cookies, which are tied to the website you are currently visiting and are used for purposes directly related to that site only. They do not engage in cross-site tracking or data sharing with external domains, minimising privacy concerns. In contrast, third-party cookies, often set by external domains for cross-site tracking and ad targeting, are not a part of our practice.
For sites using the new Infinity script, the following data is stored as a JSON object under the local storage key _its.{installationId} (replacing {installationId} with the current installation ID).
Depending on configuration and browser support, data may also be stored in cookies which follow the name of the values above, prefixed with _its.{installationId}. For example, the visitor ID if stored as a cookie would be under the key _its.{installationId}.vid.
Below is an outline of each cookie stored by our legacy script, and what it is used for.
In the digital age, data security and user privacy have become paramount concerns. At Infinity, we place a high premium on safeguarding user data and adhering to stringent standards like ISO 27001, PCI DSS Service Provider Level 1, HIPAA, and GDPR (General Data Protection Regulation). To achieve this, we prioritise the use of local browser storage as our preferred method for data storage and user interaction.
We acknowledge that users have the option to disable local storage in their browser settings. Only in such cases, we turn to cookies as an alternative. Our cookies are specifically designated as first-party cookies because they are associated only with the domain our call tracking script operates on, ensuring a high level of user privacy and data security in line with GDPR and similar regulations.
Our commitment to data security standards, especially GDPR, is unwavering. We adhere to these regulations, striving to maintain the highest standards of data protection and privacy. Our preference for local storage and first-party cookies aligns with these principles, assuring users that their data is handled with the utmost care and in compliance with the most stringent data security standards. We prioritise local storage for its efficiency and data security benefits, turning to first-party cookies only when necessary. We are committed to PCI DSS, ISO 27001, HIPAA, and GDPR compliance and respect individual website policies and privacy standards.
This article is applicable to any customers looking to deploy the Infinity tracking script on websites in regions with local laws and regulations on cookie consent, including:
When managing various technology partners on your website, it's crucial to classify them accurately to comply with data protection regulations and enhance user trust. This decision typically falls under the responsibility of your website owner or entity. In larger organisations this may fall under the remit of a Data Protection Officer (DPO) or the compliance or legal team.
Consent for data processing, including cookies and personal information, is typically managed through website consent management practices like cookie banners. These banners outline cookie types and purposes, allowing users to accept or reject them.
Essential cookies are integral to basic website functions, ensuring core features operate smoothly such as remembering shopping cart items or ensuring telephone calls get routed to the right department.
Non-essential cookies enhance user experience through personalisation and analytics insights.
Infinity is a product with various services and use cases. Many of our customers classify Infinity as an essential consent class, but that's for you to decide. We have provided information below on the typical use cases where our customers classify Infinity as an essential consent class:
You'll still get rich insight, but only from users who accept (opt into) cookies.
The Infinity tracking script will not activate for any users who decline (opt out) of non-essential cookies, meaning that any calls from these users will not be handled through the Infinity Platform. If you decide that Infinity isn't an essential cookie, there is a way to maximise the insights you gather by setting up fallback numbers.
Fallback numbers can automatically take the place of your standard dynamic numbers when a visitor declines consent. They'll help you to ensure all calls are handled by the Infinity Platform and still capture useful data.
You can set up one fallback number for each of your tracking pools, so if you've not already got them set up, you can get started by getting in touch with our support team.
Deciding whether Infinity is essential requires careful consideration aligned with regulatory requirements. We understand that many of our customers have elected to classify Infinity as essential due to the value of the insights that are generated, and the operational benefits associated with our product features and solutions.
Our article on cookie consent will provide further information on classifying Infinity. You can decide what data is 'strictly necessary' when gathering consent.
Many of our clients have elected to classify what they gather with Infinity as necessary because it's enabling them to provide a functional, beneficial experience to their customers. Some reasons and uses include:
If these aren't ways in which you're currently using call tracking data, but you would like to in the future, get in touch with your Customer Success Manager to learn about how you can achieve this.
Also, we don't sell any data from either you or your customers, nor do we use your visitors' data to optimise our own product, and we don't use third-party cookies.
This data is also useful for marketing analytics, sales funnel insights, and other uses where understanding customer engagement is crucial. If you're using it for these other purposes, that needs to be communicated when outlining your strictly necessary data gathering.
If you want to ensure you're able to fully monitor how website traffic flows across the online and offline experience, you'll need to classify Infinity's JavaScript as an essential script.
Google Consent Mode v2 is a framework designed to integrate website visitor consent preferences with Google's advertising and analytics tools. If the website visitor consents, then what Google tracks with its cookies remains the same.
Please read our blog post, which covers Google Consent Mode.
Once you have your chosen means in place to gather consent, Google has detailed support pages on activating Google Consent Mode v2.
To find out how the tracking script is added to your site, read Install the Infinity JavaScript code. To learn more about visitor-level call tracking, read Visitor Level Call Tracking.
If you're still stuck, get in touch with your Customer Success Manager or email support@infinity.co.