WooCommerce plugin has been released on WordPress.orgView plugin →

Move from Stape to TagLinc

4 min readUpdated Nov 15, 2026

If your server GTM container runs on Stape today, you can move it to TagLinc without rebuilding anything. Your tags, triggers and variables live in your own Google Tag Manager account, not at Stape. TagLinc runs the same server container, so you only change where it is hosted.

Keep your current tracking subdomain (for example data.yourstore.com) and the switch is one DNS record. You don't touch your web container or your website, and there is nothing to publish.

Before you start

    You need
  • A TagLinc account (create one).
  • Access to the Google account that owns your GTM server container, or its container config (how to get it).
  • Access to the DNS settings of your tracking subdomain.
  • Keep your Stape container running until the move is done. Cancel it only after you see traffic on TagLinc.

Step 1: Create the container on TagLinc

  1. Open Server GTM Containers and choose Add container.
  2. Under Connect your GTM server container, choose Connect Google and pick the same server container you use on Stape. Do not create a new one. If you can't connect that Google account, choose Set up manually and paste the config from Admin → Container Settings in Tag Manager. It is the same string you gave Stape.
  3. Pick the region closest to your visitors, choose a plan and deploy. See Deploy Your First Server GTM Container.

Wait until the status reads Running. Your container now runs on both Stape and TagLinc, but visitors still go to Stape.

Step 2: Turn on the same Power-Ups

If you used Stape power-ups, turn on the TagLinc ones that match on the container's Power-Ups tab before you switch DNS:

On StapeOn TagLinc
Custom LoaderCustom Loader (see "If you use the Custom Loader" below)
Cookie KeeperCookie Keeper
User IDUser ID
Click ID RestorerClick ID Restorer
GEO HeadersGEO Headers
Bot Detection, Preview HeaderBot Detection, Preview Header

The full list is in Server GTM Power-Ups: All 13 Explained.

Step 3: Switch your tracking subdomain

  1. Open the container's Domains page. Under Add your own domain, copy the CNAME value it shows.
  2. At your DNS provider, find the record for your tracking subdomain (for example data). Delete Stape's record for that name, whether it is a CNAME or A records. Then add one CNAME with the value you copied. On Cloudflare, set it to DNS only (grey cloud).
  3. Back on the Domains page, type the full subdomain (data.yourstore.com) and choose Check and add. TagLinc issues the HTTPS certificate automatically.

That's the whole switch. Your Google tag still sends to https://data.yourstore.com, which now reaches TagLinc. Details and error messages are in Custom First-Party Tracking Domains.

A short gap is normal. While DNS changes over and the certificate is issued, some requests can fail for a minute or two. Do the switch at a quiet hour. If you need no gap at all, use the next option instead.

Option: a new subdomain, with no gap

Add a new subdomain (for example s.yourstore.com) on the Domains page while Stape keeps serving the old one. Then, in your web GTM container, set server_container_url on your Google tag to the new address and publish. See Connect Web GTM to Your Server Container. This takes about five minutes, with one publish.

If you use the Custom Loader

Stape's Custom Loader puts its own script address in your website's GTM snippet, and TagLinc's loader uses a different one. After the switch, replace the snippet on your website with the one from the Custom Loader Power-Up in TagLinc. Without the Custom Loader, the standard GTM snippet stays as it is.

Check your server tags

Most tags (GA4, Meta Conversions API, TikTok, Google Ads) work unchanged. Check two things:

  • Stape-only templates, such as tags that write to Stape Store, call Stape's own services. Replace them, for example with TagLinc's Data Store, or remove them.
  • Headers with Stape in the name. If a variable reads a header such as X-Stape-User-Id, change it to the TagLinc header shown on the Power-Up (for example X-Taglinc-User-Id) and publish the server container.

Check that it works

  • Open your site with GTM Preview, or check the Network tab of your browser's developer tools. Requests such as /g/collect to your tracking subdomain should succeed.
  • On paid plans, the container's Event Logs show the requests as they arrive. See Using Event Logs and Analytics.
  • Check that the Stape container's traffic has dropped to zero. Then cancel it.

Something not working? See the Server GTM Troubleshooting Checklist.

Was this guide helpful?
Thanks, that helps us improve the docs.
Still stuck?

Open a support ticket from your dashboard and include the container name.

Contact support