The event funnel is one of the SQL queries I have imprinted in my brain. Basically, the event funnel showed us what part of the product we should be looking to change if we wanted to drive the highest increase in user engagement. So, we reached out to some of the users who got stuck at this step and brainstormed some improvements that we could make to help reduce the friction in getting a database connected. the screen giving instructions about how to connect to a database) and successfully getting a database connected. This event funnel makes it really clear that the biggest drop off point is between steps 3 and 4: seeing the connect modal (i.e. I used our awesome tool, Beacon, to run the query and share the results directly with the team in Slack: I built an event funnel for users starting at "I installed the app" and going to "I executed a query". So, we have an action ("execute a query") that we're trying to optimize the completion rate for, and we know the steps leading up to that action. Specifically, we wanted to figure out why people weren't running a query with Beacon after installing it. Once we launched it, we wanted to understand how users were engaging with the product. We built a product, Beacon, that lets you write, run and share your SQL in Slack (you can add it to your workspace here!) How we used event funnels to drive higher engagement with Beacon.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |