Show Menu
TOPICS×

Rules

Dynamic Tag Management is a rule-based system. It looks for user interaction and associated data. When the criteria outlined in your rules are met, the rule triggers the tool, script, or HTML you identified.
A rule consists of two parts:
Part
Description
Identifier
The identifier is what you want the rule to look for. The identifier you specify depends on the type of rule.
Trigger
Triggers occur after a rule's conditions are met. A rule in Dynamic Tag Management can trigger as many discrete actions as you want. For example, a single rule for an e-commerce Thank You page can trigger your analytics tools and third-party tags from a single rule. There is no need to create separate rules for each tool or tag.

Types of rules

There are three types of rules in Dynamic Tag Management as well as several default rules:
Event-based
Events are where the majority of interactions on sites take place. You can measure and react to these interactions in real-time, without the need for JavaScript.
Event-based rules are executed when visitors interact with on-page elements.
By leveraging in-page interactions and page-level tagging, you can optimize based on things like social media sharing, video interactions, tabbed interfaces, image galleries, and product sorting and filtering.
See Event-Based Rules Example for an example of how to set your condition to look for clicks on the various tabs on your product pages.
Page load
Let you target by URL, site section, or set up scenarios that are independent of the site structure. For example, a page-load rule can load a survey on the fifth page view or in the seventh minute of a visitor’s session.
Advanced page-load rules let you, for example, target specific user segments in rules.
Direct call
Designed to bypass Dynamic Tag Management event detection and lookup systems.
Direct call rules are ideal for situations where you want to tell Dynamic Tag Management exactly what is happening. Also, they are ideal when Dynamic Tag Management cannot detect an event in the DOM, such as with Adobe Flash.
See Creating conditions for Direct Call rules for more information and to watch an EnterpriseTV video about direct-call rules.
Default rules
When you activate a property, Dynamic Tag Management includes several default rules.
These rules track common interactions with your site and can help you analyze opportunities throughout your site.
Dynamic Tag Management includes the following default rules:
  • Dead Header: Tracks any clicks on "dead" (i.e. unlinked) header items.
  • Dead Image: Tracks any clicks on "dead" (i.e. unlinked) images.
  • Download Link: Tracks any clicks on downloadable site content.
  • Email Link: Tracks any clicks on linked emails.
  • Orientation Changed: Tracks any page orientation change (mobile relevant).
  • Outbound Link: Tracks any clicks on links driving off site.
  • Telephone Dial: Tracks any click on a phone number.
  • Zoom Changed: Tracks any change in page zoom.

New vs existing rules

You can create a new rule or add your script to an existing rule.
In each rule, you might notice that the screens look very similar: the Conditions section is listed first, then any Installed Tools, and finally the JavaScript / Third Party Tags section.
The reason the sections are listed in this order is that the Conditions (the visitor scenario being tracked) are the first things to think about when planning a new rule or a change to an existing rule.
What is the visitor doing? Where is it happening? When is it happening? If the Conditions are the same, if your scenario is the same, then you can add as many tool actions or variables, and as many third party tags as you would like to an existing rule, if one exists with the Conditions you need. If you have a different set of Conditions, you need to create another rule.
For example, if you have a new conversion pixel or tag to place on your site, and you have some existing rules, think about the scenario that must occur for the rule to execute. Consider whether you have a rule in your web property with the condition you need, to execute the conversion pixel. Suppose that you already have a page-load rule for your purchase confirmation page, and you are loading three conversion pixels in the JavaScript / Third Party Tags section. You can add your new pixel as a new Script in the same section of that rule, without creating a new rule.
If the Conditions are different, then you need to add a new rule.

Event-based rules example

An example of how you to use event-based rules in click-tracking for a tabbed interface on a product page.
When using event-based rules, it helps to have some knowledge of CSS selectors so that you can identify elements on the page.
The CSS Selector lets you quickly and easily select CSS elements to use as triggers for event-based rules without leaving the DTM rule builder. For more information, see Using the CSS Selector .
The following links are useful resources to learn about CSS:
Set up how to track this click in Adobe Analytics.
If you also have Google Analytics or any other platforms installed, you can leverage the same rule to configure or send data to as many platforms as you want.
When using event-based rules, Dynamic Tag Management offers powerful tools to surface data from the page and page elements with which the user interacts.
DTM Basics: Event-Based Rules, Part One

By then end of this video you should be able to:
  • Understand what an event-based rule is
  • Explain the event-based rule types
  • Create an event-based rule
DTM Basics: Event-Based Rules, Part Two

By then end of this video you should be able to:
  • Understand what an event-based rule is
  • Explain the event-based rule types
  • Create an event-based rule
DTM Basics: Event-Based Rules, Part Three

By then end of this video you should be able to:
  • Understand what an event-based rule is
  • Explain the event-based rule types
  • Create an event-based rule

Page load rules example

You can implement rules that trigger during the course of a page load. For example, you can display a survey after a certain number of page views, or after a specified number of minutes into a session. Page load rules let you target by URL, site section, or set up scenarios that are independent of the site structure.
DTM Basics: Page Load Rules, Part One

