Best Practices: Storing User Action List

@blueback09, I saw your post on this topic.

We’re considering doing something similar. Was wondering if you could how you structured your database for this, and why? Also, any insights or best practices that may help us implement it more wisely?

Last, did you look at using tools like Mixpanel and Keen.io for this? If so, any particular pros/cons vs. doing it within Bubble?

Thanks!
Scott

I’ve got a table called “usr-act-audit” with fields “action”, “user”, and a bunch of others that reference other tables. Then I’ve got a lot of actions in workflows that record a new usr-act-audit when something interesting happens. Usually it will also get a reference to the other thing that’s being changed. Like if someone makes a new ticket in support the usr-act-audit will record the user, a phrase like “made a new ticket in support”, and a reference to the ticket created in a field called “ticket”.

I haven’t actually used it for analytics much. I built it to try to catch obscure errors to speed up my troubleshooting efforts. Like, if a user complains about something, I can go in and review their actions to have a better idea what they actually did.

Also, I haven’t tried integrating any dedicated analytics like Mixpanel or Keen yet, so I can’t compare.

2 Likes

Thanks for sharing. Seems useful.