Implement a merchandising variable
Describes how to enable and implement a merchandising variable.
Enable a Merchandising Variable
Merchandising can be enabled for any custom eVar on the Admin Tools > Report Suites > Conversion Variables page (you no longer need to call Adobe):
Determines how long merchandising values should persist.
Product Syntax : The value is set within s.products. Conversion Variable Syntax : The value is set in the designated merchandising s.eVar.
Merchandising Binding Event (Conversion variable syntax only)
Indicates when a product should be tied to the current merchandising category. Multiple events may be selected by holding down Ctrl and clicking on multiple items in the list. Note: When "Product Syntax" is selected, you can not choose an event (it is disabled, but not grayed out). You can select an event only when the "Conversion Variable Syntax" is selected.
Implementing Using Product Syntax
When Product Syntax is enabled, the merchandising category is populated directly within the products variable, so selecting and setting a binding event is not required. This is the recommended method and should be used unless the value is not available to set in s.products when the success event takes place.
s.products="category;product;quantity;price;event_incrementer; <codeph outputclass="syntax"> eVarN=merch_category| <codeph outputclass="syntax"> eVarM=merch_category2" </codeph outputclass="syntax"> </codeph outputclass="syntax">
s.events="prodView" s.products=";Fernie Snow Goggles;;;; <codeph outputclass="syntax"> eVar1=goggles" In </codeph outputclass="syntax">
The value "goggles" for eVar1 is assigned to the product "Fernie Snow Goggles". All subsequent success events (product adds, checkouts, purchases, and so on) that involve this product are credited to "goggles".
Implementing Using Conversion Variable Syntax
Conversion Variable Syntax should be used when the eVar value is not available to set in s.products . This typically means that your page has no context of the merchandising channel or finding method. In these cases you must set the merchandising variable before you arrive at the product page, and the value persists until the binding event occurs.
When the binding event selected during configuration occurs, the persisted value of the eVar is associated with the product. For example, if prodView is specified as the binding event, the merchandising category is tied to the current product list only at the time the event occurs. Only subsequent binding events can update a merchandising eVar that has already been assigned to a product.
- Syntax On the same or previous page before the binding event:
s.eVar1="merchandising_category"On the page where the binding event occurs:
- Example Page 1 of the visit:
s.eVar1="Outdoors:Ski Goggles"Page 2 of the visit:
s.events="prodView" s.products=";Fernie Snow Goggles"The value "Outdoors:Ski Goggles" for eVar1 is assigned to the product "Fernie Snow Goggles". All subsequent success events (product adds, checkouts, purchases, and so on) that involve this product are credited to "goggles".
Additionally, the current value of the merchandising variable is tied to all subsequent products until one of the following conditions is met:
- eVar expires (based on the "Expire After" setting)
- The merchandising eVar is overwritten with a new value.
For more information, see " Advanced Conversion Syntax Merchandising " at analyticsdemystified.com.