Event Development

Event testing

Since the number and complexity of events can affect system load, it is important to ensure that events produce the wanted data. The Event Manager includes an integrated tester to test your defined events against session data before it deploys them in the live environment.

Event execution

After objects are created or edited with the Discover Event Manager are saved, the event definitions are replicated to the Processing Servers (Canisters) where they are run. Searchable and aggregated reporting data is generated when the event fires. The time lag between saving changes and being able to see results depends on both system configuration and load.

Changes to Events

The definition of events has changed significantly since Release 7.x. For example:

• Event categories, such as compound session close events and compound page events, have been largely eliminated, in favor of a simpler model that evaluates events that are simply based on where they occur in the session. Events can be organized into event labels, but a label is an organizational structure only.
• Compound events can be created simply by using the outputs of one or more events as inputs to another event. Outputs of page-level events can be mapped to the inputs of page-level or session-level events.
• Event hierarchies have changed. Hierarchies are essentially dependencies between events and are not explicit parent-child relationships. Hierarchies can no longer be necessary because of the potential for multiple triggers for an event.