Closed Bug 1843610 Opened 2 years ago Closed 2 years ago

Add telemetry for deferred deep link test

Categories

(Firefox for Android :: Experimentation and Telemetry, enhancement)

All
Android
enhancement

Tracking

()

RESOLVED FIXED
117 Branch
Tracking Status
firefox116 --- fixed
firefox117 --- fixed

People

(Reporter: royang, Assigned: royang)

References

Details

(Whiteboard: [fxdroid])

Attachments

(4 files)

Add telemetry to measure if user receives our test deferred deep link from Google App Campaigns. This telemetry will also measure the timing of when we receive the test deferred deep link.

Assignee: nobody → royang
Whiteboard: [fxdroid]
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch

To test on nightly, enter this in command line " adb shell am start -d fenix-dev://test_deferred_deep_link". This should trigger the telemetry.

Hello,
We would need extra steps to reproduce, and what's the expected result. Currently, the app is opened but there is no behaviour on the telemetry itself, the pings are not sent to the glean dashboard.
Are we looking after a "deferred_deeplink_time" metric?
A command that would also send the metric to glean dashboard would be very helpful.
Thank you

Flags: needinfo?(royang)

Sorry :amocirean, I should have been more clear. On Nightly the command should be "adb shell am start -d fenix-nightly://test_deferred_deep_link". Depends on which branch you're testing on, you'll have to use the deep link scheme of that version.

I don't think this needs to be QA'd since the code added is to test deferred deep link on Nightly. I'll remove the QA-verify+ tag. Thanks

Flags: needinfo?(royang)
Flags: qe-verify+

Comment on attachment 9343945 [details] [review]
[mozilla-mobile/firefox-android] Bug 1843610 - Add telemetry for deferred deep link test (#2851)

Beta/Release Uplift Approval Request

  • User impact if declined: Can't confirm if deferred deep link works and will not have the timing needed for attribution based onboarding.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • 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): This adds a new deep link that when it is triggered will send a telemetry. No behaviour changes and the user will not see anything on UX.
  • String changes made/needed: N/A
  • Is Android affected?: Yes
Attachment #9343945 - Flags: approval-mozilla-beta?

The backport has conflicts that need to be resolved

Flags: needinfo?(royang)
Comment on attachment 9344891 [details] [review] [mozilla-mobile/firefox-android] Bug 1843610 - Add telemetry for deferred deep link test (backport #2851) (#2929) switching flag
Attachment #9344891 - Flags: approval-mozilla-beta?
Attachment #9343945 - Flags: approval-mozilla-beta?

Resolved conflict manually. Thanks

Flags: needinfo?(royang)
Attachment #9344891 - Flags: approval-mozilla-beta?
Comment on attachment 9344943 [details] [review] [mozilla-mobile/firefox-android] Bug 1843610 - Add telemetry for deferred deep link test (backport #2851) (#2933) Approved for Mobile 116.0b8
Attachment #9344943 - Flags: approval-mozilla-beta+

Since this didn't need manual QA verification for Nightly either, I'll remove the qe-verify+ flag.

Flags: qe-verify+
Regressions: 1846040
Flags: qe-verify+
Target Milestone: 117 Branch → 119 Branch

This revert probably should have landed in a different bug to avoid confusion around the flags.

Flags: needinfo?(royang)
Target Milestone: 119 Branch → 117 Branch

Yes, agreed. Didn't think about the confusion this causes. We'll just let the revert ride the train in v120. I don't think there's a need to uplift.

Flags: needinfo?(royang)
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: