A calm way to set up GA4 that you will not regret

Dear founder,

I've lost count of the GA4 accounts I've opened to find events firing twice, purchases with no value attached, and internal traffic quietly inflating everything. None of that is GA4's fault. It's the fault of a setup done in an afternoon, under pressure, with the tag copied from a forum post.

Get the foundations right first

Before you touch a single custom event, sort the basics. They're dull, and they're the reason your numbers will make sense in six months.

• Filter out your own traffic so your team's browsing doesn't pollute the data
• Confirm the purchase event carries a value and currency — this is where most stores go wrong
• Set your reporting time zone and currency to match how you actually run the business
• Turn off Google Signals unless you genuinely need it and understand the reporting knock-ons

Test before you trust

The single habit that separates a reliable account from a mess is checking things fire correctly before you rely on them.

1. Use the DebugView to watch events land in real time
2. Place a real test order and confirm the value matches
3. Wait a full day, then compare against your platform's own order count

If GA4 and your store disagree on how many orders you took, fix that before you look at anything else. Everything downstream depends on it.

Don't measure everything on day one

You do not need forty events to start. You need purchases, add to carts, and page views working perfectly. Add more only when you have a question they'll answer.

A quiet, careful setup is worth ten clever dashboards built on shaky data. If yours was thrown together and you no longer trust it, start with a FREE call and we'll work out whether to repair it or start clean.