Sometimes a script is loaded from an external source.
Example of an external script loaded using the src attribute.
To block or allow external scripts to be loaded and setting cookies we need to use two custom
attributes handled by js library:
- data-consent-src which keeps the src of the script to be executed, and
- data-category-consent which keeps the label of the category (i.e.:
'cookie_cat_marketing').
Also, we need to leave the src attribute empty. So, in fact, we have to move value from 'src'
attribute to 'data-consent-src'.
Review an example of a transformed external script to enable it to be managed by the SDK presented
below:
Example scenarios (above script):
The visitor wants marketing cookies to be set in his/her browser:
- visitor agrees on setting marketing type cookies (cookie_cat_marketing)
- website loads
- js library finds the script
- js library fires script with src="http://example.marketingscript.com", because it has
the data-category-consent attribute set to the category that he/her agreed on - the request fires–marketing cookie from this initiator can be set in visitor's browser
The visitor doesn't want marketing cookies to be set in his/her browser:
- visitor disagrees on setting marketing type cookies (cookie_cat_marketing)
- website loads
- js library finds the script
- js library blocks request (http://example.marketingscript.com), because it has
the data-category-consent attribute set to the category that he/her disagreed on - the request doesn't fire–marketing cookie from this initiator can't be set in visitor's browser
Other examples:
Now:
We categorize above element as a one that sets statistic cookies. After enabling the Cookie Control SDK this element should be changed to:
In this way, js library will handle allowing and blocking this initiator.
By default, there are 5 basic cookie types:
- cookie_cat_necessary
- cookie_cat_functional
- cookie_cat_statistic
- cookie_cat_marketing