[Michael]

In Google Analytics 4, you should be able to track activity and money from each group without setting up Content Groups. Instead, you can indeed use User-ID’s and a data layer to hand over the userId along with the customerGroup. Your proposal to use window.dataLayer.push is on point and would enable you to track these data effectively.

Each time a user logs in, a ‘login’ event is sent to GA4 along with userId and customerGroup-values attached to it. After setting this up, you should be able to see these values in your GA4 interface and create audiences, reports, and analysis based on these user properties. Remember to configure User-ID tracking in the property settings of your GA4 property too. For even more detailed tracking, you may also consider utilizing event parameters for specific actions users take. With this information, you’ll be able to assess which groups are performing best and contributing the most revenue.

[Michael]

As Tony mentioned, it’s not best practice to use both GTM and gtag.js calls on the same page. It’s more effective to stick with GTM because it helps centralize all your analytics data – trying to use both can lead to complications like the one you’re experiencing. So, hanging on to your gtag() might actually be creating more tech debt in the long run.

If you’d rather keep both sets of analytics, start by ensuring that GTM doesn’t have any active ga4 tags. Next, you can troubleshoot your gtag calls by looking into the console or network tab to check for any issues, and also make sure your gtag.js library is loading properly.

If these steps don’t make the situation clearer, you can take screenshots and provide more information about your debugging process.

[Michael]

The issue you’re facing seems to be related to your Google Tag Manager (GTM) trigger not properly recording the ids2_verify_email event in Google Analytics 4 (GA4). This event is supposed to trigger when a user verifies their email and visits a URL containing verify-email. However, despite getting actual traffic to these URLs, GA4 is not registering any events. When you manually test the event in GTM, it works fine, which increases the confusion. There could be several reasons for this.

Maybe your actual users are reloading the page before the GTM tag fires, therefore preventing the event from registering due to the custom JavaScript that checks if the page is being reloaded. It might also be that there are some flaws in the condition that defines when your tag should fire. Lastly, there might be an issue with how GA4 processes or displays the data.

To determine the exact cause, you would need to debug the issue further, potentially by tweaking your GTM configuration, inspecting how users interact with the page, or checking how GA4 handles your data.

[Michael]

In Google Analytics 4, you can’t directly substitute _gaq.push(['_setDomainName', '']) as this belongs to the old Universal Analytics tag method. The domain setting is managed by “cookie_domain” which auto-configures itself in the gtag setup. When you migrate to GA4, you are shifting to an event-based model and much of the configuration that was done in code in Universal Analytics is now handled in the GA user interface. Also, domain configuration is generally handled automatically in gtag.js, the library used in GA4. If you see an error from gtag('_setDomainName', ''); it’s because this command is not valid in GA4. You should remove it from your GA4 scripts because it is not necessary. The error occurs because GA4 does not support the ‘_setDomainName’ command.

[Michael]

While Google Tag Manager is a popular option, you can still track click links in GA4 by directly integrating custom event tracking into your website’s code. You can add an event listener for click actions tied to a phone number link and log these as custom events in GA4. Just make sure the linked phone number click is distinct and trackable as an event in your GA4 setup.

[Michael]

The issue you’re encountering with GA4, where long numbers are being displayed in an exponential format, likely stems from the way JavaScript handles large numbers. JavaScript uses floating-point arithmetic which is not suited for large integers and as a result, very large numbers often result in scientific notation when handled by JavaScript. This might be altering the format of your custom dimension.

A potential workaround may be to convert the numbers into strings before sending them to GA4. Alternatively, if you’re using these large numbers as unique identifiers, consider using a UUID (Universally Unique Identifier) generator that gives shorter string values.

However, please note that GA4 natively doesn’t support a 37 digit number as a distinct value. It officially supports a numeric value range of ‘±9.22*10^18’ for ‘event_bundle_sequence_id’ and ‘user_pseudo_id’. For ‘event_params’, the numbers’ limit is ‘±2^53’. This limit is set due to the floating-point double precision number limit in JavaScript.

You may want to re-consider the design of your event data structure and choose a more feasible way to represent your number.