Analytics changes for GA4 and Ripple 2

Owned by Emma Cameron
Last updated: 29 Feb, 2024
2 min read

Major changes to analytics

Google Analytics now uses Google Analytics 4 instead of Universal Analytics. SDP is also moving to an updated version of its design system Ripple.

The following is happening to support this:

  • Ripple Shared Container: Introduction of a shared container— GA tags will be removed from the site's GTM container and re-configured in the Ripple container. All GA tracking will go into this container.

  • Universal Analytics will be deprecated: Ripple 2.0 does not support Universal Analytics tracking.

  • Changes to Improve GA4 Tracking: Enhancements aligning with the new Ripple 2.0 framework will lead to minor updates in GA4 conversions and audience conditions.

  • Migration to Single Digital Presence Analytics Account: Jellyfish will migrate the property to the Single Digital Presence analytics account and initiate the upgrade to GA360 if not completed earlier. For users currently holding access, your permissions to the property will remain unchanged.

Prepare for the changes

Check marketing activities

For sites upgrading to Ripple 2.0 and engaging in marketing activities, you’ll need to make sure you’re ready for the integration of Google Ads, DV360, CM360 and SA360 where applicable.

Google Ads integration details.

Connecting GA4 with Search Console

If you need Jellyfish’s assistance in connecting GA4 with Search Console and making the search console reports available in the report workspace, you’ll need to provide Jellyfish with Search Console Owner access.

Search Console integration details.

After launch of your Ripple 2.0 site/s

Jellyfish tasks

Jellyfish is working on the tasks below in the following order to ensure the transition is as seamless as possible:

  • post-live checks 

  • add new custom dimensions to GA4 property to reflect the improved Ripple 2.0 tracking

  • update audiences and conversions conditions where applicable

  • link to BigQuery, Google’s data warehouse that enables scalable analysis.

Once a substantial amount of data is generated, Jellyfish will proceed to update and validate the GA4 dashboard.

What should you do?

We recommend you do the following reviews:

  • your GA4 property, paying specific attention to conversions and audience collections

  • any marketing pixel collection if applicable.

If you come across any issues or have questions, please don't hesitate to log a ticket. Your insights play a crucial role in refining our approach.

Ongoing access and roles

The Ripple shared container

The Ripple shared container is responsible for tracking across every single SDP website using the Ripple 2.0 frontend. Any changes made to this container will impact every website. Due to this Jellyfish are currently responsible for all updates made to the Ripple shared container.

The Department of Government Services will also be charged extra money if usage and events in the Victorian government analytics account go over the specified amount. Due to this the number of GA4 tags in containers needs to be monitored.

Tracking custom events

If you wish to track custom GA4 events on your website please log a support ticket.

The SDP team and Jellyfish will provide advice on the best solution to implement the requested custom tracking.

 

 

 

 

Â