I agree with @Brian_Johnson_ that it sounds like a linkTrackVars issue. If you haven't already it may be worth adding a console log just before you send the analytics beacon to see what the linkTrackVars value is at this point.

If I have a two rules that trigger from the same event and one rule at order 50, and the other rule at order 60 - will the rule at order 60 wait for the rule at order 50 to finish before executing if we have "run rule components in sequence" enabled? We are seeing some weird timing stuff going on wh...

In order to run 2 report suites with different configurations in one Launch property, I think you are going to have to set up one of your report suites on separate tracking object using s_gi().  See the following help article:s_gi() | Adobe Analytics You'll be able to use the wizard driven Adobe Ana...

I think you may need to give us an idea of the report that you are trying to generate off the back of the data collected, then we can advise how best to do this. Are you able to mock up a table(s) with the report output you want at the end of this?

@amgup is correct, you need to set the list var in custom code. The only thing to add is that if you are passing a list var on a custom link tracking call you need to remember to add the variable to s.linkTrackVars in your custom code or else it won't pass through to Adobe (it's easy to forget this ...

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

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