search

PolicyEngine / policyengine-app

PolicyEngine's free web app for computing the impact of public policy.
GNU Affero General Public License v3.0
37 stars 101 forks source link

Add Analytics tags on buttons #27

Open MaxGhenis opened 1 year ago

nikhilwoodruff commented 1 year ago

Made a start, analytics is up and running but we could add plenty more event loggers

anth-volk commented 9 months ago

Are we still doing this?

nikhilwoodruff commented 9 months ago

I think it's still worthwhile

dotslashbit commented 8 months ago

@anth-volk Can you provide some more clarification to this. Do we need to add analytics tag to each and every event or there's some specific condition on where to put analytics tag

anth-volk commented 8 months ago

Let me provide some background first, because perhaps we could use your best judgment on this. We're hoping to track a few things - the number of times users access certain features/functions of the app, how users access these features/functions, and who these users are (where possible). We're not interested so much in tracking particular events as we are particular user flows: if someone clicks on the button to implement a reform on IRS income tax bracket 7, what are all of the next things they do within their user session? How are they going about it? What platform are they on? And what sort of user are they (again, where possible)?

Perhaps the best first step to this would be developing some sort of system to encapsulate that user flow. Note that we also provide users a cookie consent pop-up, so we can log cookies.

Do you have any ideas as to how we might proceed with this? Happy to discuss.