taking myself off since this should be reviewed by a c/b/extensions reviewer
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Rob and I needn't both review this, and he's a UKM expert.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Friendly ping on reviewing this cl @rdevlin...@chromium.org @rka...@chromium.org
Thanks!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
| Code-Review | +1 | 
thanks for the patience here
ukm::SourceId UkmRecorder::GetSourceIdForExtensionUrl(is this in error, this is already exists
    Recorded the extension related action metrics that reflects the extensioncan you expand here exactly how and when this is triggered
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Friendly ping on reviewing this cl @rdevlin...@chromium.org @rka...@chromium.org
Thanks!
Done
ukm::SourceId UkmRecorder::GetSourceIdForExtensionUrl(is this in error, this is already exists
This is needed as the PassKey type is different than the one on line 103.
    Recorded the extension related action metrics that reflects the extensioncan you expand here exactly how and when this is triggered
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Thanks Howard! Implementation lgtm, would like to look at the design doc before approving since it's not clear to me why various actions with different entry points will be wrapped on the same ukm
Following https://chromium-review.googlesource.com/c/chromium/src/+/5731681 to add UKM for tracking extension pin/unpin actionnit: break line
b/451675689Please fix this WARNING reported by No short links in OSS: Do not use b/<number> in OSS code. Prefer crbug.com/<number> instead. While bugs...
Do not use b/<number> in OSS code. Prefer crbug.com/<number> instead. While bugs should be public by default, bugs that must remain internal may use b/<number>, ignoring this warning; see https://www.chromium.org/issue-tracking/googler-guidelines/.
    Recorded the extension related action metrics that reflects the extension
    usage for the Chrome Web Store. Action such as pinning/unpinning extensions,
    enable/disable extensions, initiate context menu (right click) on extensions
    and left click on extension icon from toolbar will be recorded.Is the same UKM going to be used for pin/unpin, enable/disabled, clicks? They are different actions, wouldn't that make the metrics different?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Thanks Howard! Implementation lgtm, would like to look at the design doc before approving since it's not clear to me why various actions with different entry points will be wrapped on the same ukm
Thanks, I don't have a specific design doc but I already shared the approval doc with you.
Following https://chromium-review.googlesource.com/c/chromium/src/+/5731681 to add UKM for tracking extension pin/unpin actionHoward Changnit: break line
Done
Please fix this WARNING reported by No short links in OSS: Do not use b/<number> in OSS code. Prefer crbug.com/<number> instead. While bugs...
Do not use b/<number> in OSS code. Prefer crbug.com/<number> instead. While bugs should be public by default, bugs that must remain internal may use b/<number>, ignoring this warning; see https://www.chromium.org/issue-tracking/googler-guidelines/.
Done
    Recorded the extension related action metrics that reflects the extension
    usage for the Chrome Web Store. Action such as pinning/unpinning extensions,
    enable/disable extensions, initiate context menu (right click) on extensions
    and left click on extension icon from toolbar will be recorded.Is the same UKM going to be used for pin/unpin, enable/disabled, clicks? They are different actions, wouldn't that make the metrics different?
There will be different metric values but all these actions are keyed by the item id so we can have an overall idea on how users interact with a specific extension.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Adding Justin to take a look because I'm gardening today and falling behind on CL reviews :')
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Hi Robert, I think you got removed from reviewer accidentally. Can I get your approval again? Thank you.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
| Code-Review | +1 | 
lgtm enums.xml
Hi Howard! A couple small changes otherwise it's looking good.
  <int value="1" label="Extension UnPinned"/>```suggestion
<int value="1" label="Extension Unpinned"/>
```
  <owner>howa...@google.com</owner>Is there a team group we could add as an owner too?
    Recorded the extension related action metrics that reflects the extension
    usage for the Chrome Web Store. Action such as pinning/unpinning extensions,
    enable/disable extensions, initiate context menu (right click) on extensions
    and left click on extension icon from toolbar will be recorded.nit: perhaps slightly more concise wording? (I don't think clicks will change, but in the future perhaps taps so best to leave that part out)?
```suggestion
Records user actions related to an extension, providing usage metrics for the
Chrome Web Store. Tracked actions include pinning, unpinning, enabling,
disabling, context menu access, and toolbar icon clicks.
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
| Code-Review | +1 | 
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | 
Add pin/unpin ukm for cws```suggestion
Add extension pin/unpin ukm for cws
```
| Commit-Queue | +1 | 
```suggestion
Add extension pin/unpin ukm for cws
```
Done
```suggestion
<int value="1" label="Extension Unpinned"/>
```
Done
Is there a team group we could add as an owner too?
added websto...@google.com as owner
    Recorded the extension related action metrics that reflects the extension
    usage for the Chrome Web Store. Action such as pinning/unpinning extensions,
    enable/disable extensions, initiate context menu (right click) on extensions
    and left click on extension icon from toolbar will be recorded.nit: perhaps slightly more concise wording? (I don't think clicks will change, but in the future perhaps taps so best to leave that part out)?
```suggestion
Records user actions related to an extension, providing usage metrics for the
Chrome Web Store. Tracked actions include pinning, unpinning, enabling,
disabling, context menu access, and toolbar icon clicks.
```
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |