Infinity visits vs Google Analytics sessions do not match, because the two platforms attribute credit in different ways. This article explains how Infinity counts a visit, how Google Analytics counts a session, and why we recommend not comparing the two.
An Infinity visit is the same as a "land" trigger. Because Infinity's tracking is JavaScript based, sometimes when a visitor moves around a website the referrer data they send back shows a land, when they are really clicking back to the first page, or their browser is hiding referrer data.
To avoid generating spurious land triggers (visits), Infinity performs re-land detection. This compares the current landing source with the last tracked landing source, and decides whether to count the land or convert it to a page view instead.
The re-land algorithm is activated if the land occurs within 30 minutes of the last visitor activity.
Google Analytics works differently. When you compare Infinity visits vs Google Analytics sessions, note that a single user can trigger multiple sessions, on the same day or over several days, weeks or months. As soon as one session ends, there is an opportunity to start a new session.
By default, a Google Analytics session lasts until there are 30 minutes of inactivity, but you can adjust this length so a session lasts a few seconds or several hours. Because visit and session data are tracked in fundamentally different ways, we recommend not comparing visit metrics across the two platforms.
We do not send channel data into Google Analytics for any online calls. Instead, we send the GUA_CID captured from the visitor along with the Infinity event (call, CRM event and so on), so Google Analytics can find the visitor by their Client ID in its own system and assign the channel it sees fit to the Infinity event. We do send basic channel information for calls that do not have a GUA_CID (offline calls). GA4 marks offline calls as 'Unassigned', as there is no URL string to define the online channel.
Below are examples of how we send Infinity events into Google Analytics.
For calls to dynamic pool numbers that are attributed to an Infinity visitor ID, we do not send the Infinity marketing data (channel) to Google Analytics. We send only the GUA_CID variable, as explained above. This allows Google's own attribution model to be applied to online calls, so they can be mapped back to the Google tracked visitor journey.
Because no land is detected for fixed number calls, we cannot record a Google Analytics Client ID against the call event. Our system detects this and instead sends the Infinity marketing source data using UTM variables.