Information Technology Reference
In-Depth Information
As you have noticed, the custom fields belong to a group. the custom field
grouping has no influence on your tracking or reporting and is merely created for you
to be in control of all the data fields. thus there is no error to be made by placing the
fields in the wrong group. more importantly, a custom field has the following public
properties available:
t
•
racking code Id
c
•
ustom field name
•
c
ustom parameter
•
c
arry-over option
•
s
tatus scope
the tracking code Id is the most important in regard to the actual tracking, as
this is what you deploy in your tracking script. continuing with the first examples of
creating a custom field to capture a document subgroup, the tracking script variables
would look like this:
version 4
var ACTION='07';
var DOCUMENTNAME='Wedding gift list promotions';
var DOCUMENTGROUP='Gift lists';
var _s_cf01='Wedding';
112
version 5
YWATracker.setAction(“07“);
YWATracker.setDocumentName(“Wedding gift list promotions“);
YWATracker.setDocumentGroup(“Gift lists“);
YWATracker.setCF(1, “Wedding“);
the custom field name is the friendly name that will be shown in the interface
when you want to create reports using this new dimension. this name can be changed
at any time, and it will affect data already collected as it is simply a lookup.
the custom parameter, carry-over option, and status scope describe the type of
data that we want to collect and how to treat it in the system.
let me explain the scope with an example. Imagine that as part of a sign-in pro-
cess you ask people to supply their gender and that you collect that information in a
custom field. As this information is the same throughout the whole visit (I am assuming
most people do not change their gender during a web visit), you would choose a session
scope. However, on the other hand, you might have a search function as described ear-
lier, where you collect the From Airport data. this data could have multiple values dur-
ing a single session, and you could choose to set the scope to no carry-over, as you do
not want to attribute all searches to one value. the carry-over options include:
n
•
o carry-over
•
c
arry-over until visit ends
