Open Bug 1907594 Opened 1 year ago Updated 1 year ago

Create an inital set of messaging system targeting constants

Categories

(Firefox :: Messaging System, enhancement, P2)

enhancement
Points:
3

Tracking

()

ASSIGNED

People

(Reporter: mviar, Assigned: mjung)

References

(Blocks 1 open bug)

Details

We often reuse certain targeting strings in messaging system, both for in-tree messages and experiments. At the moment, we don't document these commonly used combinations / heuristics. This makes it difficult to effectively communicate changes and maintain consistency across messages. This bug is for collecting an initial set of targeting constants with the intent of landing them in-tree. Our team discussed using a versioning system to highlight targeting changes. This might look like adding a new constant with _V2 or a similar suffix added to denote an update.

Experimenter offers a model of using constants for commonly reused targeting strings.

This document can be used to compile an initial list of constants.

Example candidates for targeting constants:

  • 'browser.shell.checkDefaultBrowser'|preferenceValue && !isDefaultBrowser" for user needs to set default (see uses here)
  • (currentDate|date - profileAgeCreated|date) / 86400000 >= 28 && previousSessionEnd for existing users
    • We recently began adding previousSessionEnd to this targeting to avoid including users with older profiles who deleted Firefox, then reinstalled and refreshed their account resulting in them seeing first run onboarding
  • totalBookmarksCount <= 5 as a heuristic for users who have not imported from another browser
    • This also needs to be updated as the default number of bookmarks in release will be 4 with bug 1904630.
    • We could now use something like !( browser.migrate.interactions.bookmarks || browser.migrate.interactions.passwords || browser.migrate.interactions.csvpasswords || browser.migrate.interactions.history)
Assignee: nobody → nsauermann
Blocks: fxms-infra
Status: NEW → ASSIGNED
Points: --- → 3
Priority: -- → P1

Putting as a P2 for now until I wrap up some feature work for upcoming experiment.

Priority: P1 → P2
Severity: -- → S4
Iteration: --- → 132.2 - Sep 16 - Sep 27
Priority: P2 → P1
Iteration: 132.2 - Sep 16 - Sep 27 → 133.1 - Sep 30 - Oct 11
Iteration: 133.1 - Sep 30 - Oct 11 → 133.2 - Oct 14 - Oct 25
Iteration: 133.2 - Oct 14 - Oct 25 → 134.1 - Oct 28 - Nov 8
Iteration: 134.1 - Oct 28 - Nov 8 → 134.2 - Nov 11 - Nov 22
Iteration: 134.2 - Nov 11 - Nov 22 → 135.1 - Nov 25 - Dec 6
Iteration: 135.1 - Nov 25 - Dec 6 → 135.2 - Dec 9 - Dec 20

Setting this as a P2 for now in favor of higher priority rootCa desktop and android messaging.

Iteration: 135.2 - Dec 9 - Dec 20 → ---
Priority: P1 → P2

Sorry this unfortunately fell off my plate, hoping to re-prioritize soon.

You need to log in before you can comment on or make changes to this bug.