Creating Purchase View Events for Web

Like cart and checkout rules, purchase configurations enable you to collect data on a visitor's shopping experience. Define purchase rules to identify pages such as an order confirmation and the elements that are contained within it.

Purchase view events generate entries in the ORDER_SUMMARY table and the ORDER_DETAILS table.

To create a purchase view event:

1. On the navigation bar, click Event TrackingEvents.

2. Click .

3. Select Purchase View.
4. Select Page View.

   You can select the web page with SAS Customer Intelligence 360 or manually specify the page URL.

   • To select the web page using the user interface:
     • Navigate to the web page that a visitor loads.
     • (Optional) Click Select Row for Product Purchase to identify the element for each product in the purchase.
       Note: When you select an element, the Selector field displays the corresponding CSS selector. You can refine this selector if you need to match an element based on different characteristics.

       You can change this element by navigating to Event DetailsPurchase Product Attributes. Then, click to select a new element in the Purchase row selector field.

       The embedded site browser is not currently integrated with the SAS tag that loads only the JavaScript Events API Version 2 (ot-api.min.js). If you use this tag, you must manually set the page locations, page elements, selectors, and so on for any events that you create in the user interface.

     • (Optional) Click Select Product Attributes for Purchase to define default attributes for the product in the purchase. You can change this attribute later by navigating to Event DetailsPurchase Product Attributes.

       Select which default attributes to set values for in the Attribute list.

       • Product Name is a required attribute.
         Note: Product names are limited to 40 characters.
       • Click Select Parent to refine the selector.
       • Click Returned Value to preview and edit the value that the attribute returns.
     • (Optional) Click Select Purchase Attributes to define default attributes for the product in the purchase. You can change this attribute later by navigating to Event DetailsPurchase Attributes.
     • Click Create Event.
   • To manually specify the web page and selector details, click Create Event. Then navigate to Event DetailsEvent Configuration to configure the URL. Next, you must navigate to Event DetailsCart Product Attributes and specify the Purchase row selector and the product name Selector, which are required values. You can use this option to specify the URL for a web page that requires a login or that is part of a single-page application (SPA).
   Note: Select JavaScript API to create an event that listens for a corresponding event from the JavaScript Events API. The steps are similar to defining a custom JavaScript API event. For more information, see the relevant steps in Creating JavaScript API Events for Web.

   Navigate to Event DetailsPurchase Product Attributes to see the standard purchase product attributes for the JavaScript API event. Navigate to Event DetailsPurchase Attributes to see the standard purchase attributes for the JavaScript API event. These values are read-only.

5. Refine the pages that are associated with your event by navigating to Event DetailsEvent Configuration.

   When you define the pages where the event occurs:

   • Choose Selected page to include only the page that you selected for the event’s location.
   • Choose Any page to include all pages that contain the click target that you defined.
   • Choose Pages matching attribute pattern to define rules that determine which pages to include. You can create a pattern that matches a URL, a domain, or an element.

     When you add a rule, you can choose different options to match pages for the event. For more information about the options, see Page Elements and Attributes.

6. Define rules to identify attributes for each product being purchased. Navigate to Event DetailsPurchase Product Attributes.

   To refine the selector for the products in the cart in Purchase row selector, click and specify the selector.

   Note: The embedded site browser is not currently integrated with the SAS tag that loads only the JavaScript Events API Version 2 (ot-api.min.js). If you use this tag, you must manually set the page locations, page elements, selectors, and so on for any events that you create in the user interface.
   Note: After an event is published, you can add new attributes but you cannot modify existing attributes.

   Adding attributes enables you to collect additional information about the action that triggers the event and the page that contains the event. The attribute data that is collected can be used elsewhere. For example, attributes that you add to this event can be selected as criteria when you define a segment. The available attributes vary by event type.

   1. Select Define value for the category that you want to specify.
   2. For the Selector field, click and select the element that corresponds to the category.
      Note: The embedded site browser is not currently integrated with the SAS tag that loads only the JavaScript Events API Version 2 (ot-api.min.js). If you use this tag, you must manually set the page locations, page elements, selectors, and so on for any events that you create in the user interface.
   3. For the Return value from field, select a value based on the type of element:
      • For attributes, select the name of the attribute.
      • For field values, select value.
      • For the content of a node, select innerHTML or innerText, depending on the node type.
   4. For the Return field, specify the part of the return value that you want returned.
   5. Select an option for Attribute data type. For some attribute types, this option cannot be modified.
7. Define rules to identify attributes for the purchase process. Navigate to Event DetailsPurchase Attributes.
8. Define rules to identify custom attributes for the purchase. Navigate to Event DetailsCustom Attributes.
   1. Click and select the attribute type.
   2. Select the attribute's type from either the Page Load Attributes tab or the Event Attributes tab.

      For more information about the attributes that can be selected, see the topics Page Load Attributes and Event Attributes.

   3. Define the attribute’s properties and return value.
      Note: Do not exceed 150 characters for an attribute’s name or value. The attribute that you create cannot use the following reserved attribute names. You cannot use the reserved names with a different case because the check is not case sensitive.
   4. By default, the Personally identifiable information check box for a custom attribute is selected. You cannot track an event attribute if the check box is selected. Uncheck the Personally identifiable information check box if the associated data is not considered personal information.

      When this option is enabled, the system stores the data in a temporary table for the amount of time that you specify. SAS Customer Intelligence 360 can store this information up to a maximum of six months. After the specified time period has passed, the data is discarded.

      Note: For email data types, the Personally identifiable information option is enabled and cannot be deselected.
9. On the Orchestration tab, complete one of these actions:
   • Select Mark ready to change the status from Designing to Ready. A Ready status indicates that this item is ready to be published. When you are ready to promote an item from a Ready status to an Active status, click Publish.
     Note: When you publish an item, you are prompted to publish any dependent items that are marked Ready.

     Items with a Ready status can be changed back to a Designing status by clicking Return to designing. Changing this status to Designing prevents the item from being published.

     Note: If your item has a Ready status and a start date, the item is not automatically published when the start date is reached. For example, if you are creating a task, it must be published in order for the start date to activate the task.
   • Select Mark ready and publish to change the status from Designing to Active. Items with an Active status cannot be changed back to Designing.

   If the content of a published item is changed and saved, that item becomes out of sync with the published version. To synchronize the content, select Republish. Otherwise, the item stays out of sync with the published version and the updates are not delivered.

   For more information, see Republishing Out of Sync Items.

10. (Optional) Click and select Properties to perform these actions:
    • Add a name and a description for the event.
    • See folder information for the event.
    • Select Make the event available to the customer state profile to make the data for SAS Customer Intelligence 360 available to SAS Intelligent Decisioning so that SAS Intelligent Decisioning can return criteria for targeting and merge tags. The targeting and merge tag criteria are displayed in the Decision Flows and Models folder.
      Note: This option is accessible only after SAS Intelligent Decisioning is enabled for your tenant. For more information, contact SAS Technical Support.
11. Publish the event in the data collection configuration. This step is necessary because the event type was previously an advanced collection rule, and the event is still used to populate those data tables.
    1. On the navigation bar, click Data Processing.
    2. In the Published Status section, click Publish.