UTMs vs the GCLID
UTMs and the GCLID solve overlapping problems from different directions. The GCLID is set automatically by Google and is what Google Ads uses for its own attribution and offline imports. UTMs are manual and are mainly consumed by analytics platforms like GA4. On Google Ads traffic you often want both: auto-tagging for the GCLID so Google Ads reconciles correctly, and UTMs so your analytics reporting is consistent across every paid and non-paid channel. They are complementary, not competing, and turning off auto-tagging to force UTMs is usually a mistake.
Common UTM mistakes
Almost every broken UTM report traces to inconsistency. Mixed casing, where one campaign uses Facebook and another uses facebook, splits what should be one row into several. Free-text mediums like paid, ppc, and cpc used interchangeably scatter paid traffic across buckets. Spaces, inconsistent separators, and typos do the same. Because analytics treats these strings literally, there is no forgiveness: the fix is a written naming convention, lowercase everywhere, a fixed vocabulary for medium, and a shared builder so nobody hand-types tags.
How iClick standardizes UTMs
iClick enforces a single UTM naming convention across every channel so reporting rolls up cleanly instead of fragmenting into near-duplicate rows. The rule is lowercase everywhere, a fixed controlled vocabulary for medium, and a shared spreadsheet or builder that generates every tagged URL, so no one improvises. Auto-tagging stays on for the GCLID alongside the UTMs, because the two serve different tools. Consistency, not cleverness, is what makes UTM data trustworthy.
