etracker consent & tag manager
Why does the consent dialog not offer a selection option for individual providers?
The consent dialog provided in the etracker consent manager offers a consent and rejection function at the highest level, as required by the supervisory authorities.
At the same time, the Consent dialog offers a granular selection of purposes at the top level.
“Regardless of whether it is then possible to consent to or reject all purposes via one action, end users must then also be able to consent or reject them separately.” (Guidance of the supervisory authorities for providers of digital services (OH Digital Services) version 1.2, para. 52)
Individual purposes can be activated via the toggles. This means that only the purposes that are activated via the toggles are clearly permitted or the purposes whose toggles are inactive are rejected.
The user therefore has all the legally required selection options at the top level:
1. Allow all by either clicking on the Allow all button or by activating all purpose toggles and then clicking on Allow selection.
2. Reject all (except necessary cookies) by not activating any further toggle and clicking directly on Reject all.
3. Select and allow individual purposes by activating the desired purposes using the respective toggles and then clicking on Allow selection.
It is not necessary to select individual providers. However, it is mandatory to provide information about the individual providers. This can be done on a special subpage, which is then referred to via a link from the consent dialog.
The information for providers can look like this, for example.
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?
The display of the overlay is probably blocked by so-called CSP headers. In this case, a website admin must add *customer.etracker.com* to the CSP headers.