Digital Peax 
There’s a new tag type in GTM: the destination tag. It connects your GTM container to Google products such as GA4 or Google Ads and sends data directly to them.
For us, this is one of the most exciting and useful GTM updates in a while. These connections no longer need a separate gtag.js layer. That means less JavaScript to load, with destination connections and settings managed inside GTM. Google’s announcement
We’ve migrated Digital Peax’s own GTM container, carrying across our GA4 and Google Ads connections with their existing shared settings.
What changes in daily work?
For marketing teams, the practical gain is simpler maintenance. Seeing where data goes and where shared settings live makes the setup easier to review and hand over between an agency and an internal team.
| Area | Before | With destination tags |
|---|---|---|
| Google product connection | Through a Google tag loaded by GTM | Directly from the GTM container |
| Shared settings | In Google tag settings | In GTM’s Settings section |
| Existing events | Event tags and triggers | Preserved during migration |
Do existing tags need rebuilding?
Usually, no. The migration converts existing Google tags into destination tags while preserving event tags and triggers. The resulting setup still needs testing before publication. Google’s migration guide
Use a destination tag when connecting another Google measurement product. When adding an event to an existing GA4 destination, continue using an event tag.
Our technical migration guide walks through the panels we used for Digital Peax.
Let’s review your GTM setup for free
Our free GTM audit reviews your tags, destination connections and shared settings. We can then plan and implement the migration, test the setup and manage publication. Get in touch with Digital Peax.
