Instead of setting up a tag manually you can import a container containing the tag.
It may seem unnecessary in relation to the size of the task, but sometimes tags contain details that are easy to miss, and therefore importing a container can be a safer way to get the job done.
Start the import by going to Admin and clicking Import Container:
- Select the container file
- Select the workspace
- Use the merge option or your existing container will be deleted
- To be on the safe side you can choose to rename conflicting tags, triggers, and variables
- Go through the preview section and review the changes
- Confirm the import.
Importing a server container
If GTM Kit generated a server container file (the server-side selections in the Template Assistant), import it into your server container in Google Tag Manager, not the web container. The steps above are the same.
If your server container’s GA4 client uses Server Managed cookies, tick Migrate from JavaScript Managed Client ID in the client’s settings. Without it, purchases that GTM Kit recovers on the server land on a Google Analytics user with no session, and their traffic source shows as (not set). The server-side purchase webhook explains why and how to check it.
If you use GTM Kit’s server-side webhooks and imported your server container before September 2026, generate it again and re-import it: the GA4 webhook tag in older templates records order status, refund and subscription webhooks as extra purchases.
When you import a container from somebody else you usually have to make some changes or fill in some details. For example, you may have to fill in your own Google Analytics 4 measurement ID.