ScriptTagFilter behavior

[vikramshrowty]

I can't find documentation on script-tag but from looking at the code I'm guessing that you're supposed to modify your script type to be 'text/plain' instead of 'text/javascript' and then cookieconsent will restore it to javascript if there is consent.

If so, is there a reason this is done differently from dynamic-script? Seems like it would be easier for the user if the same mechanism was used in both places?

[nklido]

@vikramshrowty
I didn't find any documentation either but looking through the code basically script-tag filter
expects you to set your scripts that need to be blocked with type="text/plain" and data-consent="your-script-keyword"

for example

<script type="text/plain" data-consent="googletagmanager">
  // tag manager code here
</script>

and then at the CookieConsent config

services: {
  google_tag_manager: {
    category: 'marketing',
    type: 'script-tag',
    search: 'googletagmanager',
    language: {
    locale: {
        en: {
          name: 'Google tag manager'
        }
      }
    }
  }
}

ScriptTagFilter will run when the page loads and will enable the scripts that match the search keyword
only if the marketing cookies are accepted.