How to explain the gap between the number of clicks on Facebook and the number of visits in Piano Analytics?
How to explain the gap between the number of clicks on Facebook (or other Meta platforms such as Instagram) and the number of visits in Piano Analytics?
Why clicks and visits don’t match
Facebook counts a click each time a user interacts with a link. This count does not require your page to finish loading, and it can include repeated clicks from the same user.
Piano Analytics counts a visit only when your site successfully sends its first event for that session (typically a page load). In other words, the redirection from the external source must be correctly completed, and the destination page must be fully loaded enough for tracking to fire.
As a result, it is normal to see more Facebook clicks than Piano Analytics visits.
Conditions required to attribute a visit to a campaign
For a visit to be attributed to your Facebook campaign in Piano Analytics:
The user must reach your site and trigger the first tracked event of the visit (for example, a page view).
The campaign tag must be present in the destination URL on arrival so Piano Analytics can detect the campaign source.
If the campaign parameters are missing on landing (for example, removed during redirection), the visit will still be counted, but it may not be attributed to the Facebook campaign.
Common reasons for discrepancies
Multiple clicks can produce a single visit
If a user clicks twice on a Facebook link (due to connectivity issues on their end for example), this counts as two clicks for Facebook but only one visit to your site.
A visit is a set of pages visited within a delimited timeframe. Example: a user consults their Facebook feed, clicks on your tagged link, and accesses the page on your site. They then go back to their feed and click another tagged link of yours. If 30 minutes (by default) have not passed between the two events, only one visit will be counted for 2 clicks.
The click doesn’t result in a trackable page load
Facebook may count a click even if:
The user abandons the navigation before the page loads.
The page fails to load (network issues, timeouts, etc.).
In these cases, Piano Analytics may not receive any event, so no visit is recorded from that click.
Tracking parameters are stripped or altered
Campaign attribution depends on parameters being present on the landing URL. Discrepancies can occur if:
The URL is not tagged correctly.
A redirect removes query parameters.
Third-party tools or campaign setup processes modify or strip tracking parameters.
Measurement is affected by user privacy tools
Piano Analytics can only count what it receives. Differences may be increased when users:
Use ad blockers or privacy tools that prevent events from being sent.
Opt out of tracking (so events are not collected).
Bots and non-human traffic
Ad platforms can report clicks that may include automated or low-quality traffic. This traffic does not always result in a real page load with trackable events, which can widen the gap between clicks and visits.