Use events in Tealeaf to track specific data from the parts of your website that you choose. For example, you might have a cart abandonment event that fires when someone does not make a purchase from their cart. This gives you the information you need to see not only what might be happening, but you can then investigate why it happened.
After creating events, you can update them whenever you need to which helps make sure you're always getting the exact data that you want.
Create an event in basic mode
If you want the Event you are creating to publish Event data to Acoustic Exchange, you need to configure the Event as an "Exchange event" by setting the Category and Event type.
To publish Event data to Acoustic Exchange, make sure your administrator has registered Tealeaf as an endpoint in Exchange, and that the Exchange integration settings for your organization are set on the Company Settings page.
- In the Event manager, click New.
- Select Event.
- Add the following information for the event:
- Enter the event name.
- Add tags.
- Enter a description of your event.
- Select the trigger for your event.
- Choose the frequency for your event.
- Choose the Published at time for your event.
- Choose Basic as the Mode.
- Add conditions.
- Add a new hit, session, or step attribute:
- Click Conditions.
- Click Hit Attribute, Session Attribute, or Step Attribute from the left navigation.
- Click Create new hit attribute, Create new session attribute, or Create new step attribute.
- Fill out the form and click Save.
- Click Select to add the attribute to your Event.
- Add events, hit attributes, step attributes, or session attributes as conditions:
- Click Conditions.
- Select a condition (Event, Hit Attribute, Step Attribute, or Session Attribute) from the left side panel.
- Select an item from the Results window.
- Check the Select Multiple check box and set the condition type if you want to add more than one condition at a time.
A check box is added to the items in the Results window, allowing you to select multiple conditions.
- Select the check boxes for the conditions that you want to add.
- Click Select to add the condition(s) to your Event.
- Select your Reference value and choose how to treat it.
- Choose how you want to store metrics.
- Choose how you want to track metrics.
- Specify whether the Event is a building block only Event.
- Specify whether you want to discard sessions based on user-defined Event criteria. If you select Discard sessions, any session that meets user-defined event criteria is not written to session list.
For example, if you check Discard sessions and specified that you don't want sessions with only one screen view event to be included in the search, Discard sessions implements the following logic:
If [Event: Screenview Count] is <= 1, Discard Session
- Optional: Configure the Event to be an Exchange event.
- Select a Category.
- Specify an Event.
When you select a category, the events associated with the category are listed in the Event drop-down list.
- Set the attributes for the Exchange event.
See Publishing event data from Tealeaf to Acoustic Exchange for more information.
For a use case that describes the end-to-end configuration scenario for sending event data to Exchange with a ready-to-use Exchange event, see Create a campaign that targets cart abandonment causes.
Note: With the July 2020 release of Tealeaf, you can publish user-defined events to Acoustic Exchange.
- Add any dimensions groups.
- Optional: Select On to enable Geo analytics for the dimension groups that are associated with this event.
- Click Save.
Update basic events
In Tealeaf, you can edit, copy, and delete events, and purge data from your events.
In the Event manager, click Event to view the list of events.
- You can copy events. Copying and modifying an event is useful if you have a complicated event that has multiple elements associated with it and that can be reused with few changes.
When you copy an event, it is displayed in the Events list as <original event name> copy. Additional copies of an event are named <original event name> copy n, where n is the number of the copy. You can rename and modify the copied event as needed.
- If reporting data is inaccurate, you can purge the event data.
Data might be inaccurate because of an incorrect event definition. Rather than creating a new event, you can modify the existing event to correct the settings. You then purge the old event data so that you have only accurate data in your reports.
You can also purge the data for the dimension for the event. If you purge dimension data, the historical event data for the dimension becomes "other".
- You can delete events. When you delete an event, items that use that event are also affected.
- Events that use the deleted event as a condition, value, or Exchange attribute are deleted.
- Dimensions that use the event as a value source are deleted.
- Reports that use the event as a metric or calculated metric are deleted along with the report schedules.
- Alerts that use the event are deleted.
- Session attributes that use the event as a value source are updated to remove the value source. If the deleted event is the only value source and the session attribute is not provided by the system, the session attribute is also deleted. If the session attribute is provided by the system, the session attribute is disabled when the event is deleted.
- Struggle Analytic reports that use the event are updated to remove the event from the struggle factor score or page mapping rule.
Note: You must have administrator permissions to delete an event.
Before you confirm that you want to delete an event, you are shown a list of the items that will be deleted along with the event. If there is an item in the hierarchy that you do not want to delete, click Cancel. Then, disassociate the item from the event and delete the event.
For example, there is an event that needs to be deleted. The event is used by a session attribute that is used in a session view template. When the event is deleted, the session attribute is deleted and the session attribute column is removed from the session view template.