Data is the lifeblood of modern marketing, but lately, a "ghost" has been haunting the reports of New Zealand businesses.You’ve likely seen it in your GA4 (Google Analytics 4) dashboard: a massive, grey block labelled Unassigned sitting right where your Facebook Ads, Google Search, or Email traffic should be.It’s frustrating. You’re making strategic investments in digital growth, but GA4 is effectively shrugging its shoulders when you ask for the ROI. In a world where we are moving toward different commerce protocols, where AI tools need high-fidelity data to act on your behalf, having "broken" data isn't just a reporting nuisance; it’s a competitive liability.Let’s pull back the curtain on why this is happening and how to get your data in order.What is "Unassigned" Traffic, Really?In the old days of Universal Analytics, Google was a bit more forgiving. If it didn't know where a click came from, it usually dumped it into "Other" or "Direct."GA4 is different. It operates on a strict set of Default Channel Group rules. These rigid rules automatically organise traffic based on source, medium or URL parameters like GCLID.Think of it like a high-speed automated sorting facility. If a piece of traffic arrives with a label that the machine doesn't recognise, even if it's just a capital letter where a lowercase one should be, the system doesn't guess. It drops it into the "Unassigned" bucket.The Four Most Common Data LeaksIf your Unassigned traffic is climbing above 10%, you likely have one of these three issues:The UTM Naming Trap This is one of the most common causes of Unassigned traffic and it’s slightly misunderstood.GA4 doesn’t simply expect lowercase like most of us believe. The real issue is how GA4’s Default Channel Grouping rules work behind the scenes.When traffic arrives on your site, GA4 checks the utm_source and utm_medium values against a predefined set of rules. These rules use pattern matching (regular expressions) to determine whether traff...