On all routes in the OCM Portal, we want to set a Javascript variable with metadata that can be passed up to the Insights Chrome to add context to pageview tracking.

All pages should identify what OCM plan ID is relevant (ocp, osd, moa, etc). On some pages, like the cluster details page, this will need to be determined dynamically. On pages like the OCP install pages, this can be a static value tagged on the pages.

Four routes are dynamic with ID's in them, and we'll want to tell our tracking system to ignore the ID's when logging those as well.

Exact variable/mechanism TBD based on RHCLOUD-19413, but something like...

For route '/details/s/:id':

window._analytics = {
  ocm_resource_type: 'osd',
  page: {
    path: '/details/s',
    title: 'View Cluster'
  }
}

Details on tracked pages in OCM are outlined here: https://docs.google.com/spreadsheets/d/1C_WJWPy3sgE2ICaYHgWpWngj0A3Z3zl5GcstWySG9WE/edit#gid=0

Acceptance Criteria

1. Add method to OCM main App page to track/trap route changes
2. Verified via normal analytics testing

Follow On:

• Add browser url changes for each wizard step in order to track analytics