Bugzilla

Because we are not including page url on click or other non `page_load` events. It would be very helpful for analysis of what happens on a given page to have a page_id metric on all the glean.js pings that is incremented or updated on whenever a new page is loaded.

We can create this in analysis but it makes for more complicated queries, see the following query to build page_ids:
```
select
    *,
    -- Increment the page_id every time we see a page_load per session and ordered by submission time.
    sum(if(event_name = 'page_load', 1, 0)) over (partition by client_info.session_id order by submission_timestamp asc) page_id
  from `moz-fx-data-shared-prod.debug_ping_view.events_stream`
  where submission_timestamp >= timestamp_sub(current_timestamp(), interval 3 day)
  window session_window as (partition by client_info.session_id order by submission_timestamp)
```

Because we are not including page url on click or other non `page_load` events. It would be very helpful for analysis of what happens on a given page to have a page_id metric on all the glean.js pings that is incremented or updated on whenever a new page is loaded.

We can create this in analysis but it makes for more complicated queries, see the following query to build page_ids:
```
select
    *,
    -- Increment the page_id every time we see a page_load per session and ordered by submission time.
    sum(if(event_name = 'page_load', 1, 0)) over (sessison_window) page_id
  from `moz-fx-data-shared-prod.debug_ping_view.events_stream`
  where submission_timestamp >= timestamp_sub(current_timestamp(), interval 3 day)
  window session_window as (partition by client_info.session_id order by submission_timestamp)
```