insights: landing page pings for GA launch

Created by: Joelkw

RFC: https://docs.google.com/document/d/1J-fnZzRtvcZ_NWweCZQ5ipDMh4NdgQ8rlxXsa8vHWlQ/edit#

I will make sure this RFC is done and approved by February 9th. Update: it's approved as of Feb 9th.

Prioritized list of pings, if we don't have time for all of them for 3.37.

Here is the figma with the definitions / locations.

This naming matches the RFC and assumes that each item includes both uniques and total, the same way we have it for the creation funnel docs. Top priority first.

1. Get-started-pageview
   1. Very important note on implementation – we should filter this out of the “insights pageview” we already collect. This should be its own category, and not a subset of the other category. So our normal pageview pings contain NO pageviews of the get-started-page, and the get-started-pageviews contain NO other pageviews. They are distinct sets, the venn diagram is two circles with no overlap.
2. Get-started-page-hovers are FILTERED
   1. Note: This is not the priority of collecting the hovers, but rather the priority of making sure we do not include them in our existing hover stats. If that means we just remove the event from firing, that is fine! It is important not to include hovers here in our other stats because hovers are a good indication of use of "actual insights they created" – since they did not create these insights on the getting-started-page, we do not want to include those in the normal hovers pings! See the later list item for the priority of otherwise separately collecting the hovers.
3. Get-started-primary-cta-click
4. Get-started-template-copy-click and get-started-template-use-click
5. Get-started-tab-[TABNAME]-click and get-started-tab-[TABNAME]-more-click
   1. Note this is "dynamic" and should match the actual tab's name where it says "[TABNAME]" so it'd show up as like "get-started-tab-migrations-more-click" for example
6. Get-started-big-template-click
7. Get-started-query-modification and get-started-repo-modification
   1. Note – we can debounce these, or just count them per pageview (so it’s max 1 time unless you refresh the page). That won’t tell us if the # of modifications matters to the conversion, but that’s more granular than we’re able to easily get in pings anyway (tying things to individual sessions isn’t something we can do in pings).
8. Get-started-docs-clicks
9. Get-started-page-hovers 10. Note on implementation – we should separate these hover counts from our existing hover counts. These can be in a separate json section – we don’t want them to impact our data counting of existing hovers.
10. Video-plays-clicks (we will have a video is my understanding)

Our "must have" goals would get us to implementing through number 5 on this list (the TABNAME pings), our "good state" goals get us to number 7 (so query/repo modification pings), and our "stretch goals" are to get all the way through this list.