Arena Data


Arena Data mennesker
 
. . .
 
.
hjem   produkter   nyheter   kurs   konferanse   kundestøtte   om arena
 
 
 

Nedlasting av dokumentasjon | Support skjema | Kontakt oss

 
 



How to configure WebTrends using meta tags

These pages are samples to demonstrate how you can use meta tags to configure WebTrends automatically. For source examples simply "view source" in the sample files here.

Content groups with subgroups    -    Scenario analysis    -    Campaign

Content groups with subgroups

When you define content groups in the WebTrends product configuration itself, you do only have access to one level of groups. But if you use the following meta tags, you can generate groups and also subgroups automatically, through the content of the pages, without having to do any configuration in WebTrends. In the following examle these two meta tags are defining the page to be part of the main group "Test" and the subgroup "Pay".

<META name="WT.cg_n" content="Test">
<META name="WT.cg_s" content="Pay">

Scenario analysis

Scenario may be set up manually through the WebTrends configuration, or party automatic using meta tags. Even if you use meta tags, you have to define the name of the scenario and the steps. These are the meta tags:

  • WT.si_n : Name of the Scenario Analysis
  • WT.si_p : Identifies the step by name.
  • WT.si_x : Identifies the step by position.
You should only use one of the meta tags WT.si_p and WT.si_x. We recommend using WT.si_p, and then defining the position in the WebTrends GUI.

When the above tags are present in the pages, you have to do a definition of a new scenario analysis in WebTrends. The sample pages here are set up like this:

Scenario Analysis - SmartSource Identification String:
Arena Test Shopping

Then the steps are defined like this (4 steps):
SmartSource Identification String:
Start
Shop
Pay
Finish

Campaign

It is easy to set up WebTrends to track and measure campaigns. This way you can measure the exact value of each campaign, being external links to your site, paid advertisements, e-mail campaigns or other links. Just make sure you add the standard tracking parameter adviced by WebTrends. Examples of page name before and after adding tracking parameter:

Before:
http://www.site.com
http://www.site.com/page.asp?id=33333

After:
http://www.site.com?WT.mc_id=12345
http://www.site.com/page.asp?id=33333&WT.mc_id=12345

The parameter name "WT.mc_id" is a signal to WebTrends saying this is a visit to be tracked as a campaign. The value "12345" will show up as the name of your campaign. You may have as many names as you like, and you may replace the name by mapping files and drilldown information, say replacing "12345" by "Banner", "Newspaper", "Large".

To get reports based on the campaign functions you have to turn on the following in your WebTrends profile for tracking purposes:

General - Visitor history
Enable visitor history
Turn on (enable):
  Campaign History
  Search Engine History
  Most Recent Search Engine Duration
  Visit History
  Purchase History
  Custom Visitor Segmentation

Then turn on the following Custom Report to collect data into pre-defined reports:

Adcanced
Customer reports
Turn on (enable):
  Same Visit Campaign ID

Example of meta tags

<META name="WT.cg_n" content="Test"> ==> Content group = Test
<META name="WT.cg_s" content="Pay"> ==> Sub-content group = Pay
<META name="WT.ti" content="Pay - Step 3"> ==> Page title = Pay - Step 3
<META name="WT.si_n" content="Arena Test Shopping"> ==> Scenario = Arena Test Shopping
<META name="WT.si_p" content="Pay"> ==> Scenario step name = Pay
<META name="WT.si_x" content="3"> ==> Scenario step number = 3

Support and more info

These are just some simple demonstration samles. If you have questions feel free to contact us at Arena Data AS.


   
.
.
.
    arena data as | meierisvingen 2 | 1383 asker | e-post: | tlf: 667 667 00