Hi Matt,I suppose you are noticing these values in raw data/data feed. If yes, such values can be expected for BOT Hits, which can be ignored.However, if you are able to see it in live server calls while debugging (as suggested by Pratheep), please share the public facing URL so that we can check on the same.

Hi,You'd need to reach out to ClientCare@adobe.com. They should be able to help as it may require some changes from the back-end.

Hi,Per your question, it seems both the pages are reporting in the same report suite. If yes, the best way to segregate the data, would be to pass a unique identifier using 1 custom variable, for both the pages. For an example:For version A, pass prop1 = Ver ASimilarly for version B, pass prop1 = Ver BThe one above is just a generic example. Choice of variable and the value being set is completely up to your requirement.Note: When you say Document Path, I'm assuming it's the localhost path being...

Hi,As you rightly mentioned, the error code: 409, indicates a conflict and mostly it's because someone is already connected to that stream.If you feel above isn't true for your scenario, this would require further debugging for this specific end-point and I'd suggest reaching out to ClientCare directly.

Hi,The X-Forwarded-For will work as that's what our server looks for, however, you'd need to ensure that the header must contain the correct IP i.e. the private IP and not the proxy server's one.Thanks.

Hi,A fallout is always at Visit level hence Page View isn't an option available because it won't hep define Fallout.As far as I can understand by your question statement, it seems you want to check how many different pages Visitors viewed before reaching the checkout page to complete the transaction. If yes, then you should use any of the Page Flow reports, whichever best suits your data need.If you have a different requirement, kindly elaborate.