More Analytics Events [AARD-2097]

[AlexD717]

Task

Add more analytics events

AARD-2097

Symptom

Our analytics system currently only tracks basics analytics and robot import events. This means that there is some data about how users use our product that could be helpful to us, but we don't record.

Solution

Add more analytics events that could be helpful

Match Mode Events

• Match Start (called on match start)
• Match End (called on match end)
• Match Mode Config Created (created config with gui tool)
• Match Mode Config Uploaded (successfully uploaded a valid json match mode config)
  These can be helpful to see how match mode is utilized, and what is tools are most often used.

Graphic Settings Event

• Calls when graphics settings are changed
  Already send events about average fps and performance sample. Can be useful to identify what settings most users are using.

Drag Mode Events

• Drag Mode Enabled
• Drag Mode Disabled (plus how long it was enabled for)

Can be useful to determine if drag mode is being utilized and how much

Mode Selected Event

• Called when pressing "singleplayer", "multiplayer", or "load default" in main menu.
  Useful to determine which mode is most used and how many people actually tried to use multiplayer/singleplayer

Verification

Navigating onto our google analytics page and going into debug view, results in the events being called at the corresponding time with the appropriate parameters.

---

Before merging, ensure the following criteria are met:

• All acceptance criteria outlined in the ticket are met.
• Necessary test cases have been added and updated.
• A feature toggle or safe disable path has been added (if applicable).
• User-facing polish:
  • Ask: "Is this ready-looking?"
• Cross-linking between Jira and GitHub:
  • PR links to the relevant Jira issue.
  • Jira ticket has a comment referencing this PR.

[ryanzhangofficial]

Definitely will unearth important insights!