1193448 - Add Google Analytics events to new AAQ flow

Status: RESOLVED FIXED

(support.mozilla.org :: Knowledge Base Software, task, P2)

Description

[Kadir Topal [:atopal]]

We need to fire the following events in the new AAQ flow:
* product is selected
* topic is selected
* user types in input field
* user types in textboxt
* user clicks on one of the suggested articles
* user clicks on submit
* submit fails due to missing data (username, subject, etc)

This is a preliminary list, we might need to make changes to it.

Comment 1

[Michael Cooper [:mythmon]]

This should be fairly straight forward. It will probably be about 2 points, but I'm not going to mark that in the whiteboard field until this bug is fleshed out enough to be ready to start implementing.

Generally, it would be good to have specific event names for these (or specific url patterns if we want to do extra pageView events). We could make them up during implementation, but documenting them in this bug is probably a good idea either way.

For the "user types in..." events: This is the first time they type in the field, right? Not a repeating event as they continue typing?

Do you want any events related to user authentication or registration?

Comment 2

[Kadir Topal [:atopal]]

(In reply to Mike Cooper [:mythmon] from comment #1)
> Generally, it would be good to have specific event names for these (or
> specific url patterns if we want to do extra pageView events). We could make
> them up during implementation, but documenting them in this bug is probably
> a good idea either way.

Event Category: Ask A Question Flow - SPA 

Event Action (in parenthesis):
* user loads the page                                  (AAQ SPA loaded)
* user is already logged-in upon loading the page      (preregistered)
* user selects product                                 (product selected)
* user selects topic                                   (topic selected)
* user types in input field                            (title input)
* user types in textbox                                (details input)
* user clicks on one of the suggested articles         (suggested article selected)
* user clicks share data                               (share data selected)
* user clicks "show the data I'm sharing"              (showing data selected)
* user types in email field                            (email input)
* user types in username field                         (username input)
* user types in password field                         (password input)
* user clicks "show password"                          (show password selected)
* user clicks on submit                                (question submitted)
* user clicks on "I already have an account"           (login requested)
* submit fails due to missing data or incorrect data   (username, subject, etc) (submit failed)
** event label is the error
* submit succeeds                                      (question posted)

 
> For the "user types in..." events: This is the first time they type in the
> field, right? Not a repeating event as they continue typing?

yes, only the first time they start typing


> Do you want any events related to user authentication or registration?

yes, see above.

Comment 3

[Michael Cooper [:mythmon]]

I think this should be pretty easy, except possibly the validation related ones (we might have to retool that a bit, I'm not sure). Rehan's work on re-organizing the new AAQ will actually help a lot here since it makes it a lot clearer when a user gets to a particular part of the AAQ.

I'm going to mark this as 2 points, and make it block on the AAQ styling bug.