Saturday, February 20, 2010

Omniture SiteCatalyst events

This post is a continuation of my last post Omniture Site Catalyst: Props ,eVars and events in which I made a passing mention about Omniture events. This particular post is dedicated specifically for events .

Events in SiteCatalyst are classified as:

Predefined events: Events that come out of the box with SiteCatalyst

Custom events: Events which you can define based on your specific requirements

Predefined events:
Omniture offers several predefined events, some of them described below:

prodView      :  Success event occurs any time a visitor views a product.
scView          :  Success event occurs any time a shopping cart is viewed.
scOpen          :  Success event occurs any time a visitor opens a shopping cart for the first time.
scAdd            : Success event occurs any time a product is added to a shopping cart.
scRemove      : Success event occurs any time an item is taken out of a shopping cart.
scCheckout    : Success event occurs on the first page of a checkout.
Purchase        : Success event occurs on the final page of a checkout (includes Revenue, Orders, and Units).

When any of the predefined events above occurs, an instance of the event is incremented, and you can view the metrics related to the event in several different SiteCatalyst reports. The following is an example of the code used to configure predefined events."scAdd""scOpen,scAdd"

In the first example above, scAdd is the value of the event. Any time an item is added to the shopping cart, the event is incremented. In the second example, two values are captured at the same time. When multiple success events occur on the same page, each event is incremented.

Shopping Cart Page (scOpen, scAdd, scRemove)"scOpen,scAdd"

First Checkout Page"scCheckout"

Confirmation Page (Purchase Complete)"purchase"

Custom Events:
Custom events allow you to define your own success metric. For example a registration page on your website can be a success event for which there are no predefined events. Custom events follow the standard syntax shown below.

The code above shows how you would assign an event to the events variable. However, if you do not modify the event name in the interface, then "event3" would display in the interface.By default, success events are configured as Auto Incrementor events or standard counters. Auto Incrementor events simply count the number of times a success event is set

1 comment:

  1. Hey Paul,
    I am really confused as to how do we link the events with the interface?? I mean how does omniture know that this is a particular event ?