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: https://experienceleague.adobe.com/docs/analytics/implementation/vars/config-vars/usebeacon.html?lang=en 

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 cal...

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 t...

@Ryan_Monger That is great news!  - thanks for the update

@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 othe...

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 th...

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 u...

Figures that you were working around an issue.... Particularly interested to hear that you've noticed some issue with the JavaScript promises... we've also noticed that it doesn't always seem to wait for one action to complete before executing the next (even though we got "run rule components in seq...