Adobe Experience Cloud Debugger displays duplicate hits

[LiFa]

Hi,
I'm a frequent user of the Adobe Experience Cloud Debugger. Main purpose is to verify data collection as it has always displayed the captured data very well. There are multiple different tools to achieve the same goal. If you use the browser built in Network tab in dev tools you usually see two AA requests for a page load, one redirect request (status code 307) and one standard request (status code 200). This was one great benefit with debugger, that it only showed the "true" page load hit with status code 200. However, that seems to have changed very recently.

Getting multiple hits for each load is soon making the validation a bit teadious, especially if you intentially send more than one request on a load. I haven't found any way to filter the hits to only display the status code 200 hits. Is there any way to achieve the same functionality in Debugger as it has been before i.e. to only display the 200 hits?

[Jennifer_Dungan]

I'm having the same issue

It makes testing so much harder... especially if you need to look at Post-Processed data which adds yet another column for the same hit... it's now very hard to tell "debug" columns from "real" tracking, or to see if there is in fact a duplicate tracking call inflating stats....

I got frustrated and stated using Omnibug... There is a setting there to show redirected entries, or not... 

Now, I don't get the redirection if the Debugger isn't open.. but if I need "post-processed" this gives me additional context about how many calls are being made....

The official Adobe debugger has no filtering options that I have seen...  I actually had talked with a PM for that tool about 3 years ago, asking for filtering (even just to cut down on the unnecessary rows - either hide or collapse by default, re-ordering important rows closer to the top, etc)... they seemed to like the ideas, but never followed through