By default, Full Picture’s Cookie Notice can manage tracking tools:
- Installed with Full Picture’s integration modules
- Installed with the “Custom Scripts” module
- Installed with other plugins and managed with the “Scripts Manager” module
In this article, we will concentrate on the third method.
How does it work?
Full Picture can manage tools installed by other plugins. It does it by:
- blocking the scripts that install these tools
- loading these scripts when and where it is necessary
How Full Picture knows what scripts to block?
You need to tell it.
Here’s a video which explains how to do it.
Overview of the Scripts Manager module settings
The screen below presents a group of settings from the “Scripts Manager” settings page.
This group is responsible for blocking a single script, but you can have as many groups like that as you want.
Let’s see what these fields do.
- Give the script a name (for your information only).
- Choose whether Full Picture should block scripts by their:
- filename (e.g. supertrack.js),
- URL (https://example.com/superanalytics/supertrack.js)
- URL part, e.g. (example.com)
- or unique content of the script tag (e.g. UA-12312323-1)
- Enter the searched URL, name, or part of content.
- Specify the purpose of the tracked data. This information will be used to load this tool only to visitors that agree to certain types of cookies (if they live in a country where they need to opt-in to them).
- Script ID – a unique name that is used by FP for various purposes. This ID is also viewable in
- Choose where this script should load (these fields are only visible when the geolocation module is enabled).
- Disable the management of this script – this option can be used to temporarily test the original script without having to remove the scripts settings from full Picture’s settings panel.
- Add another script or remove the current one