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 a "UBX event" by setting the Category and Event type.
To publish Event data to Acoustic Exchange, make sure your administrator has registered Experience Analytics (Tealeaf) on Cloud as an endpoint in Exchange, and that the Exchange (UBX) 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.
- Add a new hit, session, or step attribute:
- 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 a UBX event.
The Exchange (UBX)-supported categories and event types for Acoustic Experience Analytics (Tealeaf) are listed in the Category and Event drop-down lists, and can also be found in Acoustic Exchange, in the Exchange (UBX) Dynamic Event Library.
The Exchange Dynamic Event Library is an interactive guide of the Event types that are recognized by Acoustic Exchange, and the publishers and subscribers that support the Events.
The Acoustic Experience Analytics (Tealeaf) Events (grouped by category) and the prerequisite attributes adhere to the Exchange taxonomy. For information about Acoustic Exchange (UBX) events and the Dynamic Event Library, see the Acoustic Exchange help center.When you configure an Event to be a Exchange (UBX) event, and the defined conditions for the Event are met:
- Experience Analytics (Tealeaf) publishes data from the Event to Exchange.
- Acoustic Exchanve processes the data that is generated from the UBX event configuration only, and ignores everything else.
- Experience Analytics (Tealeaf) processes the Event normally based on the conditions and parameters outside of the Acoustic Exchange parameters.
- 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 (UBX) Event.
- 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 Experience Analytics, 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 edit events by modifying the conditions in either Basic mode or Advanced mode.
- 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.
Note: You must have administrator permissions to delete an event.
- Events that use the deleted event as a condition, value, or Exchange (UBX) 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.
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.