Expand my Community achievements bar.

SOLVED

What do each of the built-in DTM Event Types mean?

Avatar

Level 10

I'm creating an Event Based Rule in DTM and need help understanding each of the different event types.

1 Accepted Solution

Avatar

Correct answer by
Level 10

Here’s a list of the different built-in Event Types we can use in Event Based Rules, and how they’re defined:

EventDefinition
clickA pointing device button has been pressed and released on an element.
mouseoverA pointing device is moved onto the element that has the listener attached or onto one of its children.
keypressA key is pressed down and that key normally produces a character value (use input instead).
focusAn element has received focus (does not bubble).
blurAn element has lost focus (does not bubble).
submitA form is submitted.
changeAn element loses focus and its value changed since gaining focus.
endedPlayback has stopped because the end of the media was reached.
loadeddataThe first frame of the media has finished loading.
playPlayback has begun.
pausePlayback has been paused.
stalledThe user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
volumechangeThe volume has changed.
% completeEmits an event given a specified percentage of total playing time. Example: entering 10% indicates this rule will only fire when 10% of the total length of the video has been played.
time completeEmits an event given a specified duration of playing time. For example, entering 10 indicates this rule will only fire when 10 seconds of the total length of the video has been played.
orientationchangeThe orientation of the device (portrait/landscape) has changed.
zoomchangeWhen a pinch or spread gesture is performed on a mobile device.
enters viewportWhen the element first comes into the view of the visitor. If the element is in view immediately upon page load, it will be triggered right away, if it only comes in view after scrolling, it will fire then. An optional delay can be specified in the rule which determine how long the element has to be in view for before the event is triggered, of which the default value is 1 second.
element existsWhen an element of a specified selector comes into existance – either because it’s in the page markup or dynamically injected later on. Each rule only fires once.

For more info, please see this blog post or the documentation.

View solution in original post

1 Reply

Avatar

Correct answer by
Level 10

Here’s a list of the different built-in Event Types we can use in Event Based Rules, and how they’re defined:

EventDefinition
clickA pointing device button has been pressed and released on an element.
mouseoverA pointing device is moved onto the element that has the listener attached or onto one of its children.
keypressA key is pressed down and that key normally produces a character value (use input instead).
focusAn element has received focus (does not bubble).
blurAn element has lost focus (does not bubble).
submitA form is submitted.
changeAn element loses focus and its value changed since gaining focus.
endedPlayback has stopped because the end of the media was reached.
loadeddataThe first frame of the media has finished loading.
playPlayback has begun.
pausePlayback has been paused.
stalledThe user agent is trying to fetch media data, but data is unexpectedly not forthcoming.
volumechangeThe volume has changed.
% completeEmits an event given a specified percentage of total playing time. Example: entering 10% indicates this rule will only fire when 10% of the total length of the video has been played.
time completeEmits an event given a specified duration of playing time. For example, entering 10 indicates this rule will only fire when 10 seconds of the total length of the video has been played.
orientationchangeThe orientation of the device (portrait/landscape) has changed.
zoomchangeWhen a pinch or spread gesture is performed on a mobile device.
enters viewportWhen the element first comes into the view of the visitor. If the element is in view immediately upon page load, it will be triggered right away, if it only comes in view after scrolling, it will fire then. An optional delay can be specified in the rule which determine how long the element has to be in view for before the event is triggered, of which the default value is 1 second.
element existsWhen an element of a specified selector comes into existance – either because it’s in the page markup or dynamically injected later on. Each rule only fires once.

For more info, please see this blog post or the documentation.