Page Comparison

...

Image Removed

Scripts config tab configures scripts which are included on a webpage.

...

If we have scripts with different variables (such as Ids), we can control them via the Global Variable area:

...

The CustomVendorBcn, for example, differs if the publishers use different CMPs. To simplify the insertion of this ID, we have stored a default value at global level and the corresponding ID at publisher level. See also Script config tab.

The following can be defined within the scripts:

...

1. Scripts title - name/description of the script

2. Apply script to - All means all publishers, but you can open the selection and select, exclude or include individual publishers

3. Priority:

   1. low - SDK load script after first ad request

   2. high - SDK load script during initialization

   3. very high - SDK load script during initialization before high priority scripts

4. Required - toggle: if required is true, SDK will throw an error and stop initialization process whenever script fails to load

5. Force execution - toggle to force the script delivery even when no_ad applied (even if dataLayer.push({ 'atf-noAdDelivery': true });)

6. Use user consent - on/ off toggle: if useUserConsent is true, SDK will check if consents are applied for vendors from vendorIDs list and then load scripts if all consents are allowed

7. Vendor ID: vendorIDs is list of vendor ids for which consents need to be verified if useUserConsent 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.

8. Script input - to include the script

9. on/off - toggle to turn on (activate) or off (deactivate) the script. If deactivated, script will not be included.