VDM Sessionization priority

Products

Cause

Here are the new Visitor identification/sessionization options for VDM in V9.4 (Fall 2010 release). These replace the older one illustrated further down.

Remember that these settings are only available for edit during profile creation. They cannot be changed later.

Option 1 – Default option for new profiles

• ?Use Webtrends Visitor Identification parameters? enabled
• ?Only count visitors that can be tracked across multiple domains? not checked.

Order of parameter processing:

• The loader looks for WT.vt_sid parameter first,
  • if not present, then we look for WT.vtid parameter,
    • if neither are present, then assumes unknown visit and visitor (1000000008000000001)

How are the parameter values used:

• If WT.vt_sid parameter found,
  • the visitor ID is taken from WT.co_f parameter if present,
    • if not present, then the loader looks for WT.co_d parameter,
      • if not present than the loader uses WEBTRENDS_ID cookie,
        • if none are present, then the loader assumes an unknown visit and visitor (1000000008000000001)
  • the session time is taken from the WT.vt_sid value
• If WT.vtid parameter is used (because WT.vt_sid absent),
  • the visitor ID is taken from WT.vtid. The loader will not use WT.co_f, WT.co_d, WEBTRENDS_ID even if they are present.
    • If WT.vtid parameter is not present, then the loader assumes an unknownvisit and visitor (1000000008000000001).
  • the session time is taken from the WT.vtvs value

Corresponding settings in the profile WLP file:

[sessiontracking]
startofvisitparametertype=4
visitparametertype=4

Option 2 – Default option for existing profiles

• ?Use Webtrends visitor identification parameters” enable
• ?Only count visitors that can be tracked across multiple domains” checked

How are the parameter values used:

• the visitor ID is taken from WT.co_f parameter if present,
  • if not present, then the loader looks for WT.co_d parameter,
    • if not present than the loader uses WEBTRENDS_ID cookie,
      • if none are present, then the loader assumes an unknown visit and visitor (1000000008000000001)
• the session time is taken from the WT.vt_sid value

Corresponding settings in the profile WLP file:

[sessiontracking]

startofvisitparametertype=1
visitparametertype=1

Option 3

• ?Use a custom Visitor identification parameter?

How are the parameter values used:

• The loader uses whatever parameter is specified in the UI for both Visit and Visitor identification. It will not use WT.vt_sid, WT.vtid even if present.
  • If the parameter is absent, then the loader assumes an unknown visit and visitor (1000000008000000001).
• The WT.vtvs parameter must also be present on every hit, and have a valid value.

Corresponding settings in the profile WLP file:

startofvisitparametertype = 2
visitparametername=
visitparametertype = 3

Option 4 – Not UI selectable

This option corresponds to a selection that was available in the V9.3 UI, but is no longer available. These settings will be retained unless a request is made to Support to modify them on the backend (manual change in the WLP file).

• “Use the alternate Webtrends Visitor ID (WT.vtid)” (see below)

How are the parameter values used:

• the visitor ID is taken from WT.vtid. The loader will not use WT.co_f, WT.co_d, WEBTRENDS_ID even if they are present.
  • If WT.vtid parameter is not present, then the loader assumes an unknownvisit and visitor (1000000008000000001).
• the session time is taken from the WT.vtvs value

Corresponding settings in the profile WLP file:

[sessiontracking]
startofvisitparametertype=2
visitparametertype=2