Add new Leanplum Add Ons Installed Attribute

[cbonacuse]

The following attribute was identified as a priority for Fenix during a recent test by the Mobile Engagement team.

• Add Ons Installed

This should include a list of add-ons the user has installed when the user successfully adds an add-on to their browser (by clicking "+" on the screen in the below image).

UNITO-UNDERSCORE!20200616-184806!

Tasks:

• Create attribute: Add Ons Installed
• Understand if it is possible to implement in the requested way of having a list of values vs. boolean
• Undergo data review
• Add test to show it's being fired (e.g. specified by UI tests for existing LeanPlum events #11210 )
• Test end-to-end and validate attribute in Leanplum

This needs to be added to the Mobile Engagement ❤️ Fenix project. I do not have access to add it myself.

┆Issue is synchronized with this Jira Task

[jhugman]

@liuche @chutten @boek

Requesting a data-review on this prior to doing the engineering work on this: this is the ids of the addons installed, logged at/near startup.

@cbonacuse of the mobile engagement team is requesting this.

[jhugman]

@cbonacuse to fill in.

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

1. What questions will you answer with this data?
   To understand which add-ons to message to users for feature discovery to optimize their experience with the app

2. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

• To measure the usage of add-ons and to help direct users to discover add-ons as a feature to enhance their experience within the app.

3. What alternative methods did you consider to answer these questions? Why were they not sufficient?

• N/A

4. Can current instrumentation answer these questions?

• No, while we are tracking some of these metrics in Glean, we need access to them in Leanplum for marketing usage.

5. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the found on the Mozilla wiki.

• Category 2 (add ons)

6. How long will this data be collected?

• This data will be present as long as the user ID exists in Leanplum. LeanPlum does not support expiry dates for probes, but the mobile engagement/marketing automation teams will track this. @cbonacuse is the first contact here.

7. What populations will you measure?

• All release, beta, and nightly users with telemetry enabled.

8. Please provide a general description of how you will analyze this data.

• Leanplum / Amplitude

9. Where do you intend to share the results of your analysis?

• Only on Leanplum, Amplitude and with mobile teams.

[cbonacuse]

@boek just curious, what is the difference between enabled_addons and installed_addons? Are these not the same? I see the definitions are slightly different in the code but I thought if an addon was installed, it is enabled.

I just hit the "+" button for 2 addons and I'm now seeing a value of 2 for both attributes.

cc: @liuche

[andreicristianpetcu]

@cbonacuse you can enable an addon and then disable it. same like on desktop.

[bifleming]

Work is complete