Learn business growth with Google Analytics 4 Forums Google Analytics 4 Transitioning to GA4: Compatibility of analytics.js based UA-XXXXX code after migration?

  • Transitioning to GA4: Compatibility of analytics.js based UA-XXXXX code after migration?

    Posted by Li on 5 October 2022 at 10:14 pm

    So, I’ve got each of our UA accounts switched over to a shiny new GA4 account, right? But the thing is, we’re still rocking the old UA-XXXX code, which is based on this analytics.js source code. Come July of 2023, will we still receive data on these new GA4 accounts we’ve got linked up? Or, do we need to put things into gear and go ahead with updating our core code to include the new G-XXXXX code, running off that gtag.js snippet? Of course, we’ve also got the option to take our sweet time with this migration, doing it bit by bit when we can.

    For what it’s worth, I’ve already got the GA4 linked to my old UA and data is flowing in as we speak. What are your thoughts?

    Lucas replied 1 year, 4 months ago 3 Members · 2 Replies
  • 2 Replies
  • Lucas

    Member
    21 December 2022 at 4:12 am

    Currently, Google recommends using both tracking codes (UA-XXXX and G-XXXXX) simultaneously as it allows data to flow into both the Universal Analytics (UA) and the new Google Analytics 4 (GA4) properties. If you’ve linked your old UA to GA4 and data is flowing, you’re on the right track. However, Google has announced that it will stop supporting UA in July 2023. After that, no new data will flow into UA properties, but your old data will still be accessible. Therefore, it is advisable to start migrating to the new GA4, by updating your website code to include the new G-XXXXX code. The speed of this migration is up to you; it can be done in your own time, but should ideally be completed before July 2023 to avoid any disruption to your data collection.

  • Lucas

    Member
    11 May 2023 at 1:45 pm

    Yes, it would be best to prioritize updating your website’s core code to include the new G-XXXXX code; this is because Google plans to sunset the Universal Analytics (the UA-XXXX you’re referring to) and it’s being replaced by Google Analytics 4 (GA4). Even though your UA data is still flowing to GA4 for now, it’s not clear how long this support will last; hence updating to the new GA4 property ID is advisable. As per the transition, there’s no rush as Google also offers dual tracking to use both GA4 and UA till you fully migrate. It would be ideal to make this transition gradually and get accustomed to the new interface and data model of GA4.

Log in to reply.