Success events
Success events (also known as conversion events or custom events) are actions that can be tracked. You determine what a success event is. For example, if a visitor purchases an item, the purchase event could be considered the success event.
For a video overview of success events, see Introduction to conversion events in the Analytics tutorials guide.
Success event examples
There are many kinds of success events, depending on your web site type. Several examples include:
- Retail: Product view, checkout, purchase
- Media: Subscription, contest sign-up, page view, video view
- Finance: Application submission, login, self-service tools usage
- Travel: Booking (purchase), internal campaign (click-through), search (pricing itinerary)
- Telecommunications: Purchase, leads, self-service tools usage
- High Tech: White-paper download, RFP, form completion, support requests
- Automotive: Lead submission, request a quote, brochure download
The s.events variable defines a success event.
Configure success events
You can configure the Event variables used on your site. You can add up to 1,000 success events. Events 81-1,000 work only if you are on H22 code or higher.
To configure success events:
-
In Adobe Analytics, select Admin > Report Suites.
-
Select the report suite where you want to configure success events.
-
Select Edit Settings > Conversion > Success Events.
-
In the Event column, identify the name of the event that you want to use as a success event.
-
In the Name column, select the checkbox next to the item to enable editing, then specify the desired name.
Give meaningful names to success events used on your site. For example, if event1 is used to track registrations, change the name here so that event1 will be represented as the “Registrations” metric in all Conversion reports.
-
In the Type column, select the checkbox next to the item to enable the drop-down list, then select the desired type.
note important IMPORTANT Consider the following when changing the event type: - You can change the event type between counter and numeric without losing access to previously captured data.
- When changing event types to or from a currency event, a message is displayed stating that historical data is not available in reporting. Different event types use separate data tables, and cannot be used simultaneously. Some historical data can be restored if the user reverts the event type. However, any data collected after the initial change is not available.
The type that you select determines whether the event is a counter (standard), numeric, or currency event.
Counter events are used to record an event in time.
Numeric events are used to report on non-currency numbers, such as the number of coupons used in an order.
Currency events record a decimal number, like tax or shipping. The value passed into currency events is converted from the page currency to the report suite’s base currency upon receipt. Currency events are used to track tax and shipping charges. For details on using currency events, contact an Adobe representative.
Numeric and currency events allow you to increment metrics by more than one.
Events used in the Standard type of Data Sources must be numeric or currency events.
-
In the Polarity column, select the checkbox, then choose from the drop-down menu whether an upward trend for this metric is good or bad.
this allows you to indicate whether Adobe Analytics should consider it good or bad if a given custom event (metric) goes up. It activates directional indicators (arrows) for various metrics to add context (for example, week over week comparisons). Examples: if “Bugs Submitted” goes up week over week, should Adobe Analytics consider that good, or bad? An increase in Email Registrations is probably good. But an increase in Form Submission Errors is probably bad. In Analysis Workspace, polarity is applied to: Freeform Table conditional formatting, Summary Change visualizations, and the Map visualization’s Positive/Negative color scheme.
-
In the Visibility column, select the checkbox, then choose from the drop-down menu whether to hide standard (built-in) metrics, custom events, and built-in events in the Menu, Metric Selectors, Calculated Metrics Builder, and the Segment Builder.
This setting does not impact the data collection for that metric or event; it affects only its visibility in the user interface, as follows:
The following settings are available:
table 0-row-3 1-row-3 2-row-3 3-row-3 Setting Visible in Not visible in Visible everywhere - Analysis Workspace
- Segment Builder
- Calculated Metric Builder
N/A Builders - Segment Builder
- Calculated Metric Builder
- Analysis Workspace
Hidden everywhere N/A - Analysis Workspace
- Segment Builder
- Calculated Metric Builder
-
In the Description column, select the checkbox, then provide a description.
-
In the Unique Event Recording column, select the checkbox, then choose from the drop-down menu whether to always record the event.
The following options are available:
table 0-row-2 1-row-2 2-row-2 Option Function Record Once Per Visit Ties the given event to the visitor’s session. Subsequent counts to a given event in the same visit are ignored. This type of event serialization does not require any implementation changes. Use Event ID Ties the given event to a custom ID. Subsequent counts to a given event with the same event ID are ignored. This type of event serialization requires a custom ID in hits to deduplicate values. See Event ID serialization in the Implement user guide. -
In the Participation column, select the checkbox, then choose whether to enable or disable participation. When enabled, it gives full attribution credit to all dimension items in the visit.
note note NOTE You can enable participation for up to 100 custom events. Beyond that, you can create participation metrics in the Calculated Metrics builder. -
Select Save.