Bugzilla

(In reply to Abhishek from comment #10)
> Hey :agibson. Thanks a lot for providing perspective here.
> 
> The [current state of click events](https://github.com/mozilla/bedrock/blob/0eb294b0efb12d0b08901ab3b35475c6f1d47ed9/glean/metrics.yaml#L195-L207) in bedrock (as per the document I shared) gave me an impression that there is no need for capturing urls as part of the event context. May be I missed something there? or is it something that is intended to be done for bedrock in future?

Bedrock also sends additional, page level metrics such as `path` and `referrer` in its click events (see other metrics that are [sent in events pings](https://github.com/mozilla/bedrock/blob/0eb294b0efb12d0b08901ab3b35475c6f1d47ed9/glean/metrics.yaml#L25)). This is useful information for answering questions like "How many downloads did landing page X generate?" or "How many downloads were a result of organic search referrals?".

I'm very interested in the work proposed here, as I'd be keen to switch to using these more standardized click events instead of our own implementation. But I'd say being able to know both the `url` (or at least `pathname`) and also the `referrer` of the session where the click occurred, is a pretty standard ask for most marketing/campaign reporting needs.

(In reply to Abhishek from comment #10)
> Hey :agibson. Thanks a lot for providing perspective here.
> 
> The [current state of click events](https://github.com/mozilla/bedrock/blob/0eb294b0efb12d0b08901ab3b35475c6f1d47ed9/glean/metrics.yaml#L195-L207) in bedrock (as per the document I shared) gave me an impression that there is no need for capturing urls as part of the event context. May be I missed something there? or is it something that is intended to be done for bedrock in future?

Bedrock also sends additional, page level metrics such as `path` and `referrer` in its click events (see other metrics that are [sent in events pings](https://github.com/mozilla/bedrock/blob/0eb294b0efb12d0b08901ab3b35475c6f1d47ed9/glean/metrics.yaml#L25)). This is useful information for answering questions like "How many downloads did landing page X generate?" or "How many downloads were a result of organic search referrals?".

I'm very interested in the work proposed here, as I'd be keen to switch to using these more standardized click events instead of our own implementation. But I'd say being able to know both the `url` and also the `referrer` of the session where the click occurred, is a pretty standard ask for most marketing/campaign reporting needs.