Extension updates: opening a new tab when update gets installed

[marniepw]

For extension (Chrome and Firefox) updates only Timer for when the user is idle Take focus to the new page; decision needed on URL and whether UTM code is needed

[marniepw]

Thursday: nearly ready to push out for review. Push into hidden state.

[aaga]

I'm proposing we send users to rally.mozilla.org/pixel-psa

This is where the infographic will live, and once we submit extension for review this can't be changed. Note that this is just the URL/slug we are talking about, ie low visibility to end users.

@compzilla please advise what the UTM codes should be. The codes will also be locked in once we submit for review.

[rhelmer]

@compzilla please advise what the UTM codes should be. The codes will also be locked in once we submit for review.

I think the options here are to send some/all of the attribution codes (if any) stored in the extension based on how it was installed, or to set new ones.

[jepstein]

What are we trying to test and how might we measure it?

I think we're testing the behavior of someone who receives the new tab, so in that way, I think of this like its own campaign. Which leads me to think we want a new set of UTM codes in this case. If others agree, let's use the UTM generator to create.

[aaga]

@jepstein that's what I was thinking as well

[compzilla]

rally.mozilla.org/pixel-psa/?utm_medium=blog&utm_source=traffic&utm_campaign=extension-open-tab-20221027

[compzilla]

Do we want a different UTM for both Mozilla and Chrome?

[marniepw]

Decision ^ was no. From @rhelmer "Yeah GA has the browser and OS/platform info already, there probably isn't a need to differentiate that w/ our own utm codes too"

[marniepw]

Chrome has been approved, but is in hidden state. Still waiting on AMO.

[aaga]

AMO: https://mozilla.slack.com/archives/C4C0HCX6F/p1666989934094679 JIra ticket for AMO review

[aaga]

Chrome is live