Create a Fenix Leanplum Attribute that tells us the app is Fenix

[st3fan]

Why/User Benefit/User Problem

Because of the application migration, the application could be Fennec or Fenix. This is a request to add a simple Fenix attribute to Leanplum that will tell us that the app is Fenix.

What/Requirements

A leanplum attribute Fenix that is always set to true.

Acceptance Criteria (how do I know when I’m done?)

┆Issue is synchronized with this Jira Task

[cbonacuse]

For additional context, adding the attribute will allow us in Leanplum to create an "event" which we can then track as a "conversion event" for a campaign. i.e. when we roll out Fenix to the Android release app, we will want to know how many users we were able to convert to the Fenix version of the app and we cannot do this by simply filtering on app version.

By having the attribute of 'Fenix' set to 'true', we will set up a Leanplum event (i.e. E_Updated_To_Fenix) that will be triggered in a users profile and we can track conversions in a campaign.

[lwa-moz]

@st3fan after speaking with @cbonacuse, it sounds like the Marketing team will also need a Leanplum event that corresponds to a user updating from Fennec to Fenix.

"Events" are used by the Marketing team as a means of determining campaign success. In this instance, that they have successfully encouraged a user to update to Fenix.

Additionally, events can be used to trigger additional campaigns, for instance an onboarding message sent to users after they update to Fenix.

Unfortunately, attributes cannot be used in this way. We will therefore need to create an event that fires when a user updates from Fennec to Fenix. Perhaps this event could be instrumented at the conclusion of the data migration flow?

[AndiAJ]

Hi, verified as fixed.

✔️ Fenix Nightly - Fenix Leanplum Attribute set to TRUE (Device ID 5152fa49-fbd5-43ac-8f45-9c7cecf4bf9a )

✔️ Fenix Beta v4.0.0-beta.1 - Fenix Leanplum Attribute set to TRUE (Device ID 39ec97f9-7cbd-43eb-9466-0956119cefb7 )

✔️Performed manually a migration from Fennec to Fenix and the E_Fennec_To_Fenix_Migrated event was successfully created. (Device ID ca28e3cc-82c2-49c3-bad5-5a81b62a7e15)

Please note that this event was generated in the Firefox Nightly section of Leanplum.

[cbonacuse]

Hello! I know this is now closed, but after looking in Leanplum at the Nightly users, it appears that the fenix attribute did not get applied retroactively to users who were updated to Fenix prior to the attribute being created. Was this expected?

According to this dashboard, the earliest version of Nightly (with the date/timestamp versioning) that shows fenix (or Fenix) is TRUE is 2/14.

[ValentinTimisica]

Yes, this is expected. We added a new attribute in code which only produces effects for the future.