How to migrate to Stape?
Updated Sep 24, 2026
Migrating your server-side tracking to Stape means switching your hosting provider to Stape for your server Google Tag Manager (sGTM) container. You can easily make the move by exporting your server container configuration, redirecting your tracking requests to Stape, and shutting down your previous tagging server. Follow this guide for a clean cutover with little or no downtime.
Step 1 | Export and import the configuration in GTM
- 1.Go to the container you want to migrate, and click Admin tab → Export Container.
2. Choose the container’s version, and then click Export. You’ll get a .json file.
3. Create a new sGTM container in Google Tag Manager, copy the Container Config and save it for later.
4. Go to your new container, and click Admin tab → Import Container.
5. Click Choose container file and select the .json file you’ve downloaded. Choose the workspace and the import option.
6. Click Add to workspace. The configuration from the old container is now migrated.
Step 2 | Set up a new container in Stape
- 1.Create a new sGTM container in the Stape account and paste the container configuration that you’ve saved previously.
2. Add a new custom subdomain. Verify it, and add the DNS records in your hosting provider.
3. Go back to Google Tag Manager and open the web container. Update every place that sends data to sGTM (for example Google tag’s server_container_url, other tags, and webhooks) to the new tagging URL.
Step 3 | Test and publish
- 1.Test your setup in the Preview mode.
2. When the preview looks correct, publish the web and server containers.
3. Turn off the old tagging server so you don’t duplicate events.
Tip:
You can enable Stape features and power-ups that fit your setup. For example, we highly recommend the Custom Loader power-up that makes your tracking scripts more resistant to ad blockers and improves data accuracy. Take a look at the products offered by Stape.
Was this article helpful?
🍽 Table of content:
Comments