The messy jobs: confusing GA4, agency reporting, ad blockers, mismatched numbers.
- Agency client reporting, minus the bloat — One SiteLine user per subscription, unlimited sites, Search Console plus cookieless analytics. Multi-member teams exist in code but stay off by default.
- Analytics blocked by ad blockers — Filter lists cut third-party analytics scripts. Proxy the SiteLine script and collect path first-party to reduce the loss. It does not vanish.
- Why GA4 is confusing, and what to do — GA4 piles taxonomy, identity, and modeled conversions into one UI. SiteLine is cookieless pageviews, named events, dashboard goals, and Search Console.
- Unique visitors without cookies — SiteLine unique visitors are a daily hash of truncated IP, user agent, and a rotating salt. No analytics cookie, no cross-day person, no GA4-style user id.
- Why analytics numbers don't match — SiteLine will not match GA4, GSC clicks or ads. Daily hashes, blockers, bot filters, lag and different event definitions pull the totals apart on purpose.