Closed Bug 1910870 Opened 7 months ago Closed 6 months ago

Microsurvey Sync - Add the feature trigger based on time - behavioural targeting

Categories

(Fenix :: Experimentation and Telemetry, task, P3)

All
Android
task

Tracking

(firefox132 fixed)

RESOLVED FIXED
132 Branch
Tracking Status
firefox132 --- fixed

People

(Reporter: towhite, Assigned: vdreghici)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid][group2])

Attachments

(1 file)

Add behavioural targeting trigger for:

  • User has been signed into sync for 7+ days

With trigger-if-all & exclude-if-any we can have an event to flag that the user has signed in in the last 7 AND hasn't signed out in the last 7 days. These events are SyncAuth.signIn & SyncAuth.signOut

Assignee: nobody → Vlad.DreghiciPopa
Status: NEW → ASSIGNED

Upon trying to add the triggers I noticed that there is a difference in Sync events recorded in Nimbus. Even though signing in with an email or scanning the QR code from another device lead to the same result (the user being synced), the actual events are not the same. This can be seen here. Because of this, there is no way to figure out for how long a user has been signed in if they paired with a QR Code.

Because of this, we have decided that the best approach is to just target users that are currently signed in, without keeping track of when or for how long they have been synced.

So the behavioral targeting for the MVP for the Sync Microsurvey are the following:

  • User currently signed in to Sync.
  • User has at least 2 devices connected.

We have decided to also conduct a Spike to decide on adding more Nimbus events to track Sync events, so we can make use of them in the future.

Summary: Microsurvey Sync - Add the feature trigger - behavioural targeting → Microsurvey Sync - Add the feature trigger based on time - behavioural targeting
Pushed by vlad.dreghici@gmail.com: https://hg.mozilla.org/integration/autoland/rev/d049eb5ee270 Add behavioral targeting trigger for signed in FXA r=android-reviewers,twhite,gmalekpour,amejiamarmol
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: