Manually blocking services prior consent

Once you've implemented the Usercentrics script you'll need to ensure that Data Processing Services don't load until consent has been given.
You can do this by adding markup to the elements that load these services. This process is similar, but slightly different for scripts, and images and iframes.

Scripts

To ensure a script is fetched without executing you have to set the type to "text/plain". This will essentially tell the browser that the script is just text and shouldn't execute it.
To allow the Usercentrics script to determine whether the service should be loaded (or remain blocked) you need to add the data-usercentrics attribute with the exact name of the data processing service as it's listed in the Usercentrics admin interface.

For example:

The original script:

<script type="text/javascript" src="https://tracker.com/script.js"></script>

With markup applied:

<script
  type="text/plain"
  src="https://tracker.com/script.js"
  data-usercentrics="Example Tracking Solution"
></script>

Images and iframes

To ensure an image or an iframe doesn't track your visitors without their consent, you need to replace the src attribute with data-src. This ensures that the resource isn't actually fetched, but the link is stored in the data attribute, so the resource can be fetched and loaded once consent is given.

To allow the Usercentrics script to determine whether the service should be loaded (or remain blocked) you need to add the data-usercentrics attribute with the exact name of the data processing service as it's listed in the Usercentrics admin interface.

For example:

The original pixel tracker:

<img src="https//tracker.com/pxl/1.gif" width="1" height="1" alt=""/>

With markup applied:

<img
  data-src="https//tracker.com/pxl/1.gif"
  width="1"
  height="1"
  alt=""
  data-usercentrics="Example Tracking Solution"
/>