THE WHOVISITED BLOG
Build better tracking.
Make clearer decisions.
Practical engineering notes on website analytics, signup goals and traffic sources. Real examples for the websites you build.
How to diagnose HTTP 429 errors in website analytics
Distinguish a monthly event quota from per-minute rate limiting, inspect the failed endpoint, and avoid mistaking a retry queue for durable analytics delivery.
· 5 min readRead article Implementation · PrivacyKeep personal data out of website analytics events
Audit URLs, page titles, referrers and custom event properties so analytics answers product questions without collecting form data or identifiers.
· 5 min readRead article Analytics infrastructure · PrivacyTrust proxy headers before using visitor country analytics
See why IP-based country reports can show a CDN location, how to configure trusted proxy ranges safely, and what WhoVisited currently records.
· 5 min readRead article Next.js · Analytics testingKeep Next.js preview deployments out of production analytics
Prevent test traffic from polluting live conversion reports by separating production, preview, and local WhoVisited installations.
· 5 min readRead article Traffic attribution · TroubleshootingKeep campaign attribution through landing-page redirects
Trace UTM parameters across redirects, confirm when WhoVisited records a session source, and fix a broken campaign path without storing sensitive query data.
· 5 min readRead article Search performance · Conversion analysisTurn Search Console page data into a useful landing-page review
A practical way to compare Google Search Console page impressions and clicks with website sessions and goal sessions without claiming a query caused a conversion.
· 5 min readRead article Visitor analytics · PrivacyWhy one person can appear as more than one website visitor
Learn how browser storage creates analytics visitor and session IDs, why those counts do not equal people, and how to check identity splits without collecting personal data.
· 5 min readRead article Conversion tracking · DebuggingDuplicate conversion events: safe retries versus a second event
Learn when WhoVisited deduplicates a retried event, why a second track call is different, and how to test conversion signals without counting an action twice.
· 7 min readRead article Search Console · ReportingWhy Search Console data can look stale in your analytics dashboard
Learn why WhoVisited waits for finalized Search Console data, how its snapshot cache works, and how to read the date and sync status before comparing trends.
· 6 min readRead article SecurityIs a website analytics site ID a secret?
Understand what a public tracker site ID can do, how origin checks and short-lived tokens protect event ingestion, and where browser analytics still has limits.
· 5 min readRead article Next.jsPrevent custom events from racing an async tracker in Next.js
An async analytics script can load after a signup or form succeeds. Use Next.js Script readiness to queue a small number of custom events without blocking the user flow.
· 5 min readRead article ImplementationWhy a website analytics tracker splits visits across subdomains
Learn why the same browser can appear as separate visitors on your main site and app subdomain, how allowed origins affect collection, and what to check before comparing those journeys.
· 6 min readRead article Conversion tracking · SaaSMeasure demo bookings beyond the scheduler click
Separate interest in a demo from a completed booking when a visitor leaves your site for a scheduling tool, and set an honest WhoVisited goal.
· 5 min readRead article Measurement · CampaignsCompare two campaign landing pages with the same conversion goal
Set up a fair, practical landing-page comparison with consistent campaign tags and one outcome goal, then read the limits of the result correctly.
· 5 min readRead article Measurement · ImplementationKeep analytics event names stable as your product evolves
Choose event names that stay useful in reports, match WhoVisited goals exactly, and change their meaning without breaking your conversion history.
· 5 min readRead article Implementation · PrivacyHandle consent changes and browser privacy signals in analytics
Connect a consent manager to WhoVisited, handle withdrawal safely, and test how Global Privacy Control and Do Not Track affect collection.
· 5 min readRead article Implementation · SecurityAllow a website analytics tracker through your Content Security Policy
Find the CSP directives that control an analytics script and its event requests, test changes in report-only mode, and diagnose blocked collection safely.
· 5 min readRead article Search Console · TroubleshootingFix a Search Console property that does not match your website
Troubleshoot why a verified Search Console property is missing from WhoVisited by checking property type, protocol, hostname, and the site's allowed origins.
· 6 min readRead article Analytics fundamentals · AttributionRepeat visitors, sessions and source attribution: what your analytics is counting
Learn how WhoVisited separates a browser visitor from an activity session, when a return visit starts a new session, and how to test session-level source reports.
· 6 min readRead article Traffic sources · AttributionWhy website traffic sources show Unknown and how to investigate it
Understand why referrers disappear, how WhoVisited prioritizes UTM campaigns, and how to test redirects, privacy policies and direct visits safely.
· 7 min readRead article Release testing · AnalyticsA landing-page analytics release checklist that checks more than script loading
Verify a landing-page release from campaign arrival through accepted conversion, with checks for consent, collection requests, fresh sessions and safe test evidence.
· 7 min readRead article Conversion goals · Measurement designSuccess-page goals or custom events: choose a conversion signal you can trust
Choose between exact success-page paths and confirmed custom events in WhoVisited, with tests for direct visits, retries, session counts and incomplete tracking.
· 7 min readRead article Navigation tracking · TestingVerify single-page application page views without counting every URL change
Test WhoVisited page views across client-side routes, browser Back, query changes and hash navigation, with an explicit checklist for consent and delayed page titles.
· 6 min readRead article Integration hygiene · Next.js and GTMAvoid duplicate WhoVisited installations in Next.js and Google Tag Manager
Audit duplicate tracking snippets, understand which WhoVisited configuration takes effect, and migrate between app layouts and Google Tag Manager with a verification checklist.
· 7 min readRead article Conversion engineering · Data minimizationTrack contact form conversions without collecting form contents
Measure accepted contact form submissions in WhoVisited using a minimal custom event, with failure and retry checks that keep names, emails and messages out of analytics.
· 7 min readRead article Traffic attribution · Campaign engineeringA practical UTM naming system for small SaaS launches
Build consistent campaign links for a SaaS launch, validate the three UTM fields WhoVisited supports, and compare source sessions with signup goals.
· 7 min readRead article Troubleshooting · Analytics integrationAnalytics tracker loads but no events appear: a WhoVisited debugging checklist
Debug missing WhoVisited visits by separating script loading, consent, origin checks, bootstrap responses and event ingestion, with safe browser diagnostics.
· 7 min readRead article Next.js · Conversion trackingTrack completed signups in a Next.js app with WhoVisited
Install WhoVisited in a Next.js App Router layout, record successful signups, and verify which traffic sources bring conversions without tracking personal data.
· 6 min readRead article