Do not block the push-opt-in!
For Web and Wallet Push, the browser or the operating system controls the consent of the users to receive notifications and the setting of cookies in case of consent. The integration of Signalize into Consent Management Solutions (CMPs) is therefore not only unnecessary, but also carries risks. Depending on the CMP, this can erroneously lead to the blocking of the execution of the Signalize code and thus the blocking of the push consent.
Therefore make sure that the Signalize Code is integrated in all pages as described here and not in the consent banner, so that the corresponding opt-in invitation is not blocked.
What to consider when Signalize interacts with the most common consent solutions is described below.
If Signalize is integrated via the compatible etracker tracking code, please note these instructions.
Usercentrics
Follow the instructions for the Usercentrics implementation. An adjustement of the Signalize code is not necessary.
Cookiebot
Follow the instructions for the Cookiebot implementation. The Cookiebot script can be implemented in automatic or manual mode.
Then integrate data-cookieconsent=”ignore” as a further attribute in the Signalize code, to avoid deactivating the Signalize code in auto mode. Please do not make any further changes to the Signalize code and especially leave the type at “text/javascript”!
<!--Copyright (c) 2000-2020 etracker GmbH. All rights reserved.-->
<!--This material may not be reproduced, displayed, modified or distributed-->
<!--without the express prior written permission of the copyright holder.-->
<!--Signalize Code 5.0-->
The data-secure-code “ABCDEF” has to be replaced by the personal account key.
Consentmanager.net
Follow the instructions for the consentmanager.net implementation. The consentmanager.net script can be implemented in automatic or semi-automatic mode.
Then integrate data-cmp-ab=”1″ as a further attribute in the Signalize code to avoid deactivating the Signalize code in auto mode. Please do not make any further changes to the Signalize code and especially leave the type at “text/javascript”!
<!--Copyright (c) 2000-2020 etracker GmbH. All rights reserved.-->
<!--This material may not be reproduced, displayed, modified or distributed-->
<!--without the express prior written permission of the copyright holder.-->
<!-- Signalize Code 5.0-->
The data-secure-code “ABCDEF” has to be replaced by the personal account key.
OneTrust CookiePro
Follow the instructions for the OneTrust CookiePro implementation. An adjustement of the Signalize code is not necessary.
Borlabs Cookie
Follow the instructions for the Borlabs Cookie implementation. An adjustement of the Signalize code is not necessary.
