mad and jeffreyc: I see that the download URL used by the outdated upgrade bubble uses a very specific brand and UTM query params. If we were to add support for canary Chrome to direct users to the canary dlpage, should we use those same query params or others?

I was given those params by Jeff. I remember we argued about this, but I don't remember the the details. laforge@ might remember, I think he was part of the discussions.

Chrome Canary (technically Chrome SxS) is a different product (id) than Chrome.

Yes. This is why Gab thinks it'd be a good idea for the outdated bubble for SxS installs to take users to the canary dlpage rather than the normal dlpage. The specific URL used for out-of-date Chrome has these params:

brand=CHWL
utm_campaign=en
utm_source=en-et-na-us-chrome-bubble
utm_medium=et

I have no idea what these do. If we were to take SxS users to https://www.google.com/chrome/browser/canary.html, should we use the same query params there?

Yes, sorry didn't grok the issue initially.  

That would make sense (i.e. Canary user to Canary download page, Chrome user to Chrome - Stable download page).

Do you know why normal Chrome uses CHWL and these various utm_ params? Does the canary dlpage support them, too? Should we use the same params for the canary URL? Thanks.

CHWL was the brand code that we used to track the success of these refreshes, it should be fine to reuse for canary (i.e. it's for the sake of logistics and not technical).  The url pattern, I believe came from marketing.

The other params, neither the e-mail (forwarded) nor the spec (https://docs.google.com/document/d/1Wkxc2VIvmkN82er-hSL9IDE0Belq0SiNpOpfiKDpJ3s/edit) explain their utility, but I'm guessing that one of the marketing folks will know (rpop should be able to help there).

Do we want all Chrome (Dev/Beta/Stable) to go to Stable DL page? I guess that makes sense as the channel may also be an issue (e.g. corrupted fake dev or something)?

At least it's an over-install (and since it's 12 weeks, Stable should be a more recent version than even an outdated Dev) so it's always okay to install Stable -- whereas installing Stable to fix Canary doesn't work.

Yup, that was precisely the historic logic :).