Core behaviors are events that have broad application and reliable metadata. For example, adding an item to the cart, submitting an account application or submitting a travel booking.
Acoustic provides several out-of-the-box core behavior templates. These core behaviors have names that are retail-oriented by default. You can apply the same behaviors to other verticals with only a label change. This keeps the catalog of required behaviors as small as possible.
For example, A travel site booking would be tracked using an "Order" behavior. It’s relatively simple to relabel "Orders" as "Bookings" within the dependent applications.
Core behavior templates
Add to cart
An Add-to-Cart represents the selection of a product, itinerary, account, or similar offering for purchase or application.
The trigger event can be any event type, including the following:
- Data layer event
- Add-to-cart click
- Add-to-cart confirmation text
The following metadata attributes can be configured:
- Product ID
- Product name
- Quantity
- Unit price
- Resumed cart
- Currency
- Discount
- Product category
- Product URL
- Product image URL
- Shopping cart URL
- Virtual category
Note: For the currency metadata attribute, you can select if you want to add the attribute from an existing event or choose the currency from the provided list.
Order
An Order represents a primary transaction by a user within an application.
The trigger event can be any event type, including the following:
- Data layer event
- Confirmation page screenview
- Order confirmation text
The following metadata attributes can be configured:
- Order ID
- Order subtotal
- Order Shipping
- Order tax
- Order discount
- Order currency
Error
Two types of errors are supported:
Application errors – are those that have nothing to do with the user’s interaction. Examples include 400- and 500-series status codes and “caught” exceptions that present application error messages to the data layer, the DOM, or the user interface. Examples: “We encountered an issue” or “We’re sorry.”
User errors – are those that are primarily due to a user interacting with an application in an unexpected way - or in a way that does not pass validation. Even if the error is caused by bad application design, the error would be classified as user error. Examples: “Please complete all required fields” or “Email format is incorrect.”
The trigger event can be any event type, including the following:
- AJAX Listener status code 400- or 500-series
- Text detected
The following metadata attributes can be configured:
- Error type
Self-identification
Self-identification is when a user provides their identity. This identification can be an email, phone, login ID, or device identifier.
The trigger event can be any event type, including the following:
- Data layer event
- Text detected
- Form submit
The following metadata attributes can be configured:
- Identifier Name
- Identifier Value
- Acoustic device ID
- Opt-in
- Identification from login
Set core behaviors
To start setting a core behavior:
- Select Core behaviors in the side panel.
- Choose a core behavior template from the dropdown menu.
- The metadata fields for the chosen core behavior are displayed.
Note: All supporting events required to create the core behavior must be created before you can start adding the metadata attributes.
- Select the trigger event for the core behavior. The trigger event is required to be able to select the rest of the attributes for the core event. The trigger event options in the dropdown are the existing event definitions you created.
- Continue to select the metadata attributes for the chosen core behavior from an existing event definition.
- Click Save.