Information Technology Reference
In-Depth Information
These products and actions typically register in the order presented here so that
tracking a sale of a given product would look like this:
Version 4
var ACTION='01';
var _S_SKU='DM112899';
Version 5
YWATracker.setAction(“01“);
YWATracker.setSKU(“DM112899“);
The value of the variable corresponds to the specific product or products you
wish to track, and the product skU information is typically something you inflate at
runtime. The reason for doing so is that it is unusual to see product pages managed
manually, and they are generally created in runtime based on a product database.
There is nothing wrong in hard-coding this in the
_S_SKU
variable if you have a limited
number of products.
if you do not manage your own product pages—that is, if you use an outsourced
e-commerce platform—you should expect, actually
demand
, that they provide you
with a set of tracking variables that you can use.
Let me give you a simple example of a standard php-enabled e-commerce plat-
form and what a runtime-inflated variable looks like:
Version 4
var ACTION='PRODUCT_VIEW';
var _S_SKU = “<?php echo $product_info['products_id']; ?>”;
87
Version 5
YWATracker.setAction(“PRODUCT_VIEW“);
YWATracker.setSKU(“<?php echo $product_info['products_id']; ?>“);
if your company does not deploy skU codes, you can just create your own pro-
prietary numbering or naming system. it is absolutely essential to supply Yahoo! Web
analytics with a unique number for referencing each product, as grouping separate
products into the same skU would create more harm than good.
Tracking Units and Amounts
You should always track the individual units and individual amounts; otherwise you'll
end up with flawed information, which is almost always worse than having no infor-
mation at all.
so, using the previous sales example and applying the
_S_UNITS
and
_S_AMOUNTS
variables, we get:
