The status are all 200.  

As the title states, there are two specific Adobe rules (one is triggered via custom event and the other is triggered by a CSS entering viewport) that are firing but the data is not getting into the debugger.  In the browser's network tab, I see that all the variables are being captured.  However, t...

Does the 500K refer to the TOTAL unique value or is it timeboxed? 

I have discovered an instance where two metrics have inflated numbers. I have verified this using "Custom Link Instance" which shows the correct numbers for the traffic.  I want the inflated metrics to show the values we have for the "Custom Link Instance" metric.  How should I go on about creating ...

Thank you for your response. It has been 1 week since I removed the rule.  I will wait until our dev team completes a release in the next week or so to see if the caching issue is updated.  

This is not limited to stacked bars, I am seeing this on "Donut" visualization as well. 

I did some testing on our development environment to capture the Launch rule name as it fires. I used the method below (use runtime environment for the data element).https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/capture-adobe-launch-rule-name-in-a-prop-variable/m-p/58289...

Background: With the limited number of evars and props - we are struggling to set aside enough variables to capture all the different attributes for each of the 30+ products we currently track.  My question is: what are the pros and cons of setting aside (let's say - 10-15 generic evars and props) t...

Thank your reply - this is what I was looking for.    We wanted to find the method of capturing the adobe rule name first prior to revamping our rule names.   We intend to shorten the names and apply a processing rule to parse the information in adobe analytics.   

Thank you for the reply. I utilize the _satellite.setDebug(true) during my Q/A but the purpose of having it in a prop is to debug for cross-domain tracking and auditing data integrity as opposed to Q/A for implementations.