By then end of this video you should be able to:
  • Understand what a page load rule is
  • Understand the condition criteria options
  • Create a page load rule
DTM Basics: Page Load Rules, Part Two

By then end of this video you should be able to:
Google AdWords example
A marketer would like to trigger a Google AdWords conversion tag when a user fills out a form and arrives on the page https://www.mysite.com/form/thank-you.html
Here is how you can set up this scenario in Dynamic Tag Management:
  1. Create a new page load rule.
  2. In the rule conditions, specify the page where this rule will be triggered.
  3. Paste the tag your vendor gave you directly into the Third-Party Tags section.
    Because Dynamic Tag Management does not rely on templates, marketers can use any tag within a rule, even in formatted HTML.
  4. Give your rule a name that describes the user interaction like “Forms: User submits form.”
    You can also add descriptive metadata to your rule.
    This description will help you and others identify this rule if they want to use it for their tags or tools later.
  5. Save your rule, and you are ready to test it in a staging environment, request rule approval, and publish to the production site.
    By default, page load rules load at page bottom. This setup works for most scenarios. However, if the rule you are setting up has some dependency on in page content, it might be better to configure the rule to load on DOM ready. Conversely, if you have other rules that rely on the outcome of the rule in question, load the rule at Top of Page or Onload to ensure that it fires first.

Page load rules - advanced

This example shows how to deliver an A/B test to users on iPads.
You may want to target specific user segments in your rules. The following example shows how you can deliver an A/B test to a form, using a segment specific to users on iPads who have been on our site for more than fifteen minutes and came to the site through Google search.
  1. Create the conditions.
    The following image shows the setting you use for this visitor segment:
  2. Set up a test on the form using Adobe Target.
    You are not required to modify the page, and there are no mbox containers to place in your markup.
  3. Click Save , configure your test in Adobe Target and your test is running.

Rule conditions and functions

Describes all Dynamic Tag Management rule conditions and their functions.

Custom script in a rule condition

When using custom code in rule conditions for a page load rule, you must use the boolean return true when you want the rule to fire.

Conditions and functions

The following table describes condition types, conditions, functions, and applicable notes:
Condition Type Condition Function Notes
URL
Protocol
Indicate rule to fire on HTTP or HTTPS.
Subdomain
Indicate rule to fire or not fire on specified subdomain(s).
Enable regex on this condition to include multiple scenarios in a single condition.
Path
Indicate rule to fire or not fire on specified URL path(s).
Enable regex on this condition to include multiple scenarios in a single condition. The path condition functions based on the _satellite.data.URI , which is inclusive of query params.
Parameter
Indicate rule to fire if specific URL parameter(s) with specific values are present.
Enable regex on this condition to include multiple scenarios in a single condition.
Technology
Cookie Opt-out
Indicate rule to fire only if user accepts cookies based on presence of sat_track cookie that is set to "true"
Requires data element setup. Cookie can be given custom name on the Edit Property page.
Browser
Indicate rule to fire only in specified browsers.
Operating System
Indicate rule to fire only in specified operating systems.
Screen Resolution
Indicate rule to fire within specified screen-resolution ranges.
Window Size
Indicate rule to fire within specified window-size ranges.
Engagement
Traffic Source
Indicate rule to fire if visit came from specified source.
Enable regex on this condition to include multiple scenarios in a single condition.
Landing Page
Indicate rule to fire if visit landed on specified page(s).
Enable regex on this condition to include multiple scenarios in a single condition.
New/Returning Visitor
Indicate rule to fire only if new/returning visit.
Sessions
Indicate rule to fire if visitor has had >, =, or < specified number of sessions.
Page Views
Indicate rule to fire if visitor has had >, =, or < specified number of page views in this session or all sessions.
Time on Site
Indicate rule to fire if visit persists for specified # of minutes.
Registered User
Indicate rule to fire based on user registration status as indicated in data element. If the indicated data element has a value, then the condition evaluates as "true" (does not include the default value).
Requires data element setup.
Logged In
Indicate rule to fire if user is / is not logged in as indicated in data element. If the indicated data element has a value, then the condition evaluates as "true" (does not include the default value).
Requires data element setup.
Previous Converter
Indicate rule to fire if user is / is not a previous converter as indicated data element. If the indicated data element has a value, then the condition evaluates as "true" (does not include the default value).
Requires data element setup.
Cart Item Quantity
Indicate rule to fire if user has certain number of items in cart as indicated in data element.
Requires data element setup.
Cart Amount
Indicate rule to fire if user has certain dollar value in cart as indicated in data element.
Requires data element setup.
Data
Cookie
Indicate rule to fire if specified cookie with specified value is present.
Enable regex on this condition to include multiple scenarios in a single condition.
Data Element Value
Indicate rule to fire if specified data element with specified value is present.
Requires data element setup. Enable regex on this condition to include multiple scenarios in a single condition.
Variable Set
Indicate rule to fire if specified JS object with specified value is present. It may be necessary to prefix the object path with the appropriate scope depending on the scenario - 'this.', 'event.', 'target.', 'window.', or 'param.'
Enable regex on this condition to include multiple scenarios in a single condition.
Custom
Opens a blank text box to input custom script.