DX Cloud Tags Reference Guide – Control

Overview

This document is a reference guide to the rules for controlling tags provided in DX Cloud Tags.

You can

  • protect cookies from being accessed by other third-party tags
  • control access to one of more form fields
  • point to specific tags and defer their load sequence to a later time, or block them from being loaded at all

Note

This first version of Tag Analytics & Control only allows control over dynamic tags – that is, tags that are launched by other JavaScript. For example, tag managers insert JavaScript that will launch many of the tags on the page in runtime in the browser. Static tags, which are defined directly in the HTML code (either with references to source files or actual lines of code) are not supported.

Creating rules is described in detail in Configuring Tag Control Rules in the Portal.

Tag control rules are one of two main types:

  • Orchestration
  • Protection

Alerting rules are described in DX Cloud Tags Reference – Alerting.

Protection

Protection rules allow you to identify specific elements of your app to protect from being accessed by third-party scripts.

The overall process for creating this type of rule is:

  1. Identify your web application by specifying criteria like the application's domain, path, or query string and/or the browser, device, or country code from the requesting client.
  2. Choose the action Control Cookie Access and identify the cookie you want to protect by specifying its name, the URL pattern specifying the tags you want to isolate the cookie from; or
    Choose the action Protect Form Field and identify the form field you want to protect by specifying the DOM selector of the field and the URL pattern specifying the tags you want to protect the field from.
  3. Choose to control read access, write access, or both.

Orchestration

Orchestration rules allow you to identify tags execution time you want to control.

The overall process for creating this type of rule is:

  1. Identify your web application by specifying criteria like the application's domain, path, or query string and/or the browser, device, or country code from the requesting client.
  2. Choose the action Delay Resource Load and identify the resource you want to delay by specifying criteria like the resource's domain, path, or query string.
  3. Choose the Event that you want to have the specified resource load after. The choices are
    - Page Loaded – when the webpage and its dependent resources have finished loading.
    - DOM Content Loaded – when the initial HTML document has been completely loaded and parsed, without waiting for stylesheets, images, and subframes to finish loading.
    - Never Load – do not load the script at all.