be careful with tracking ajax requests. we once set it up to track ajax and hell broke loose because each and every ajax request was  tracked - something you definitely don't want.

Agree. Right now we use our own calculated metric bounce rate which looks at Visit Container: Hit Depth <= 3 divided through all Visits

Open the developer tools in your browser (usually F12), go to Network tab, check the logs to persist and filter for the string /b/ss/ Then you should see all the tracking calls sent to the Adobe server. Click on the individual calls to see its parameters. You can check if the proper variables and/or...

Can't you test the journey? Easiest thing is to test the journey and see if everything is firing as expected.

In general "none", "unspecified", "other" should be named coherently. Sometimes it displays "unspecified", but if you want to filter it out you need to type in "none". Very confusing and incoherent.

Very important feature to analyse user behavior indeed! I need myself to help with some workarounds which are never exact (based on the entire session etc.).so +1!

It should be always clear which "total" is displayed: it is not the same behavior when filtering the data and when segmenting  the data! Many users are confused and do not know what "total" means in the current context.

Very important feature missing! Soemtimes we want to remove some specific query string parameters and we cannot do that right now without throwing away the complete query string.

Very important feature indeed!

Open the developer tools in your browser (usually F12), look for the network tab which displays requests you are sending, look for the tracking request (usually it contains the pattern "/b/ss/" ) and then you can see what you send to Adobe. v's are eVars, c's are props. But it also depends on the im...