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!

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.

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