Ecommerce migration helper

The ecommerce migration helper can assist with the following:

Review the Help section to learn more about the Purpose of the tool, How to use the tool, or to send Feedback.

Enter details about your current implementation

To run an analysis, select which library your current implementation uses and provide an ecommerce event snippet to analyze. For detailed instructions see How to use the tool.

1. Which library does your current ecommerce implementation use?

2. Provide an ecommerce event to analyze.

Replace the default example below with the ecommerce event data you want to analyze and click Analyze. The event data should be copied from your existing ecommerce implementation. For additional help see How to use the tool.

Google Analytics 4 Measurement ID:
Universal Analytics Property ID:

Results of analysis


Identify the library and version of Google Analytics for the event above.

Pending analysis...


Use the following information to confirm how the event above is interpreted by various libraries and tag configurations.

Google Analytics 4

For the following configurations:

Your event above would be interpreted as follows:

Universal Analytics (GA4 support enabled)

For the following configurations:

Your event above would be interpreted as follows:

Universal Analytics

For the following configuration:

Your event above would be interpreted as follows:

Recommended GA4 event

To send your event above as a GA4 event use the following command:


Purpose of the tool

To simplify the transition from Universal Analytics to Google Analytics 4, ecommerce events and parameters for UA and GA4 are compatible in most, but not all, cases. Review the guides available on the GA4 upgrade center for details on compatibility and the pros/cons of various upgrade options.

The ecommerce migration helper can be used to clarify the compatibility of an event with various library/API and tag configurations. It helps with the following:

  1. Identify which version and API/library is used to send the ecommerce event to Google Analytics.
    • It will attempt to identify whether the event is Universal Analytics, or Google Analytics 4 and which tagging solution was used.
    • Why?: Identify your current implementation, if you're not sure.
  2. Validate how your implementation is interpreted by Google Analytics tags in Google Tag Manager.
    • How the event is interpreted by various tag configurations. For example, if the event you provide is a UA purchase event sent using the Data Layer the tool can show how that event and associated parameters map to the equivalent GA4 event.
    • Why? (1) confirm your ecommerce eventsĀ are well-formed and (2) understand how data maps to equivalent parameters (or doesn't) when sending GA4 events to a UA property or sending UA events to GA4 property.
  3. Recommend how to transition the event to an equivalent GA4 event.
    • Why? To assist with transitioning the your implementation to the recommended GA4 format.

How to use the tool

Enter details about your current implementation

Configure the tool by selecting which library/API you're using to send ecommerce data and provide the details of the ecommerce event you want to analyze. Note: The tool is preconfigured with a default example for both the dataLayer.push API and gtag API cases.

Results of analysis

The Identification section attempts to identify the library/API used to send the ecommerce data and the Google Analytics version for which the data is formatted.

The Validation section shows how the event is interpreted for various Google Analytics configurations.

The Recommended GA4 event section attempts to generate the corresponding GA4 event for the provided event.


Analyze the default gtag.js example, a purchase event using the gtag API, the results are as follows:

Feedback / Report an issue

To view open issues, send feedback or report an issue, see ecommerce-migration-helper.