Comments on: Cool Custom Report: Campaign latency, pt 1

By: rocky

rocky — Sun, 24 May 2009 14:19:36 +0000

Scott, no, it doesn’t take into account visitor history; it will only filter visits where, in the current visit, there is a WT.mc_id on the entry page. In other words, visits that came from a campaign today, this same visit.

Did you know that “originally came in through Paid Search” is a possible filter? Your comment makes me realize we need a post on all the available visitor history campaign variables.

By: Scott Ross

Scott Ross — Wed, 06 May 2009 15:55:15 +0000

For the “The custom filter that makes it work” section if I create the new filter using the campaign variable does this take into account visitor history? The reason I ask is I was going to apply the same filter to a report I have built for Natural Search as I am using Most Recent Search Engine Organic as my primary dimension and I know this doesn’t by default exclude someone who may have original come in through Paid Search and then came back to the site Organically.

I am trying to prevent crossover with Paid and Natural Search

By: Mike Mc

Mike Mc — Wed, 04 Feb 2009 14:45:21 +0000

This makes much more sense than what I was getting out of WebTrends before. Adding that filter changes everything.

And this is much clearer than anything I’ve been reading on campaign latency on a certain other big time analytics guru blog.