Migrating to GTM destination tags: the Digital Peax walkthrough

SarpSarp · · 3 min read
Two charcoal metal sections joined by an orange sleeve on ivory paper, with an unused section behind them.

We migrated Digital Peax’s GA4 and Google Ads connections to destination tags, bringing both product connections and their shared settings into the GTM container.

A destination is the Google product receiving the data. In our setup, these were a GA4 web data stream and a Google Ads account. Google’s definition

Actual Digital Peax GTM Overview showing the container connected directly to Google Ads and Google Analytics.
Digital Peax’s Overview map after migration. Click any screenshot to view it at full size.

1. Choose which Google tags to migrate

Identify the Google tags you want to turn into destination tags. At Digital Peax, we chose GA4 - Config and the Google tag connecting Google Ads.

2. Open migration from an existing destination

In the Overview map, we opened the existing GA4 destination and selected Get started. If your container displays the Optimize your Tag Manager container banner, you can also start through Review details.

Use the optimization flow to migrate existing connections. Add destination creates another connection.

3. Review tags, shared settings and access

We selected both Google tags. Their shared settings matched, so we carried those values across. If settings conflict, decide which values should apply before consolidating them.

Review external account access separately. It determines access to the GTM container from other Google product accounts; data connectivity and user access are separate choices.

Select Preview changes, review the differences, then choose Add to workspace. This stages the changes without publishing them. Google’s optimization workflow

Actual Digital Peax GA4 destination tag configuration showing the Google Analytics tag type and the existing Measurement ID.
The migrated GA4 destination tag. The Measurement ID continues to point to the same web data stream.

4. Check Settings

At Digital Peax, the tag types became Google Analytics and Google Ads. Our existing Manage automatic event detection and Allow user-provided data capabilities settings moved into the shared Settings section.

Before changing a shared setting, check which destinations it affects. Settings and destination management

Actual Digital Peax GTM Settings showing both destinations as Optimized Yes, current external account links as Linked, and shared settings below.
The current Digital Peax Settings panel. Both destinations show Optimized: Yes. External account links are managed separately.

5. Test and publish

Use Preview to connect the site to Tag Assistant. Check destination IDs, tag execution and outgoing events. For Digital Peax, we verified page_view and generate_lead.

We then published through Submit → Publish and Create Version. You can return to a previous container version, but permissions are not versioned and need a separate review. Preview guide · Publishing and versions

Which tag should a new setup use?

For GA4, follow Tags → New → Tag Configuration → Google Analytics → Google Analytics. For Google Ads, select Google Ads → Google Ads. Adding another event to an existing destination does not require another destination tag. GA4 setup · Google Ads setup

We can help with the migration

We can review your GTM setup with a free audit, then implement and test the migration for you. Get in touch with Digital Peax.

Sarp
Written by
Sarp Founder, Digital Peax

Sarp founded Digital Peax and sets its direction, sitting on the hardest client accounts himself. He also builds Odaq, the AI platform behind the agency's work. His background is in insurance, a field where a wrong number has real consequences, and it shows in how he treats measurement, tracking, and attribution.

Keep reading

All notes ›
Newsletter

The Peax Brief

Practical notes on paid media, search, analytics, and AI. Get the next issue in your inbox.

Ads, journey, conversion.Let’s talk about yours.
Book a free strategy session