[Bug] Google Ads: Conversion Tag prevents debugger from showing Tag/Triggers correctly

[goochj03]

In Matomo cloud, when creating a Tag type of Google Ads: Conversion, if the Trigger for this Tag is set to 'Page View' and that same Trigger is used by another Tag already, the preview tool seems to not display correctly.

Tag Type:

For example, the below Tags both share the same 'Page View' trigger.

When using the debugger tool, no Tags or Triggers are shown.

If a separate page view trigger is created and assigned to the Google Ads: Conversion Tag, the debugger then loads correctly.

[snake14]

Hi @goochj03 . Thank you for taking the time to create this issue and providing good image examples. I was able to reproduce the issue and noticed an error in the JS Console:

That made me think of the warning that the tag was dependent on gtag.js:

I configured a tag of that type, on the same Pageview trigger:

Once that was done, things started working again and all of the tags executed as expected.

[AltamashShaikh]

@Stan-vw @snake14 We had this description, when we created the tag, but we no more show any inline help for the description and hence it lead to this issue, may be we should mention as an inlineHelp in the name for now ?

"GoogleAdsConversionTagDescription": "Send an event to track conversions. This tag requires Google Tag (gtag.js) tag to be configured.",

[Stan-vw]

I think it's pretty easy to miss the text about the requirement at the moment, as it's only shown as a subtitle in the one-off creation process.

To solve this lack of clarity, maybe we should

1. add it as an inline helptext in the create/edit screen (as @AltamashShaikh suggests), and
2. add a yellow/red banner on the container dashboard & manage tags screens when someone has the Google Ads Conversion tag but not the required Google Tag to make it work. That way, even when they're not in a create/edit screen, they will see what is wrong with their setup.

@AltamashShaikh what do you think, is that a good solution or do you see better solutions?

[AltamashShaikh]

@Stan-vw We just discussed this and we should add the description as inlineHelp and we should check if gtag is defined so that, no error is thrown and the code works as expected.

[9joshua]

@goochj03 I just saw this with another user even though they added the gtag.js script. This is because the Google Ads Conversion tag fired before their gtag script had initialised. Adding a 1 second 'Fire delay' to the tag solved this issue.

@AltamashShaikh
Adding this prior to calling the gtag() function might be a solution?...

  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}

without this:

with:

[AltamashShaikh]

@9joshua Thanks for the suggestion, we can check if adding window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} is better in comparison to check if gtag is defined, during the fix.