About Web Events
Use web events to identify how visitors interact with your web content. Web events can trigger a task, set a metric, or define a segment. You can combine different types of events in a data view that can be used for task targeting and metrics. For more information, see About Data Views.
View the Payloads for Web Events in a Web Browser
You can use the inspection tools in a web browser to view the information that your site’s SAS tag sends to SAS Customer Intelligence 360.
For example, you can follow these steps in the Chrome browser:
- Navigate to a web page that contains the JavaScript snippet for the SAS tag and is configured to work with SAS Customer Intelligence 360 (that is, the domain is approved and other basic configuration steps are complete).
- Right-click on the page and select Inspect to open the Developer Tools pane.
- Click the Network tab of the Developer Tools pane.
- (Optional) Configure
the Network tab to filter output:
- Enable the Preserve logs option. This action enables you to view the requests and responses that happen from a previous page. If this option is not enabled, these records are cleared when a new page loads.
- On the filter row, click Fetch/XHR to
limit the output to only those types of requests and responses.
TipTo filter results even more, you can enter the name of the domain (or CNAME) that hosts the SAS tag in the filter’s text field.
- Take an action on the web page to trigger a series of events. You could click a button, navigate to a new page, or even reload the current page.
- On the Network tab,
note the entries that have these values:
- the Name column has a value that matches your tenant ID.
- the Initiator column
has a value that matches the JavaScript file for the SAS tag, such
as
ot-min.js.
- Click a record in the
log to open the record’s details. To find a record that corresponds
to an event, find a record where the Request Method on the Headers tab
is equal to
POST. - Navigate to the Payload tab of the record’s details to see the event’s payload. The payload information includes data such as the event’s name, the event’s channel, and so on.
Manage Web Events
When an event is open, content delivery and event processing are suspended for the site on any tab in the same browser instance. To see content delivered or to process events on the site while you are creating or editing an event, open the site in a different browser.
Event attributes can also be used in personalization variables. Personalization variables are used in tasks to deliver creatives that contain information that is dependent on user behavior. For example, a variable can be replaced with the name of a product that a user has added to the cart or a user’s cart total. Event attributes collect data that personalization variables use. A personalization variable eventually needs to be replaced by information retrieved from an event attribute. As a result, at least one event containing an attribute must exist in the system before a creative with a personalization variable can be successfully delivered by a task.
For more information, see Use Merge Tags and Variables to Personalize Creatives.
View Usage Information
On the Orchestration
Usage tab, you can view which items use the event.
The ability to view dependencies between items enables you to see the items that a task depends on to work successfully. Usage information helps you identify how changes that you make to one item might affect another item.
Items That Use the Event
The first section shows the items that use the event. For example, if the event is used in a task, the task is included in the list.
The Priority column displays the priority of like tasks that use the event. Priority applies only to mobile spot, web spot, and mobile in-app message tasks because each of those task types might have two or more tasks that compete for the same resources. Other task types do not use prioritization.
For non-A/B test tasks, priority is on a scale of 1 through 5 (where 1 is the highest). The default is 3. An A/B test task has a priority of Test, which is higher than a non-A/B test task. An A/B test task always delivers its content.
You can change the priority
of a non-A/B test task on the task’s OrchestrationPriority tab.
To open an item, click
the item. To view item details and to open the item, click 
in the item’s row.
Items That the Event Uses
The second section shows items that the event uses. Because an event does not use another item, the list is empty.