It is not uncommon for data discrepancies to exist between what you see in your Feature.fm Insights pages and other third-party reporting tools. These discrepancies can be the result of many factors including key metric definitions, methodologies and unique nuances of each platform.
Common reasons for click and other metric discrepancies
- Different definitions for key metrics that have the same or similar name: Feature.fm counts Page Visits anytime a visitor lands on the page, and Clicks to Service anytime a button the landing page is clicked. Both of these are different than a Link Click that might be counted by a third-party ad platform. Methodologies and rules for data quality, e.g. bot activity detection and data de-duplication, will also vary from platform to platform and can lead to variability in reporting metrics.
- Browser and cookie settings: All page activity will be recorded in Feature.fm Insights because the activity is happening directly on the landing page. If you are using a retargeting pixel or access token to track activity on a Feature.fm landing page through a third-party site, the event data may not get sent or register if the page visitor has ad or pop-up blockers enabled, or if there are other privacy settings turned on that block cookie tracking. This is especially the case for territories where GDPR applies.
- Geographic and Legal Restrictions: Several countries and regions have restrictions on cookie tracking due to data privacy regulations. Cookie regulations are continually added and updated which are likely to interfere with pixel activity and event data registering in third-party platforms.
In general, Feature.fm analytics and Insights pages should be referenced as the primary source of truth when it comes to traffic and activity on Feature.fm landing pages.