Add-On Analytics vs privacy blockers

Hi,

for add-on / product developers, despite all the known privacy concerns, it is essential getting “user feedback” using at least basic usage analytics ( E.g. via Navigator.sendBeacon() )

On the other hand side, there’s many (equally legitimate) technical tools, and efforts (like “DoNotTrack” serttings) to block such data transfer.
Also, developers are legally required to explain any intended purposes of analytics data collection and use, and ask for user consent.

That means: to achieve this very legitimate goal, quite some effort to technically build, legally explain to users, and convince them to opt-in is required. And after that, some browser setting or blocker add-on used cancels all those efforts - despite the user has opted-in and given consent.

I am wondering: is there a best practice (or any way) how an Add-on developer can actually ensure he can reliably send analytics data to the intended URL / analytics tool ?

Any guidance appreciated.