The Google Tag Manager has established itself as the de facto standard for the integration of tracking scripts. In this way, on the one hand, responsibilities (online marketing vs. programming) are clearly separated and, on the other hand, you can quickly set up and modify tracking via an additional deployment channel. Here are two little tips for setting up triggers.
when creating triggers, you often choose the option "match CSS selector" as trigger type. for example, if you enter the value .foo .bar .button, it often happens that the trigger does not trigger reliably. the reason for this is usually that other html elements (for example <span> elements for additional styling) can be hidden within the button element. if you then click directly on these child elements, the trigger is not triggered - the event is not propagated upwards in the DOM hierarchy (not bubbled). to work around this, repeat the selector and add the universal selector "*". in our example, the entire expression is .foo .bar .button, .foo .bar .button *.
As a second tip, since iOS 10.2 (up to the current version) there is an annoying behavior in the Safari browser: If you track mailto: links, under certain circumstances the following message appears after tapping on the link:
Here the trigger type " Click - Links only " was activated with the option " Wait for tags ". This delays the activation of the actual link target, which leads to the aforementioned message. After disabling the option, the problem no longer occurs. Alternatively, you can also use the trigger type " click - all elements " and specify the target as precisely as possible as a link using the CSS selector.