Client-side Tracking

Client-side tracking collects events inside the visitor's own browser or app, where a script observes the interaction and sends it straight to a collection endpoint.

The tracking code runs on the page and can see what only the device knows: viewport, scroll position, clicks on elements, the referrer and URL parameters. That closeness is also its weakness, because blocker extensions, browser privacy modes, dropped connections and tabs closed early mean some events never arrive. The common mistake is to treat the client-side number as complete and to read its gap against server records or payment logs as a bug, when the gap is inherent to the method.