Tricks for spotting hidden traffic volumes
Standard reports can miss visits that never trigger a pageview event. This post walks through ways to surface that hidden activity so totals reflect what's actually happening on a site.
Traffic analysis
Blog
Notes on analytics, tracking, and getting the full picture
Short, practical write-ups on reading traffic data, following conversion funnels, and keeping tracking setups useful without crossing privacy lines.
Conversion funnels
Reading a conversion funnel without jumping to conclusions
Drop-off at any one step rarely tells the whole story. A short look at how to compare funnel stages side by side before deciding what to change.
Engagement
Improving survey reply rates
Small timing and placement choices can change how many visitors actually respond to an on-site survey. A few adjustments worth testing before assuming low response is final.
Plugin updates
Following along with changes
Posts here also note plugin updates alongside the analysis pieces, so readers tracking a specific release can see what shifted between versions without digging through a changelog alone.
For setup questions raised by a post, the documentation covers the technical side in more depth, including GA4/UA coexistence and custom e-commerce events.
Privacy-focused tracking changes how a WordPress site owner thinks about analytics. Instead of gathering every possible data point by default, the approach is to start with the minimum needed to understand visitors and then layer in additional signals only when they serve a clear purpose. A tag manager makes that philosophy practical, because scripts for ads, session recording, and statistics can all be loaded conditionally rather than firing on every pageview. The result is a setup that respects the visitor while still giving the site owner meaningful insight into traffic sources, content engagement, and conversions over time.
Cookie notices that adapt to where a visitor actually sits do more than satisfy legal text on a page. When a notice reads the visitor's region, the message can match local expectations around consent, and the scripts that depend on that consent only run where the visitor has actively agreed. This keeps analytics and marketing tools from quietly collecting data in regions where the law expects a clear opt-in, and it avoids the awkward situation of showing a strict banner to audiences who would have been comfortable with a lighter prompt. Geolocation-based notices turn compliance from a blanket switch into a conversation.
Blocking tags and cookies before consent is what turns a privacy policy into real practice. A tag manager that holds scripts, iframes, and pixels in a waiting state until the visitor responds prevents tools from writing identifiers or reading device information during the loading window. That matters because many third-party scripts begin their work as soon as the page renders, regardless of any later banner interaction. By gating those tags on the consent state, the site stays functional, advertising and analytics platforms still receive the data they need from consenting visitors, and the site owner has a single, auditable place to manage which tools run and under which conditions across the whole WordPress installation.