> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/google-tag-manager-setup/how-do-i-set-up-the-new-destination-tags-in-google-tag-manager.md).

# How do I set up the new Destination tags in Google Tag Manager?

This article walks you through converting the Google Tags in your GTM web container to the new Destination tags.

This article walks you through converting the Google Tags in your GTM web container to the new Destination tags. There are two situations: a container with server-side tagging via AdPage, and a container without server-side tagging. You don’t need to change your event tags, conversion tags or triggers.

#### Before you start

1. Create a new workspace, so your changes are kept separate from other work in your container.
2. Document all configuration parameters from your current Google Tags. This lets you copy everything over 1-to-1 and compare afterwards.
3. Also check your Datastream settings in the GA4 admin and in the Google Ads Data Manager. Think of excluded IP addresses, unwanted referrals and cross-domain tracking.

***

### Situation 1: container with server-side tagging via AdPage

{% stepper %}
{% step %}

#### Open your web container

Open your Google Tag Manager web container. Go to Tags in your container and click New.
{% endstep %}

{% step %}

#### Set up a new GA4 configuration

Under Tag Configuration, choose the new Google Analytics tag. Don’t choose the Google Tag, which is now listed under 'Other Google'.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FYgnjZWpuaEyqHvKvScps%2Fimage.png?alt=media&amp;token=2b42ca7d-a55d-49e0-a3e4-26b7baf6107f" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Configure the destination tag

Enter your measurement ID (G-...). This is the same ID as in your old Google Tag and probably set up in a variable.

Copy over all configuration parameters from your old Google Tag. The most important one is server\_container\_url with your own server-side domain. Without this parameter, your hits no longer go through your AdPage container. Copy the other parameters over 1-to-1, such as send\_page\_view set to false. If you use a configuration settings variable, add that as well.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2Fta9xV5He4xyYAoPY357P%2Fimage.png?alt=media&amp;token=ffdd2314-61a0-4814-9223-27bb91afdca7" alt=""><figcaption></figcaption></figure>

Save the tag with a clear name like "GA4 Destination - Server-Side".
{% endstep %}

{% step %}

#### Configure your other Google Tags

Do you also have a Google Tag for Google Ads (AW-...)? Repeat the steps above but this time select the new Google Ads destination tag. Copy over all configuration parameters here as well if you had them set up in your Google Tag.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FtyW036H5XfRRwXVt1Xsr%2Fimage.png?alt=media&amp;token=1d1275e7-e13d-4894-8330-13f7a83d84c3" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Pause the Google Tag tags

Pause the old Google Tags. Open the tag and choose Pause from the menu (⋮) in the top right. Don’t delete them yet, so you can easily go back.
{% endstep %}

{% step %}

#### Check your settings

Open the Settings menu and check that the settings match to the old way your GA4 Admin datastream and Google Ads Data Manager were set up.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FYo7w22EWzyNxW1X7P2k2%2Fimage.png?alt=media&amp;token=7223688d-c40a-4d48-aea3-c39f1dc3738c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Test the changes

Test your setup using preview mode. Open your preview mode in both the GTM web container as the GTM server container at the same time. Browse your website and check to see if the events still get sent towards the server container URL and if these events appear on your server container's preview mode.
{% endstep %}

{% step %}

#### Publish the GTM web container

After checking everything and testing the new setup you can publish your GTM web container with these changes. Before you do that you have the option to delete your old and paused Google Tag tags.
{% endstep %}
{% endstepper %}

***

### Situation 2: container without server-side tagging

{% stepper %}
{% step %}

#### Open your web container

Open your Google Tag Manager web container. Go to Tags in your container and click New.

{% endstep %}

{% step %}

#### Set up a new GA4 configuration

Under Tag Configuration, choose the new Google Analytics tag. Don’t choose the Google Tag, which is now listed under 'Other Google'.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FYgnjZWpuaEyqHvKvScps%2Fimage.png?alt=media&amp;token=2b42ca7d-a55d-49e0-a3e4-26b7baf6107f" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Configure the destination tag

Enter your measurement ID (G-...). This is the same ID as in your old Google Tag and probably set up in a variable. Copy over all configuration parameters from your old Google Tag. Save this new destination tag.
{% endstep %}

{% step %}

#### Configure your other Google Tags

Do you also have a Google Tag for Google Ads (AW-...)? Repeat the steps above but this time select the new Google Ads destination tag. Copy over all configuration parameters here as well if you had them set up in your Google Tag.
{% endstep %}

{% step %}

#### Pause the Google Tag tags

Pause the old Google Tags. Open the tag and choose Pause from the menu (⋮) in the top right. Don’t delete them yet, so you can easily go back.
{% endstep %}

{% step %}

#### Check your settings

Open the Settings menu and check that the settings match to the old way your GA4 Admin datastream and Google Ads Data Manager were set up.

<figure><img src="https://2963651437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5eC7lwaeygB0xx6AOZcE%2Fuploads%2FYo7w22EWzyNxW1X7P2k2%2Fimage.png?alt=media&amp;token=7223688d-c40a-4d48-aea3-c39f1dc3738c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Test the changes

Test your setup using preview mode. Open your preview mode the GTM web container. Browse your website and check to see if the GA4 event tags still fire and send event requests towards your GA4 destination and your Google Ads conversion tags still fire.
{% endstep %}

{% step %}

#### Publish the GTM web container

After checking everything and testing the new setup you can publish your GTM web container with these changes. Before you do that you have the option to delete your old and paused Google Tag tags.
{% endstep %}
{% endstepper %}

### Rolling back

Did something go wrong after publishing? Go to Versions in GTM, open the version from before the switch and publish it again. Your container will then work as it did before.

### Need help?

Would you rather not make the switch yourself? Email us at <support@adpage.io> and we’ll look at the options together. Good to know: making the switch and checking your site are not part of our standard support. We handle this with consultancy hours, which are billed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/faq/google-tag-manager-setup/how-do-i-set-up-the-new-destination-tags-in-google-tag-manager.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.