Add Namespace Convention to Avoid Tag Name Conflicts Between Matomo Official Tags and Tag Manager Extended Community Plugin

[Chardonneaur]

Hi Team,

This is an important issue.

Steps to reproduce

• Have the last version of Matomo (5.2.0)
• Update the Tag Manager Extended community plugin (on-premise).
• Use the Axeptio community tag.

What I got:

• The Axeptio community tag, even though it is more recent than the offcial Axeptio Matomo Tag.

What I expected instead:

• A namespace convention should be implemented to avoid tag name conflicts, allowing both Matomo official tags and community plugin tags to coexist without overriding each other.

Who asked for it?

• Ronan Hello, developer of the tag manager extended community plugin

add-namespace.mp4

[Stan-vw]

Thanks for the clear video. We're shipping a fix shortly.

[Chardonneaur]

Thank you.

[AltamashShaikh]

Adding a fix was more complicated in TagManager plugin, I have created a PR in TagManagerExtended plugin to filter out the newly created tags by TagManager plugin.

[Stan-vw]

@ronan-hello just following up on this: I understand it's working now, but let us know in case there's anything that's still going wrong. We appreciate the awesome work you're putting into MTM Extended.

[Stan-vw]

btw I've closed this because I believe the immediate issue of this ticket was "there's currently a tag that doesn't work", which was fixed.
However, we've created a new ticket for the "long term" fix for a better Namespace convention: #963

[ronan-hello]

Hi @Stan-vw, thank you so much!
Yes, this issue is now fixed 👍