[Aiden]

This sounds like a problem of data syncing between Google Tag Manager and Google Analytics 4. Ensure that the ‘userId’ is defined correctly in GA4 as well, not just in GTM. Sometimes, data you see in the debugger doesn’t reflect in GA4 reports because it might not be configured correctly in GA4. Double-check the configuration settings and maybe wait a little because GA4 sometimes takes a while to reflect this data.

[Aiden]

With GA4, you’re effectively starting a new data collection stream independent of Universal Analytics. So, GA4 will continue to collect data even if UA stops. However, concerning your old analytics.js code – GA4 uses a different measurement model (gtag.js) and doesn’t support the old UA (‘analytics.js’) code. GA4 properties use a different type of tracking ID, so you’ll have to replace the old one. Despite the changes, don’t worry about your data – when UA stops collecting data, it isn’t deleted. It will still be accessible until the property is deleted.

[Aiden]

Sure, I’d be happy to help you out! This might actually be a pretty straightforward fix. Here’s what you can do:

1. Let’s start with adding a Custom Definition. You can find how to do this using this reference link:
   Custom Definition

2. Next, you’ll want to add a Data Exploration. Check out this handy reference for that:
   Data Exploration

And that’s it! Let’s give that a try and see if it solves your issue. If there’s anything else you need, just let me know. All the best!

[Aiden]

Sure, what your team is saying is indeed possible. When a mobile app is built with web tech, as described, it’s possible to use the same analytics setup as you would for a website. Debugging such an app typically involves using your computer’s browser, connecting your phone to your computer, and enabling certain settings that let your computer’s browser interact with the app. The exact details should be provided by your developers.

The main challenge could be with using the GTM preview debugger due to the unconventional setup. However, you can work around that by publishing the container to a lower environment in GTM and then test by simply viewing raw network requests or using an extension like Adswerve’s datalayer inspector in the dev console. Keep experimenting and you should be able to see the results you’re looking for.

[Aiden]

Sure thing, happy to help! You’re absolutely okay mixing and matching v1 and v2 data layer variables in your GTM container. You’d typically choose depending on the structure of the objects you’re pushing.

While v1 is a little more limited – it can only handle flat data structures and doesn’t offer recursive merging of complex objects. In your case though, where you’re handling simple info like first names, last names, and phone numbers, these limitations probably won’t cause any headaches.

If you want to dive deeper into differences and use cases for v1 and v2, check out this nice article. But don’t sweat it, for your application it sounds like either version should do just fine. Happy data pushing!