Discourse Narrative Bot Data Explorer Queries šŸ¤–

Community Building Data & reporting
,

AI-generated summary

:robot: The discussion revolves around creating Data Explorer queries to track user interaction with @discobot. david shared two queries: all-narrative-bot-interactions.dcquery.json to show a list of users who interacted with @discobot in the last year, and narrative-bot-summary.dcquery.json to group interactions by current_state.

david noted that thereā€™s no info about the sequence of states in the database, making it difficult to show percentage progress through the track. mcwumbly suggested summarizing the number of completed steps, but david clarified that previously completed steps arenā€™t stored. david added another query to group by current_step, which might help identify where users get stuck on the track.

1

In the interest of tracking user interaction with @discobot, here are are some data explorer queries.

If anyone can think of a way to actually show a percentage progress through the track that would be awesome! But as far as I can see thereā€™s no info about the sequence of states in the database :frowning:

To use these queries, download the one you want, and import into the Data Explorer Plugin

All User Interactions

all-narrative-bot-interactions.dcquery.json (1.6 KB)

Shows a list of all users that have interacted with @discobot in the last year (configurable) and shows their current state in the track:

Screen Shot 2017-05-20 at 15.09.23.png1079Ɨ334 28 KB

Summary of Interactions

narrative-bot-summary.dcquery.json (1.6 KB)

Shows all interactions with discobot in the last year (configurable), grouped by current_state. This can be used to see which state users got stuck on. Results will look something like this:

Screen Shot 2017-05-20 at 15.08.22.png597Ɨ404 25.7 KB

I've made this post a wiki, so others can add any `@discobot` related queries they come up with
2

Can you summarize the number of completed steps and divide that by the total number of steps?

3

As far as I can tell, previously completed steps arenā€™t stored. All weā€™ve got is a string describing the ā€œcurrent stateā€. And that string has no info about the position of that state in the track

4

Iā€™ve added another query (see first post) which groups by current_step. Iā€™m thinking this might be useful to show which step of the track users get stuck on. I donā€™t have many new users on my community since introducing discobot, but Iā€™d be interested to see what data other people get! :slight_smile: