it's a hard problem to crack. hence why there aren't many solutions/strategies to work around it. hell, tag management services like Google are on easy privacy

it's a hard problem to crack. hence why there aren't many solutions/strategies to work around it. hell, tag management services like Google are on easy privacy lists used by most third party blocking software. if analytics tracking is imperative to measurement of your site and there's little to no profiling (lean toward no profiling) you can typically get your endpoints/domains removed from blacklists by simply submitting a pr with your reasoning. if you have examples even better. if you're profiling a user and need real-time engagements to sell impressions/advertising to that user based on site behavior then i think you're just SOL. a roundabout solution could be to store events on the client and attach them to some user entity. maybe some queue of action entities of time, type, and any sort of payload. at the end of the session or maybe when you're updating the user entity, you can process those queued events as you normally would. idk if these are great solutions, but hope it sparks some ideas for you and your team.