Tips, tricks, and pokes, just WebTrends Analytics
Random header image... Refresh for more!

Cool custom measure column: Number of first-time visits

This is a nifty extension of the generic create-custom-measures-based-on-KPI-pages post that we did a couple months ago.

You already can easily get reports on New vs Return Visitors, and you can use New vs Return as a dimension combined with something like Campaigns as another dimension.  Or you can use New and Return as filters in custom reports.  This is a little different, and we think it’s actually better.  It’s not a dimension (a row called New or Return), it’s a measure (a column, with numbers under it).

We’re calling this measure ”First-Time Visits” and it makes a column that shows the number of visits that were visitors’ first-ever visits.  It’s very cool in reports on campaigns, search terms, search term groups, or other “source of visit” reports.

It uses one of the important, but hidden, parameters that are created by the very very smart SDC server when it processes hits.  It’s possible only if you collect data using SDC (SmartSource Data Collector).  Normally, WebTrends uses this parameter in reports such as New versus Return Visitors.  We piggy-back on it for this special custom measure.

Reality check

You DO want to know which traffic sources are bringing in first-timers, right?  Of course you do.

Think about it.  One of the big wins for any banner campaign or affiliate site or paid search ad or organic search keyword is bringing first-timers to the site.   To introduce people to your wonderful, engaging, helpful, valuable and well-organized site and to let the site do its magic and induce these newcomers to buy, come back over and over, or whatever it is that your site is supposed to do.

How-to

Here’s how to make a First-Time Visits measure, in detailed step-by-step for those who haven’t done something like this before.   We’re following the procedure from the create-custom-measures-based-on-KPI-pages post .

  • Open the WT admin screen and go to:  Report Configuration >> Custom Reports >> Measures >> New Measure
  • Name the measure something like “First-Time Visits”.  Same for the column name. 
  • “Value to Base On” is Query Parameter and “Parameter Name” is “WT.ti” - weird, but trust us. 
  • Ignore the Advanced button and go to the next screen.
  • “When to Measure” is “Hits that Match Specified URL.”  It’s the last choice in the dropdown menu. 
  • For “Do you want to sum this measure across the visit” choose “YES.”
  • In the “URL Expression” window, enter “*” using Equal To.
  • Click on “New URL Parameter” to open the URL Parameter window.  In that window, enter “WT.vt_f” as the parameter name.  Yes, WT.vt_if is the magical internal SDC parameter that SDC sets to a value of “1″ if a visitor doesn’t have a pre-existing WebTrends cookie.  (it sets it to a value of “2″ at other times, but we only want the 1’s.)
  • Parameter Value should be Equal To the number “1,” using the Text radio button
  • Click Done.  You’ll go back to the mean Create Measures screens. 
  • Go to the Format tab and set it to “No Currency” and 0 decimal places
  • Save

Now you’re ready to add the measure to an appropriate custom report.  It works great with a report where the dimension is Campaign ID (WT.mc_id on entry page, in other words). 

IMPORTANT:  Note the above statement.  We get mail about this from people who skip over it.  When adding the measure to a custom report, specify the Method as “COUNT”.  The default is Sum.  Don’t use Sum.  Use COUNT.

Postscript:

Do we need to mention that people who delete their cookies or use multiple computers will mess up any means of identifying them as repeaters or first-timers?  Or that browsers that refuse persistent cookies can’t be classified as repeaters or first-timers?   The results won’t be perfect.  But they’re pretty darn useful anyway.

Share:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google

Tags

, , , ,

Somewhat Related Posts

  • Cool custom measure column: PPC, email, banner visit counts
  • ...
  • Miscellaneous Candy Jar post #2
  • ...
  • How to display any KPI page as a measure column
  • ...

    6 comments

    1 Bryan Cristina { 01.26.09 at 9:42 am }

    Excellent idea. Most of our measures are pretty stacked up in our reports, but I think this one will be a nice addition. Shame WT kills all your data when you add a measure, though. IIRC if you change a measure it’s fine, which doesn’t make sense, but it’s better than losing everything.

    Might be a good idea: have a few “dead” measures in a report. When you find a new one you want to add, edit the specs of that dead measure and WT should simply add that data to the report as time goes on. It won’t back-process that new measure, but it won’t invalidate the previous ones either.

    2 rocky { 01.26.09 at 9:54 am }

    I like the spoofing idea!

    Bryan, you talk a lot on Twitter about measures being important in your practice. Got any interesting ones to share?

    3 Andreas Beckman { 01.26.09 at 10:42 am }

    Another discovery of genius, in front of our eyes all this time. Thanks, this will replace some awkward custom reports.

    4 Bryan Cristina { 01.27.09 at 1:20 pm }

    Well, on Nationwide.com we use them for events that happen all over the place on our site. Quote, logins, signups, contact us, and plenty of other ones that various areas have focused on.

    And then after building reports with all those events as measures we’ve changed the dimensions to plenty of other things we’ve focused on – certain parameters we’ve placed here and there, campaigns, performed an on-site search, even language.

    With the way WT works with the session parameters, basically if we set a particular parameter that may happen during their visit, we’re able to tell all the other events/measures they did during their entire visit, even if the parameter only happens once. It’s quite powerful and I wish they talked about it more in their documentation.

    5 Kerstin Bailey { 01.27.09 at 7:42 pm }

    Okay, I gotta ask. Why WT.ti?

    6 rocky { 01.28.09 at 7:55 am }

    Three not-very-strong reasons. First, we needed a parameter that would be in every single hit. Lots of choices there. Second, we wanted something that was not numeric, i.e. that would cause something to break in the resulting report if a user accidentally set the Method to SUM or AVERAGE. Otherwise people would get numbers, very odd numbers, but not weird enough to question whether they had set up something incorrectly. Third, we pestered WebTrends Professional Services about it before publishing it, and found out that they were already using this trick and had chosen WT.ti. So we decided to be consistent.

    A better solution would be a parameter that doesn’t exist right now, but that we think should be added to SDC as a feature. That parameter would only ever have a value of 1, and would be on every hit, and would have a name that meant something. With a value of 1, it could be used for various hit-counting things. We wrote a CDT script that inserts this parameter into every hit and gave the name “WT.uno” to the parameter, though we played around with “WT.unity.”

    That script is supplied in the second post of our KPIs-as-measures post, the post that was intended for people using server logs. We could have put the CDT script into the first post that was aimed at SDC users, but we thought the whole thing was already complicated enough and WT.ti is dependable.

    Glad you asked!

    Leave a Comment