Hi @ARSARI
could it be that you are seeing "collect" calls in your network tab instead of "interact" when you filter for "/ee"?
These are typically sent upon page navigation when you choose "document will unload" on the tracking event and implicitly switch to sending a beacon and no longer a POST / GET request. This beacon or ping should signal the browser that he should execute the request no matter what i.e., also not terminate it upon page navigation.
These are notoriously hard to debug, actually you will only see their payload when looking at the network request's "payload" tab in e.g., Chrome.
All extensions I have seen so far won't be able to give you insights on this kind of requests. Typically you will just see that they're there, but not any additional data that is transported.