Bugzilla

### Top Sites
Volumetric agreement of ping volumes and `context_id` volumes across the ping types is very close:
* [topsites-impression](https://sql.telemetry.mozilla.org/queries/93623/source#231615) - oddly, the PingCentre-sent `context_id` volumes for impressions are very slightly higher than Glean-sent. We'll look into this more in identifier coverage.
* [topsites-click](https://sql.telemetry.mozilla.org/queries/93624/source#231617)

We checked `context_id` and `tile_id` identifier coverage on both ping types.
* ["topsites-impression"-`ping-type` `context_id`s](https://sql.telemetry.mozilla.org/queries/93486/source) - Glean hears from 0.69% that PingCentre doesn't. PingCentre hears from 1.03% that Glean does not. Net 0.34% higher distinct `context_id` volume from PingCentre.
* ["topsites-click"-`ping_type` `context_id`s](https://sql.telemetry.mozilla.org/queries/93626/source) - Glean hears from 3.2% that PingCentre doesn't. PingCentre hears from 0.48% that Glean does not.
* ["topsites-impression"-`ping-type` `tile_id`s](https://sql.telemetry.mozilla.org/queries/93628/source) - There are too few to really say much about, but there's nothing alarming in this preliminary look.
* ["topsites-click"-`ping_type` `context_id`s]https://sql.telemetry.mozilla.org/queries/93627/source) - There are too few to really say much about, but there's nothing alarming in this preliminary look.

I'm confused by PingCentre being able to deliver more impressions from more contexts (but fewer pings). A hypothesis we wouldn't be able to test in the data is that this is coming from ultrashort sessions (ie, the same thing driving bug 1837230). If so, the landing of the new Glean release followed by the fix in bug 1837230 ought to pull it more in line. **This is something that'll need to be resolved before we can sign off**, to my mind.

Also, I noticed that the `quick_suggest.reporting_url` is included in the "top-sites" ping and not the "quick-suggest" ping. I'll file a bug to get that taken care of pronto.

### Top Sites
Volumetric agreement of ping volumes and `context_id` volumes across the ping types is very close:
* [topsites-impression](https://sql.telemetry.mozilla.org/queries/93623/source#231615) - oddly, the PingCentre-sent `context_id` volumes for impressions are very slightly higher than Glean-sent. We'll look into this more in identifier coverage.
* [topsites-click](https://sql.telemetry.mozilla.org/queries/93624/source#231617)

We checked `context_id` and `tile_id` identifier coverage on both ping types.
* ["topsites-impression"-`ping-type` `context_id`s](https://sql.telemetry.mozilla.org/queries/93486/source) - Glean hears from 0.69% that PingCentre doesn't. PingCentre hears from 1.03% that Glean does not. Net 0.34% higher distinct `context_id` volume from PingCentre.
* ["topsites-click"-`ping_type` `context_id`s](https://sql.telemetry.mozilla.org/queries/93626/source) - Glean hears from 3.2% that PingCentre doesn't. PingCentre hears from 0.48% that Glean does not.
* ["topsites-impression"-`ping-type` `tile_id`s](https://sql.telemetry.mozilla.org/queries/93628/source) - There are too few to really say much about, but there's nothing alarming in this preliminary look.
* ["topsites-click"-`ping_type` `context_id`s](https://sql.telemetry.mozilla.org/queries/93627/source) - There are too few to really say much about, but there's nothing alarming in this preliminary look.

I'm confused by PingCentre being able to deliver more impressions from more contexts (but fewer pings). A hypothesis we wouldn't be able to test in the data is that this is coming from ultrashort sessions (ie, the same thing driving bug 1837230). If so, the landing of the new Glean release followed by the fix in bug 1837230 ought to pull it more in line. **This is something that'll need to be resolved before we can sign off**, to my mind.

Also, I noticed that the `quick_suggest.reporting_url` is included in the "top-sites" ping and not the "quick-suggest" ping. I'll file a bug to get that taken care of pronto.