Ability to Customize UTM Values in GHL
K
Kalyn Banford
I highly recommend expanding and refining UTM value handling in Go High Level. The current setup is limited, and some default mappings don’t follow common tracking standards.
Example Issues:
-The utm_medium for paid ads is currently set to "adname" rather than a standard value like "cpc" or "paid".
-Source data is too broad (e.g., "Paid Ads" or "Organic") rather than specifying the actual platform such as "google", "facebook", or "bing".
-For organic traffic, the utm_medium is pulling in the form name, which is not relevant. This makes it impossible to see which platform the lead came from.
Ideal UTM Scenario:
-Paid Ad from Google: utm_source=google | utm_medium=paid
-Paid Ad from Facebook: utm_source=facebook or fb | utm_medium=paid
-Organic Search: utm_source=google (or bing, yahoo, etc.) | utm_medium=organic
Why This Matters:
Accurate UTM structure is crucial for clean reporting and reliable attribution. Without proper utm_source and utm_medium values, it’s difficult to analyze performance by channel and platform.
Log In
K
Kashif Rehman
Yeah, The current UTM tracking in GHL is not very effective. HubSpot offers more detailed and reliable UTM tracking, so this should be improved to ensure better accuracy and reporting.