FINAL CONFIRMATION PAGE
The confirmation page is located at the end of a purchase cycle. Its primary purpose is to identify and confirm the purchase you have made. Thought you can use the products variable on any page of your Web site, the confirmation page is the location where the most fields of the product string are used. These components are discussed in this section.

PURCHASE COMPONENT
The purchase event should be set on the final confirmation (“Thank You”) page of the order process. On this page, the product name, category (optional), quantity and price are all capture in the products variable, as shown below.

    s.products=”Category;Product;Qty;TotalPrice”

As you have possible noticed, the previous examples have not used the quantity and price fields of the product string. These two fields are specified only at purchase. If it is easier to implement them with all events, it will still work and the quantity and total price fields will be ignore with all events except for the purchase event.

MULTIPLE PRODUCTS
If a customer on your site purchased multiple products, you submit them all through the products variable by using a comma separator, as shown in the example below:

    s.events=”purchase”
    s.products=”shirts;Polo;1;32.99,pants;Dockers;1;45.50”

As has been mentioned, you can also leave product categories blank, as shown below with product SKUs instead of friendly names.

    s.products=”; 12345;1;39.95,;abcdef;1;65.50”

Using the multiple products syntax also applies to other events, such as the general usage events discussed earlier in the chapter. For example, if you have a checkout with the two products listed above, you could populate the variables as follows:

    s.events=”scCheckout”
    s.products=”;12345.;abcdef”

ADDITIONAL PURCHASE VARIABLE
The purchase event populates orders, units, and revenue metrics. When you set the purchase event, the following variable can be or should be set (depending on whether or not they are required, highly recommended or optional)

  • s.events (Required)
  • s.products (Required)
  • s.purchaseID (Highly Recommended)
  • s.state (Optional)
  • s.zip (Optional)
The first two variables (s.events and s.products) are discussed earlier in this chapter. The purchaseID, state and zip variable are discussed next. For more information on these or other variable, refer to the implementation Manual.

The purchaseID Variable
The purchaseID variable is used to keep an order from being counted twice by Site Catalyst. Every time the purchase event is used on your site, you should use the purchaseID variable. If the purchaseID is populated, the products on the “Thank You” page will only be counted once per purchaseID, when is critical because many visitors to your site will save the ‘Thank You” or “Confirmation” page to refer back to. If you do not use the purchaseID variable, when the visitor comes back to the pages, it will submit another purchase event to SIte Catalyst with all of the associated variables. This can result in numbers that are far too high.

Although the purchaseID variable is not required, it is strongly recommended in order to prevent duplicate orders and other variables set on the purchase page.

The purchaseID is most commonly set to the order ID already on your site. You do not have to manage two sets of ID’s for the order that has been place. If your ID is longer than the pu rchaseID size limit (discussed below), you will probably want to figure out a way to shorten it while still keeping it unique to the order.