The ability to create an event-based rule based on clicks to certain elements in DTM is a huge leap for us. However, we're really limited by what is available right now, since not every scenario is listed in the "Event Type" dropdown, and we have to keep up with arbitrary changes to the front-end code to ensure that what we have set up doesn't break.
This idea is the proposal that, in addition to all of the current capabilities, Adobe adds the ability to create an event listener for any JavaScript event (or at least, in the same spirt of a "Data layer," an "event layer"), so that we can truly separate the concerns of firing a meaningful event and tracking that event, from our other UI code. I would imagine that either we could specify the target, or Adobe could use a specific target.
Use cases:
- Where the event is triggered by an AJAX response and not a direct user interaction (for instance, a successful login in an overlay, or a share to another service), we have a way to track it
- Where the UI's HTML is unknown, we can still give our developers a specification for alerting than an event happened so that it is trackable in the future.
- Where the UI is subject to change, we can ensure that no matter which class names or object IDs are used in the source, meaningful events stay the same.