The Google Ads tag is created in Adobe Data Collection but the campaign attribution isn't correct

4 replies
734 views
Translate

The Adobe Launch tag is created but it seems like Google Ads and Tag Manager isn't connceted. The 'Tag Name' doesn't appear in GTM Preview Mode. Although, the Gtag extenesion is used in Adobe Launch for Google Analytics.
Can the team help in the connection of the two platforms?

FarazHusainAccepted solution

Employee

This is expected behaviour when combining Adobe Launch + gtag.js instead of using GTM I believe. GTM isn’t broken — it's just telling you: "I see a Google tag fired, but I didn't fire it!" and Adobe Launch is doing its job — it’s firing the gtag() calls.
When tags like gtag('config') or gtag('event') are triggered outside of GTM (e.g. from Adobe Launch), GTM’s Preview/Debugger mode cannot identify them as GTM-managed tags. You can keep using Adobe Launch – ignore the “Unknown” label in GTM or migrate Google tags to GTM for clearer tag control and easier debugging.

FarazHusainAccepted solution

Employee

This is expected behaviour when combining Adobe Launch + gtag.js instead of using GTM I believe. GTM isn’t broken — it's just telling you: "I see a Google tag fired, but I didn't fire it!" and Adobe Launch is doing its job — it’s firing the gtag() calls.
When tags like gtag('config') or gtag('event') are triggered outside of GTM (e.g. from Adobe Launch), GTM’s Preview/Debugger mode cannot identify them as GTM-managed tags. You can keep using Adobe Launch – ignore the “Unknown” label in GTM or migrate Google tags to GTM for clearer tag control and easier debugging.

Translate

Jennifer_Dungan

Level 2

This is correct... GTM Preview Mode is only for the actual GTM implementation.. connecting the tags, triggers and variables created in the Google Tag Manager into their own debugging tool.

While the gtag files use the gtm domain, this is still very different... the tracking is being fired, but the architecture which is driving the values is different. The GTM Debugger knows nothing about what is driving the tracking. It would also be the same if you added custom JS directly onto your website, and set the values manually and used the gtag code to initiate the tracking.

If you are using Adobe to do your tracking, you will have to use other testing tools, like turning on Satellite Debugging in the console to see the rules that are fired.

// Turn on Debugging
_satellite.setDebug(true);

// Turn off Debugging
_satellite.setDebug(false);

And for seeing the actual calls, you can use the Network panel of your browser, or maybe a tool like Omnibug.

Translate

UjjwalChandraAuthor

Level 2

Thanks @farazhusain and @jennifer_dungan for the clarification.

Translate

Sign up

Login with SSO

Login to the community

Login with SSO