digital — tracking

GA4, configured to answer business questions.

Google Analytics 4 out of the box answers an analyst's questions in an analyst's language — which is why most business owners open it once, feel judged, and never return. Configured properly, it answers yours: did the website produce enquiries, from where, and is that changing. That configuration is the service.

what configuration means

From default noise to five numbers.

Events that mean something

Form submissions, phone taps, quote requests — defined deliberately and marked as the conversions they are, fed cleanly from the tag layer. Scrolls and clicks demoted to the background noise they are.

Data kept honest

Internal traffic filtered, referral spam handled, cross-domain journeys stitched, and the settings — retention, signals, IP handling — chosen deliberately rather than left on defaults.

Reports people open

Two or three saved views answering the owner's questions: enquiries by source over time, which pages carry the weight, what paid traffic did after arriving. Everything else exists when needed, invisible when not.

the honest bit

What GA4 can't tell you.

Analytics sees the website, not the business: it counts the form submission but not the phone call answered at the counter, the quote sent or the job won. Treating GA4 as the whole truth flatters channels that fill forms and slanders channels that ring phones. It's one instrument in the set — the join to your job ledger is where the real answers live, and we build toward that from day one.

Consent-mode gaps and privacy features also mean GA4's numbers are partial by design now. Configured well, it's an honest sample, not a census — reports should say so, and ours do.

straight answers

Asked often.

GA4 confuses everyone in our office. Is it us?

It's not you — GA4's default interface answers an analyst's questions, not an owner's. The fix is configuration and reporting: define the events that matter to your business, mark the real conversions, and build the two or three reports people actually open. Most of GA4's noise is optional.

What should a service business track in GA4?

Enquiry events above all: form submissions, phone taps, quote requests — plus the source data that says where each came from. Beyond that, less is more; a tidy property answering five questions beats an exhaustive one answering none.

Is GA4 compliant with Australian privacy expectations?

It can be run responsibly: IP handling configured, consent respected via the tag layer, no personal information in event data, and retention set deliberately. Privacy regulation is tightening, so we configure conservatively — and document what's collected and why.

next

Five numbers you'd actually open.