Please note that if a script affects more than one publisher, please add the script to the global scripts. If a script affects an individual publisher, please file it with the specific publisher.
To run a script for a single publisher, you can do this under the script config at the publisher
In order for IDs to take effect at publisher level, they must be stored under the variables. Please note that the publishers scope takes priority (see hereGlobal Scripts tab). See example for Boote below:
Please use the variables if two publishers have two different solutions for one value
Scripts config tab configures scripts which are included on a webpage.
Scripts title - name/description of the script
Priority:
low - SDK load script after first ad request
high - SDK load script during initialization
very high - SDK load script during initialization before high priority scripts
Required - toggle: if
required
is true, SDK will throw an error and stop initialization process whenever script fails to loadForce execution - toggle to force the script delivery even when no_ad applied (even if
dataLayer.push({ 'atf-noAdDelivery': true });
)Use user consent - on/ off toggle: if
useUserConsent
is true, SDK will check if consents are applied for vendors fromvendorIDs
list and then load scripts if all consents are allowedVendor ID:
vendorIDs
is list of vendor ids for which consents need to be verified ifuseUserConsent
is true. The IDs only need to be separated by a comma and there is no limit of Vendor IDs. The vendor IDs are stored with an and-link.Script input - to include the script
on/off - toggle to turn on (activate) or off (deactivate) the script. If deactivated, script will not be included.