Create SelfDescribingEvent for Wizard usage #192
Conversation
Yay! Awesome :) Interesting that the previous data isn't available! One way I've got around this in the past (which may or may not work with Backstage) is to add it into the url as a parameter as we navigate through the steps so that in the final view we can retrieve it. I still say we should make ministry mandatory in the metadata though! |
| } | ||
| } | ||
| enableActivityTracking({ | ||
| minimumVisitLength: 30, |
There was a problem hiding this comment.
curious what this is doing!
There was a problem hiding this comment.
The activity tracking cause page pings to fire when users are engaged on the page.
So, if a user has the page focused and they're scrolling or moving their mouse then the ping will go off every 30 seconds. If there's no activity then the pings stop.
I'm not sure if this metric is visible in the dashboards though.
There was a problem hiding this comment.
This could be useful if we want to ask dan in future to track "drop off" on wizards :)
I setup the analytics to track the "create" event which fires when Wizards are run. Specifically, when the "Create" button is clicked. There are also some formatter changes.
Here's what the event looks like in the Snowplow plugin. Its type appears as "SD Event: action", and it includes the action "wizard-complete", the name of the Wizard, and time saved in minutes.
The schema displays as Unrecognised[sic], I assume because Dan & Co haven't added it to their schema registry yet, since this is the schema spec they provided.
Ministry is blank because the Wizard's user input is not included with the create event.
I think including it is reasonable but non-trivial. Most likely requiring a custom scaffolder action that we add to the Wizard.