Expand my Community achievements bar.

Join us January 15th for an AMA with Champion Achaia Walton, who will be talking about her article on Event-Based Reporting and Measuring Content Groups!

Fix low traffic bucket (ideally remove it and it's function completely)

Avatar

Level 7

5/22/13

In a large organisation with a secondary report suite the low traffic bucket has far reaching implications for data integriy. For example a primary report suite may not ever hit the low traffic limit and as such is able to accurately report on items such as url's and page names. However when you go to the secondary report suite which has many more values from other primary report suites we commonly find that items are bundled int he low traffic bucket. 

 

This creates significant reporting descepancies between the two report suites. Which means depending on what type of query and which report suite they are looking at they can get very different or simply missing data when comparing the two.

 

As you can imagine consistency in data across primary and secondary report suites is key, in establishing trust in data and driving data's use through out the organisation. 

 

I believe for larger implementations the use of the low traffic bucket, undermines the entire implementation. 

 

My suggestion to Adobe is to remove this from all reports and products and report on the full data set regardless of size.

1 Comment

Avatar

Level 1

12/8/22

I am seeing this happening right now. Our org. uses 2 report suites ....is there a work around aside from the above suggestion? thanks for your insight