There are two major challenges with building a robust analytics solution for the privacy era: architecture and privacy operations.
In terms of architecture, things that are cross-site (i.e., a script that sends a data to a service that is not yours) are getting blocked by ad blockers and browsers like Brave. This is because, even with the best of publicly stated intentions, there is no way to know what the third-party will do with the data.
Privacy operations itself is exceptionally challenging, because you need to manage consent and purpose, provide auditability, support DSAR, etc. -- unless you operate at the strict minimum (typically what falls within “legitimate interest” under the GDPR).
My company, Blotout (YC W21), approaches this with a cloud native privacy data engineering platform that lets you ingest event and ETL data into to your own lake, and provides a complete privacy operations suite. Since it’s same-site, you’re not blocked as a tracker. And because it pulls and unifies all of your data in your own infra, it’s vastly more efficient than a third-party stack and it lets you do things with you data that you can’t when it’s spread across providers.
Of course, for your personal blog this might be overkill. :)
As the founder of a tech-driven charity and with some volunteering experience, I want to suggest another approach.
The skills that let you deploy your technical abilities are often sorely needed in this sector, particularly when an organization depends on volunteer labour.
As an example, my father is an experienced civil engineer who leads the development and refurbishment of major hydro generation facilities in his day work.
One of his primary volunteer activities, however, is hustling casseroles for a significant homeless shelter and kitchen in a large city. He is frighteningly effective because of all the skills that also make him good at his job — organization, process, people, etc. There’s often a deficit of this in volunteer efforts.
On the flip side, if you do want to use your technical chops, consider how you can do so in a sustainable way so you don’t create dependencies that put important processes at risk. I found it better to fundraise and pay professionals for important functions.
In terms of architecture, things that are cross-site (i.e., a script that sends a data to a service that is not yours) are getting blocked by ad blockers and browsers like Brave. This is because, even with the best of publicly stated intentions, there is no way to know what the third-party will do with the data.
Privacy operations itself is exceptionally challenging, because you need to manage consent and purpose, provide auditability, support DSAR, etc. -- unless you operate at the strict minimum (typically what falls within “legitimate interest” under the GDPR).
My company, Blotout (YC W21), approaches this with a cloud native privacy data engineering platform that lets you ingest event and ETL data into to your own lake, and provides a complete privacy operations suite. Since it’s same-site, you’re not blocked as a tracker. And because it pulls and unifies all of your data in your own infra, it’s vastly more efficient than a third-party stack and it lets you do things with you data that you can’t when it’s spread across providers.
Of course, for your personal blog this might be overkill. :)