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.
- See Manage Events - Hit Attributes tab. 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. - See "Step-Based Eventing" in the Unica Discover Event Manager Manual.
- Step attributes cannot be used on the
Hit attribute match conditions
First Value
- event looks for the first value of the hit attribute in the current page or sessionLast Value
- event looks for the last value of the hit attribute in the current page or sessionMatch Count
- event looks for the number of instances of the hit attribute in the current page or sessionHit Attribute Found
- event looks for the existence of the hit attribute in the current page or sessionNote: For step attribute conditions,Match Count
andLast Value
are not applicable, as there is only one unique match and its value on the hit.
To perform a case-sensitive match for the hit attribute, click the Case Sensitive check box.