In the Condition step, you specify one or more conditions under which the event fires. If the conditions are detected, the event evaluates as True, and the resulting value or values are stored and, if configured, made available for reporting.

Select specific conditions and specify whether All or Any of the conditions must be met for the event to fire. Each event must have at least one condition. There is no maximum limit to the number of conditions that an event can have. The maximum length for selected values of text for step attributes, hit attributes, and events is 256 characters.

Note: You can configure an event to be triggered on every hit by specifying a condition that occurs in each hit, such as the presence of TLTSID.

To create complex rules using multiple logical operators (for example, if ((A and B) or C) = true, then fire event), you must configure multiple events or use Advanced Mode, which must be enabled.

1. Select the evaluator that must be met for the condition to evaluate as True.
2. Add events, hit attributes, or session attributes as conditions:
   1. To add a condition, click the name for object type to use in the condition to expand the section.

      Note: End of Session events cannot reference hit attributes. Similarly, First Hit of Session events cannot reference user-defined session attributes, which were not yet defined.

   2. Select the object to be used for the condition. All available objects are displayed.
   3. Select or populate any displayed fields for the condition.
3. If you created a condition that compares the selected event or attribute to another value, you can configure a specified value or the value of another event, hit attribute, or session attribute.
   1. To specify a fixed value for comparison, enter the value in the textbox.
   2. To compare the value to the value of another data object, click Set Item. In the dialog, select the object whose value you want to use in the comparison.
      • To remove the comparison to a data object, click Set Item again. In the dialog, select the value under Fixed User Defined Value. When the dialog closes, enter the fixed value in the textbox.
      • Set Item cannot be used with some events, such as distance and sequence events.
4. Add and configure extra conditions as needed.
5. Click the next step.

Event conditions

Event conditions evaluate the existence, count, timestamp, hit number, or value of the selected event and enable comparative evaluations to constants.

Note: By creating an event that references another event, you can create compound events and specify parent-child relationships. If your compound event uses a step-based event as one of its conditions, it must be configured to be evaluated on the After Every Hit trigger.

Event + dimension combinations: For Event conditions, you can specify an event and dimension combination to be used as one of the conditions triggering the event. For example, you can configure a condition for Event B to be the firing of Event A and the recording of Value 1 in Dimension A.

In the above example, the event is configured to be triggered when the event Test Ev01 fires and when the dimension Test Ev01 URL (Normalized) is set to include the value reviewOrder.

Report groups that are associated with the event in the condition are listed in bold-italics. Report groups cannot be used in event conditions.

When you select the dimension to include, you must specify the operator to test against the dimension value.

Hit attribute conditions

Hit attribute conditions examine the specified hit for the existence of the hit attribute, a defined number of instances of it, or the first or last value of the hit attribute data.

• Hit attribute conditions evaluate the hit where the event fired for any matching data. If the hit attribute for which you are searching exists on a previous page, the hit attribute value is blank.
• Hit attributes that do not contain an ending tag return the starting tag as the hit attribute.

  Note: Hit attributes are available only within the scope of a hit. You cannot use hit attributes as conditions for events that are configured to fire on session-level triggers; instead, you should store hit-level data as session attributes, which can be evaluated at the end of the session.

  • Step attributes cannot be used on the First Hit of Session trigger.
  • The values of step attributes are always treated as text patterns. As a result, operators such as equals perform text-based comparisons, even if the captured value is a numeric or Boolean value.

  Note: If you create hit attributes from the request buffer, note that the [HitType] section and [TLFID_*] sections (where * is the identifier for the fact) are generated by the event engine and cannot be detected in live sessions.
  As a result, any events using these hit attributes do not fire in the Windows™ pipeline and are therefore not available for searching. They do fire, however, when they are evaluated in the Event Tester on sessions that were already passed through the Canister.