Condition step

When you create an event to track a JSON message item, the step attribute that is required to detect the name-value pair is also created in draft mode for you. For such scenarios, the Hit Attribute condition specifies the step attribute that the Event Manager has also created for you.

The Event Manager pre-populates the event definition with properties to identify the specific JSON item to track.

Note: For step attribute conditions, Match Count and Last Value value tests are not useful, as there is only one unique match and its value for a specified property on the hit.
Note: If you do not want to double count actions, use both the event type and the ID/name when you create events for a specific action.
  • If you look only for ID = checkout method, then this event fires twice when you only wanted it to fire once. Suppose you want to track clicked objects. Each object has the event type click.
  • To track clicks of a specific object, you must specify both the event type and object ID.
  • If a step attribute with the same properties exists, the Event Manager uses the existing step attribute.
  • As needed, you can add extra conditions to the event you are creating.
Table 1. Key Properties:
Attribute Properties Description
Icon You must select an identifying icon for your step-based events.
Labels You can organize your step-based events into labels within the Event Manager.
Evaluate Set the trigger to be either of the step-based triggers.
Track Set the occurrences to track to monitor the first or last occurrence in the session or every occurrence.
  • If you want to track the number of sessions in which the event occurrence, set the value to Last Occurrence.
  • If you want to track each time that the event occurred in a session, set the value to Every Occurrence.
Value Type Step-based events can track numeric or text values or the count of occurrences of the event.