1830401 - Add Adjust Conversion event for "activated"

Status: RESOLVED FIXED

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

Description

[Frank Bertsch [:frank]]

The Growth Program would like to use "activated" as a conversion event for our marketing campaigns. The rationale is that it is the measurement we use to determine success of a campaign, and we believe that targeting it directly may give Google Ads better signal in determining who to market to.

The definition for activation is described in this document: https://docs.google.com/document/d/1ab2bRcmOdkxgLu-Xin7fZ25qFZGY5IyyMEkVCB1jSoQ/edit#

But the tl;dr is that a user is activated if they have at least one search on days 4-7 and at least two days of use on days 2-7.

Comment 1

[Joe M [:jmahon]]

Estimate from the Android team:

• Appx 5 days to implement & test
• 3 (out of 10) complexity (so, the ‘accuracy’ of that 5-day estimate is fairly high - it’s unlikely that unexpected implementation hurdles may be encountered)
• 2 (out of 10) risk (so, there’s a low likelihood of anything unexpected happening after releasing - the problem is well-enough understood to be confident that we can ship the right thing)

---

And just capturing some additional ideas from :royang for bookeeping:

I was thinking something similar to re-enagement notification could work here. We set a workmanager task for 7 days after user first starts Fenix. When 7 days is up we can check shared preference for lastBrowseActivity and lastSearchActivity (doesn't exists yet) and see if the user matches the requirement as "Activated". If so then we send the event to Adjust.
This does means that we'll have to wait till day 7 to make that decision. Another way is we check every time the user does a search to see if we should set it but in that implementation we will need to short circuit it if the user is already activated or 7 days has passed. (more complicated but faster result)

Comment 2

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1830401 - add Adjust event for Activated Users (#2165)

Comment 3

[[:harrisono]]

PR is up now with tests.

Comment 4

[BMO Github Automation]

Authored by https://github.com/HarrisonOg
https://github.com/mozilla-mobile/firefox-android/commit/5d7097a5950e37e54fd2d6328cfc52bd737e18b0
[main] Bug 1830401 - add Adjust event for Activated Users

Comment 5

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1830401 - add Adjust event for Activated Users (backport #2165) (#2289)

Comment 6

[[:harrisono]]

Created uplift backport PR.

Comment 7

[[:harrisono]]

Comment on attachment 9336779 [details] [review]
[mozilla-mobile/firefox-android] Bug 1830401 - add Adjust event for Activated Users (backport #2165) (#2289)

Beta/Release Uplift Approval Request

• User impact if declined: Adjust "Activated" Event will not be in v114 and growth marketing will not receive that data.
• Is this code covered by automated tests?: Yes
• Has the fix been verified in Nightly?: No
• Needs manual test from QE?: No
• If yes, steps to reproduce:
• List of other uplifts needed: None
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky): Low risk telemetry addition.
• String changes made/needed:
• Is Android affected?: Yes

Comment 8

[Ryan VanderMeulen [:RyanVM]]

Comment on attachment 9336779 [details] [review]
[mozilla-mobile/firefox-android] Bug 1830401 - add Adjust event for Activated Users (backport #2165) (#2289)

v114 is in RC now, so moving this approval request over to release instead.

Comment 9

[BMO Github Automation]

Authored by https://github.com/HarrisonOg
https://github.com/mozilla-mobile/firefox-android/commit/18bfbdb8f078b504ab6a48ad16419ee6301f8a39
[releases_v114] Bug 1830401 - add Adjust event for Activated Users

Comment 10

[Pascal Chevrel:pascalc]

Comment on attachment 9336779 [details] [review]
[mozilla-mobile/firefox-android] Bug 1830401 - add Adjust event for Activated Users (backport #2165) (#2289)

Approved for RC3