Phonexa users now have the most common reporting discrepancies explained. Check this article for more information.
A list of probable reasons why reporting in Phonexa may not match with other analytics platforms. (Google Analytics, Google Ads, and other services).
-
Comparison with platforms that track only clicks
While Phonexa tracks unique users only, other platforms may count clicks (unique or non-unique), potentially causing reporting discrepancies.
-
Comparison with platforms that use the session metric
Phonexa uses the browser fingerprint and the publisher’s identifier to determine uniqueness, which resets at midnight. For example, in Google Analytics, by default, a session ends after 30 minutes of inactivity. If a user returns during the day and continues browsing the website, a new session begins.
-
Bot traffic
Each platform may track bot traffic and other non-human traffic differently.
-
Leaving a page
Users may leave a loading page either by clicking the “Back” button or closing the page. In this case, some analytic scripts could get triggered, while others won’t be, causing data to be tracked on some platforms and not on others.
-
Defining Unique Users
Phonexa uses the browser fingerprint and the publisher’s identifier to define a unique user, while other platforms may use their own metrics.