Ad platforms count clicks. Kickbite counts sessions that reach your site with the Kickbite script running and consent rules passed. Those two numbers are not the same thing.
Why clicks ≠ sessions
Not every click loads your site with a measurable session — bounces, blockers, redirects, and in-app webviews all lose sessions.
Cookie consent and privacy settings can block or delay the Kickbite script.
Multi-touch and same-day revisits behave differently in ad UIs than in Kickbite session logic.
A gap between platform clicks and Kickbite sessions is normal. Many accounts see a noticeable gap — often in the region of 10–15%, sometimes more — depending on consent rate and traffic quality. Treat that as a calibration fact, not automatic proof of broken tracking.
Cookie consent impact
If consent rates drop, Kickbite sessions often drop even when ad clicks stay flat. Check your consent tooling and the first-session articles below when sessions change suddenly after a CMP update.
When a sudden session change is a real incident
Investigate further when:
Sessions drop sharply while consent and site traffic in analytics stay flat
The drop starts on a specific day, right after a tag, CMP, or site release
Only one channel or market is affected in a way that matches a template or script change
Expected noise includes day-of-week patterns, promo spikes, and consent A/B tests. Compare complete days and the same attribution model before escalating.