Observation: Configuration screens for tags have non-essential UI elements in the default shown configuration screens. The "Don't execute this tag when any of these triggers have been triggered" setting is visible in the non-advanced section for all tags.
Problem: While this can be handy when you know what you're doing and need this item, it makes the experience for first time users more complicated than it needs to be. This reduces overall usage of MTM, as people churn before getting familiar and happy with the product.
Context: The fire limit is also under advanced settings, and serves a similar purposed (reduce undesired/false-positive triggering of a tag). Moving the "Do not execute this tag when..." to the same section as the fire limit creates a logical grouping.
I'm keen to read some thoughts on this, including:
how often do you use the "Don't execute this tag when" setting?
did you think this added unnecessary complexity the first time you used MTM?
do you think it fits in a section with the fire rate limit?
do you often use fire rate limit + "do not fire when" together?
Observation: Configuration screens for tags have non-essential UI elements in the default shown configuration screens. The "Don't execute this tag when any of these triggers have been triggered" setting is visible in the non-advanced section for all tags.
Problem: While this can be handy when you know what you're doing and need this item, it makes the experience for first time users more complicated than it needs to be. This reduces overall usage of MTM, as people churn before getting familiar and happy with the product.
Context: The fire limit is also under advanced settings, and serves a similar purposed (reduce undesired/false-positive triggering of a tag). Moving the "Do not execute this tag when..." to the same section as the fire limit creates a logical grouping.
I'm keen to read some thoughts on this, including: