If you are interested in performing a UA to GA4 Migration and are not sure which Apollo Tier is right for your needs please take our GA4 Migration Assessment.
Before You Begin
Ensure you are an account admin and have permission to publish in the GTM Container you are using (see this GTM permissions article from Google for details)
If you already have an Apollo account, follow the steps below to add a new property. If you are setting up a migration account for the first time, please start at www.apolloplatform.com/pricing to create a new account for the Migration version of Apollo.
Create a property name and select your tag manager.
In order to do a UA to GA4 Migration make sure to select Google Tag Manager from the drop-down.
Next under the property plan make sure to select Migration (Paid Plan).
Click here for a full list of our plans and pricing.
Once you select this it will begin the purchase flow. Once that is complete you will move to the next step. To continue migration, you must connect to your Google account on which you have permission to publish to the desired GTM container.
Now that you are connected to your desired Google account, you will see the green checkmark appear. If for some reason you clicked on the wrong account you can click the reconnect to google button under the drop-down arrow to select a different account.
Next to move forward select your existing GTM account, container and container version from the corresponding drop-down arrows.
After selecting the correct GA4 account, container and container version the blue import button will become available for use.
After performing the import you are now able to see the tags that they have pulled over sorted by alphabetical order.
You can also filter these tags by all, tags mapped and tags unmapped, or search for the tags that they desire to map.
Next, you will need to map your existing implementation.
Map Your Existing Tags to Apollo Events
Using the Apollo Event column, look for an Apollo event that corresponds to the tag you would like to import. For example, if you have a tag, Form Started, in your current implementation, a search for form in the Apollo Event dropdown shows various “form” related events available in Apollo. When you find a match, select it to map your current tag to the corresponding Apollo event.
Note: If there are “out-of-the-box”/platform built-in data points associated with your implementation, they will not be shown on the Map Existing Implementation screen. These are automatically mapped and included in your implementation.
Once you have selected a corresponding Apollo Event, the tag is enabled and the other options become available for configuration.
If the tag you are mapping requires the GA4 Configuration tag, then open the advanced configurations for your tag and check the box for Requires Config Setup Tag. The configuration tag defines attributes that will be sent with all tags that fire after it.
If you don’t find a corresponding event that matches the purpose of your existing tag, please reach out to the Apollo team who can help determine if what you are looking for already exists. Alternatively, you can click to create a new event within the Apollo Event dropdown.
Mapping the GA4 Configuration Tag
Apollo utilizes the Page Load Started event for the GA4 Configuration Tag, since the configuration tag fires at the start of every page before any other event tags. If you would like to map your existing GA4 Configuration Tag, simply select Page Load Started from the Apollo Event dropdown and continue mapping.
Map Your Existing GTM Tag Attributes to Apollo Event Attributes
To map the attributes associated with your tag, click the Configure Tag Attributes button. Doing so will open the the tag attributes configuration modal.
In the tag attributes modal, you will see a list of all of the attributes associated with the tag you are mapping. The name of the tag you are currently mapping is displayed in the upper left of the window. You will also find the ratio of mapped parameters to total parameters there. Additionally, you may filter the attributes list and search by Attribute Name.
Using the Apollo Variable Name column, look for the corresponding Apollo variable. Once you have selected the equivalent Apollo variable, your attribute will be enabled.
If you don’t find a corresponding variable that matches the attributes in your current implementation, please reach out to the Apollo team who can help determine if what you are looking for already exists. Alternatively, you can click to create a new variable within the Apollo Variable Name dropdown.
When you click to 'create a variable', you may choose to associate your tag attribute with a variable that already exists within Apollo:
Or you can create your own variable by providing Apollo with the appropriate GA4 configurations to create it:
When you have completed your configurations, click Save Changes in the floating footer. You must save your mappings before returning to the tag configuration view, or your changes will be lost.
Saving and Completing
To save the selections and updates you have mapped click the Save Changes button in the floating footer. If you exit or refresh the Map Existing Implementation module without saving, all unsaved changes will be lost. To undo any unwanted modifications since your last save, you may click Revert Changes in the floating footer.
Once this process is entirely finished, select All Mappings Complete.
Congratulations! You have finished migrating your existing UA implementation to your Apollo property.
The next step in the process is to begin the deployment phase of your analytics implementation. In the Deployment phase, you can automate creation of your GA4 configuration inside the the tag management system. You will notice after deployment, Apollo will have created all the tags to support your GA4 implementation and these tags leverage the GTM triggers and variables supporting your UA implementation which was mapped. You can learn more about this exciting next step below.