It takes far more work to migrate to GA4 than to “replace the old code to the new code.” Due to the fact that different types of data are being acquired in different ways, we advise tackling a GA4 conversion in phases.

This comprises, but is not restricted to:

• Pageview monitoring
• Tracking events, eCommerce, and cross-platform integration
• eCommerce Tracking
• Inter-platform Integration

In terms of a staged strategy, we advise:

Phase 1: Create a GA4 property that tracks pageviews and “standard” events as part of the first phase.

Phase 2: Implement KPI-related activities (e.g. form fills)

Phase 3: Implement e-commerce events.

Phase 4: Introduce further customised tracking (e.g. non-KPI events, custom dimensions, integrations)

Phase 5: Complete implementation audit and modifications as needed when data has been gathered.

After implementation is finished, GA4 will be operating alongside UA and will be available for you to report from if you choose.

Before transferring any reporting (including but not limited to custom reporting, dashboarding) from UA to GA4, we would advise collecting data from GA4 for at least a year.

An outline of the steps necessary to accomplish each phase is provided below.

Choose every applicable “standard” event tracking option for your website.

• Page Views
• Scrolls
• Outbound clicks
• File Downloads

Create a new “GA4 Configuration” tag that will appear on all pages if you’re using Google Tag Manager.

Add the GA4 gtag to all of your website’s pages if you’re hard coding.

You will start receiving some core data into your new GA4 property after this is configured.

 

In GA4, establish a new web property to start your migration. Either the Upgrade Assistant or the “+Create New Property” button in the admin section can be used to accomplish this. However, any specifics (that were once kept under action and label) are now decided by you as an event parameter. Event Name basically replaces “Event Category.” You have more flexibility now, but creating event tracking requires more steps than previously.

Choose the “core” events you must monitor, such as

• Clicks
• Submissions of forms Enquiries
• Web errors
• Downloads

If a goal was previously a “destination” goal, it must now be recorded as an event in order to be measured as a goal.

Determine the parameters required to help distinguish between each core event. Note: The parameter name must begin with a letter and only contain letters, digits, or underscores.

• Click Type (KPI, Nav, Text Link) (KPI, Nav, Text Link)
• Form Name (Contact Us, Job Application) (Contact Us, Job Application)
• Enquiry Method (Form, Email, Phone) (Form, Email, Phone)
• Error Message (page not found, invalid input) (page not found, invalid input)
• File Name: Q1 Performance Update 2020, Order Spreadsheet, File Type: PDF, MP3, DOC

Applied to Google Tag Manager:

• Use the selected event and parameter names to create a new “GA4 Event” tag.
• Use the triggers you’ve been using in the past, as well as any extra triggers necessary for brand-new occurrences.

To hardcode: adhere to the GA4 Event Measurement guidelines.

Create the events you wish to record in Google Analytics (either in admin or under Events > All Events).

You must add the names of the parameters you wish to track in Google Analytics under “manage custom definitions” for each parameter.

Now, all of the events you want to monitor ought to have been transferred to your new GA4 property.