-
The Impact of Sending Varied Events with the Same Name to Google Analytics 4 via Google Tag Manager
Imagine channel surfing on a site with a ton of buttons, divvied up into three groups, let’s call them
A
,B
, andC
. Every one of these buttons pushes a custombutton_click
event to thedataLayer
, when clicked. The event data includes standard columns likebutton
,size
, and so on. But there’s also a handful of “wildcard” properties that differ from set to set. Have a look:dataLayer.push({event: "button_click", button: "b1", size: "L", ..., service_id: 1, name: "John" }); // A dataLayer.push({event: "button_click", button: "b2", size: "S", ..., language: "en", term: "Long" }); // B dataLayer.push({event: "button_click", button: "b3", size: "M", ..., color: "red", item: "Shoe" }); // C
Here’s the twist: despite their differences, all three events share the same
button_click
name. So I’ve got two brain-busters for you:- Are there any potential issues with Google Analytics4 if different events share the same name?
- Knowing that in reality, there’s way more than just three sets, and lots of “common columns” that need to be manually entered into Google Tag Manager (GTM) for each one, is there any way to dodge the hassle of entering them repeatedly?
Would love to hear any thoughts or insights!
Log in to reply.