etracker consent & tag manager
Why doesn’t the consent dialog need a reject button?
The user has all legally required selection options via the consent dialog, as provided in the etracker consent manager:
- Allow all by either clicking the Allow all button or by activating all purpose toggles and then clicking Allow selection.
- Reject everything (except necessary cookies) by not activating any further toggle and clicking directly on Allow selection.
Important: All toggles are only active in the preview to make the toggle color visible. Of course, the form in which all optional purposes are deactivated by default is displayed on the website. Users can therefore reject all unnecessary purposes with a single click. - Select and allow individual purposes by activating the desired purposes using the respective toggles and then clicking on Allow selection .
This means that only two buttons are required and users still have all the legally required selection options. As required by data protection law, these are all equally easy and quick to select and not “hidden” or “difficult” to find via additional layers.
Why does the debug mode always close when the page is changed?
This can happen if the addition of the parameter ?et_debug=1
does not result in a page reload. In this case, the parameter should be entered again and the current page reloaded.
Why are the variables not displayed correctly?
If the tag has not yet been triggered, the variables are displayed as {{ID}}
.
Why is “No trigger” displayed as the trigger?
The tag has either not yet been triggered or it is a global tag that is triggered on every page.
Why is no data visible in etracker or with a third-party provider even though tags have been triggered?
In debug mode, the tags are not executed and therefore do not generate any data. This allows the tags to be tested without consequences.
Why does the overlay not appear even though the parameter has been attached?
With this information, you are well equipped to use the new debug mode of the etracker tag manager effectively and to optimize tag implementations.