Content and Advanced Conversion Tracking - Yahoo! Web Analytics - page 49

truly utilize your exported raw data and have this tied directly into your CrM system.
But even beyond that, you are provided with other opportunities, such as multiple sales
in one session.
tracking the ORDERID variable for a commerce site is almost obligatory, as this
can improve the accuracy of monitoring your sales in both systems, making sure that
there are no duplicate orders captured during a visit. this also shows why ORDERID is
heavily used by the Yahoo! support teams when troubleshooting issues with revenue
and sales tracking in general.
Furthermore, if you become advanced enough to use the application program-
ming interface (aPi), ORDERID is absolutely necessary as a key to that system.
as you can see in the next example, the ORDERID variable goes hand in hand with
the sale ACTION from a technical point of view, and from a rational point of view, the
AMOUNT variable.
version 4
var ACTION='01';
var AMOUNT='USD19.95';
var ORDERID='10099801';

49

version 5
YWATracker.setAction(“01“);
YWATracker.setAmount(“USD19.95“);
YWATracker.setOrderId(“10099801“);

i think this is my last time repeating the general note that an ORDERID variable
must not be longer than 75 characters and that you must not use non-asCii characters.
in addition to that, do not use any of the following characters in the name:
' < > # & ; : ? - * ~ ` ´ ) ( = % ! “

these and other non-asCii characters may have a negative effect on the general track-
ing script and the way it operates.

Revenue Encryption

Yahoo! Web analytics has designed a feature that allows you to avoid passing on your
revenue in clear text over the internet, for those clients and situations that warrant such
a decision. in most cases, though, having a sale of $19.95 would look like this example:
version 4
var ACTION='01';
var AMOUNT='USD19.95';

version 5
YWATracker.setAction(“01“);
YWATracker.setAmount(“USD19.95“);