Out of interest do all of your 34 variables have the potential to change
week to week or can some of them be handled through classifications?
Also, of the variable where classifications don't work because they
change week to week, how many have a known/limited set of possible
values? e.g. I'm assuming season has 4 fixed possibilities - spring,
summer, autumn, winter
If the issue is a timing issue (e.g. the browser navigating away before
the metrics call can happen) then you may want to take a look at this
method that attempts to avoid these issues:
This sounds like the getPreviousValue plugin is being called multiple
times in the same page load. One thing to check is that you are only
calling getPreviousValue when a page view occurs (e.g. not on link
tracking calls or other events). For instance, if you've put the
getPreviousValue function call in doPlugins it's easy to accidently
cause this to run multiple times as doPlugins runs all the time for
various reasons (not just on page view).
You could consider moving the aggregator rule above the referring
domains rule to give it priority over the referring domains rule - this
way there would be no need for the exclusion on the referring domains
rule. It's probably better practice to do it this way round and may make
it more simple to trouble shoot the issue e.g. if it you are not getting
aggregator traffic you know it is because either the query string
parameter is missing or does not contain the value you are looking for.
@yuhuisg - really interesting insight into how you approach this.... and
is very different to how I like to set up. I think it is one of those
situations where there are multiple approaches and there is no right or
wrong approach. Just for the record in case any one is interested here
is our approach... We have a Launch rule that always runs before
everything else that both calls clearVars and sets linkTrackVars &
linkTrackEvents to "none". We do this deliberately to create a
completely clean sl...
@Stewart_Schilling It's a fair point, and one I considered 🙂 But I
don't think I can get the configuration I wanted this way. I want
everything to appear in the console that would normally appear, plus
just the custom logs I've set in code using the _satellite.logger
function (i.e. none of the other stuff that launch outputs by default
when you enable debugging) - Launch seems to split out so much stuff
when we have debugging is enabled that it just swamps the console.
Description -Measuring the time between events is an area that is often
asked about by our users of Adobe Analytics and is an important measure
of improvement for many processes. At the moment if we want to find the
time between events we can set custom code up for each specific scenario
and pass this into an event, build some calculated metrics etc. but this
is a very clunky and inflexible way to operate. I can't help thinking
this is an area that Adobe could do something really special in. I'm...
Description -Currently when debugging is enabled all events are logged
to the console which makes it very hard to see what is going on. It
would be great if there was a way to select which types of events were
written to the console. Often I just want to see the custom logs
generated where I've used the _satellite.logger function in custom code.
Why is this feature important to you -It would make debugging easier. At
the moment I find myself often resorting to using console.log because it