[Wyatt]

Hey there! Great job in correctly setting up the GA4 tag and enabling the linking between the domains for GA4. However, it seems that you’re facing an issue because GA4 adds the _gl parameter necessary for cross-domain tracking to link elements. Your “Aplicar Ahora” button isn’t recognized as a link by GA4 because it’s not a link element, which is why you’re not seeing the _gl parameter.

Good news is that there’s a simple fix for this. If you change the button to an actual link element, GA4 will identify it as such and add the _gl parameter, enabling cross-domain tracking to work seamlessly. Give this a shot!

[Wyatt]

It sounds like you’re in a bit of a tight spot! Honestly, if you use one GTM container and add a condition to check for GDPR specific domains, you should be fine. This will eliminate any inaccuracies and make your life easier, as updating would only need to be done in one place. The consultant might be extra cautious, but adding unnecessary complexity can be just as risky as slicing corners.

[Wyatt]

Sure, let’s break it down into a discussion:

Let’s say you want to create a sneak peak link from your website that secretly tracks clicks before whisking users to their intended destination. To do that, you’ll need Google Tag Manager (GTM).

Here’s a simple step-by-step guide:

1. First, you need to establish a new URL variable in GTM that checks for the presence of a “redirect” query in your URL. Let’s call this url-redirect-parameter.

2. Next, you’ll need to craft a JavaScript variable that checks for url-redirect-parameter and redirects users to its URL after a short delay, giving GTM enough time to register the visit. Not tech-savvy? No worries, here’s the code for it:

`javascript
function() {
try {
return {{url-redirect-parameter}}?setTimeout(function(){window.location='{{url-redirect-parameter}}’},500):false;
}
catch(e) {
return e;
}
}
`

3. Now, link this new JavaScript variable to a new GTM tag and have it trigger your Google Analytics (GA) tag on your website.

What you have now is a clever little system that springs into action the moment it detects “redirect=” in your website URL. It logs the visit and then redirects the user to their destination.

There is another way to do this – by simply adding UTM parameters to a page on your site and have a code on the page auto-redirect to a parameter. It’s a similar principle: the catch here is the presence of a query string (QS) in the URL.

At the end of the day, both methods tell you who is clicking on your links and where they’re going. Now you can see that traffic in your Universal Analytics results.

This seamlessly integrates with GTM and GA and doesn’t involve adding additional code to another website. So yeah, it’s pretty cool how you can layer your own tracking onto someone else’s link, right?

[Wyatt]

In Google Analytics 4 (GA4), custom parameters get attached to events to which they are relevant, but can appear within other events too. Essentially, when you generate custom definitions for any parameters in GA4, you’re making these parameters universal and they can appear across different events, even when they’re not directly associated with those events. This is why you’re observing “Updated_Footer_Menu_event” definitions when you click on “Updated_Header_Menu_event”.

So, these custom dimension/definition aren’t technically unrelated to these events, they’re simply universal because they were created as custom definitions in GA4. They may not be relevant but they will continue to appear regardless. This function allows for the cross-analysis of data across different event types which might be useful in certain analytics settings.

[Wyatt]

No, you can’t pull a user’s GCLID (Google Click Identifier) using Measurement Protocol. The Measurement Protocol is primarily designed for sending data to Google Analytics, not retrieving it. It doesn’t provide a specific parameter for accessing the GCLID. GCLID is mostly used in Google Ads for auto-tagging and tracking the effectiveness of advertising campaigns. It is applied when a user clicks on an ad and is directed to a webpage with Google Analytics enabled. For retrieving GCLID, other methods should be employed outside the scope of Measurement Protocol.

[Wyatt]

So, just to put it out there, the ‘Elapsed Time’ we’re talking about here is actually a total, not an average. Meaning, each time a user moves from step 1 to step 2 in the funnel, that time gets piled up, not averaged out. I’ve tried finding a way to check the average or median of Elapsed Time but came up with nothing, which is a bummer since I think an average would be way more useful than a total. And I don’t think there’s a way to see how many times this shift from step 1 to step 2 actually happened, so even if you wanted to, you can’t do the math to get the average yourself.