Thank you!
TL;DR Since I use Heap Analytics for basic user analytics stuff, I just use Heap's built-in click tracking mechanism to track "waves". Some ad blockers will block the analytics data from being sent — others let it through. It's been a while since I built that feature — I should probably update it to hide the widget altogether if you've got an ad blocker on.
As I wrote above, I use Netlify for hosting it, and I'd really prefer to use their analytics solution (more privacy centric), but it's a little too costly to justify for a personal site.
One question: I really like your Wave widget at the bottom of each page. How does the Wave mechanism work on the backend? It doesn't appear to send anything apart from setting a local cookie.