1676437 - Collect browser attribution for onboarding telemetry

Status: VERIFIED FIXED

(Firefox :: Messaging System, enhancement, P1)

Description

[Nan Jiang [:nanj]]

This allows us to use the attribution as a segment to examine the onboarding telemetry.

Comment 1

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla-services/mozilla-pipeline-schemas/pull/641

Comment 2

[Nan Jiang [:nanj]]

Attachment: Bug 1676437 - Collect attribution data for Onboarding r=pdahiya

Comment 3

[Nan Jiang [:nanj]]

Attachment: data_review_attribution.txt

Hey :chutten,

Could you take a look at this, plz?

Thanks!

Comment 4

[Chris H-C :chutten]

Comment on attachment 9188344 [details]
data_review_attribution.txt

PRELIMINARY NOTES:
Traditionally Q1 is about the product questions you'll be answering using this collection. Collecting the attribution data in activity stream is about better identifying activity-stream-instrumented early browser uses that might lead to activation. In future reviews please list the uses you hope to put the data collection to.

DATA COLLECTION REVIEW RESPONSE:

Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes.

Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences.

If the request is for permanent data collection, is there someone who will monitor the data over time?

Yes, Nan Jiang is responsible.

Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, Interaction.

Is the data collection request for default-on or default-off?

Default on for all channels.

Does the instrumentation include the addition of any new identifiers?

No.

Is the data collection covered by the existing Firefox privacy notice?

Yes.

Does there need to be a check-in in the future to determine whether to renew the data?

No. This collection is permanent.

---

Result: datareview+

Comment 5

[Nan Jiang [:nanj]]

Traditionally Q1 is about the product questions you'll be answering using this collection. Collecting the attribution data in activity stream is about better identifying activity-stream-instrumented early browser uses that might lead to activation. In future reviews please list the uses you hope to put the data collection to.

:chutten Gotcha, will do. Thank you!

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/a5578b488bdb
Collect attribution data for Onboarding r=pdahiya

Comment 7

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/mozilla-central/rev/a5578b488bdb8d9158d895a028307681b92eda87

Comment 8

[Robert Martin [:romartin], Ecosystem QA]

Hey @Nan,

I've downloaded the latest Firefox Beta 85.0b4 (Build ID: 20201220193140) stub-installer from mozilla.org using Google Chrome on Windows 10 x64, and I've observed the following attribution telemetry:

• In the "about:telemetry" page:
  • "attribution.campaign" with "%2528not%2Bset%2529" value.
  • "attribution.content" with "%2528no%2Bset%2529" value.
  • "attribution.experiment" with "%2528no%2Bset%2529" value.
  • "attribution.medium" with "%2528direct%2529" value.
  • "attribution.source" with "%2528 other%2529" value.
  • "attribution.ua" with "chrome" value.
  • "attribution.variation" with "%2528not%2Bset%2529" value.
• In the "Browser Console" the "about:welcome" page related pings are displayed with the following:
  • "attribution":{"campaign":"%2528not%2Bset%2529","content":"%2528not%2Bset%2529","experiment":"%2528not%2Bset%2529","medium":"%2528direct%2529","source":"%2528other%2529","ua":"chrome","variation":"%2528not%2Bset%2529"}

I have also verified that the "attribution.*" properties are successfully sent and received using a local Telemetry Server.

@Nan, can you please confirm that these are the expected values for a fresh profile?

Comment 9

[Nan Jiang [:nanj]]

Hey Robert,

Yes, confirm that all those attribution assets are URL encoded (a.k.a Percent-encoding) similar to what we collect for the browser telemetry.

Thanks for verifying this!

Comment 10

[Robert Martin [:romartin], Ecosystem QA]

Hey Nan,

Thank you very much for the confirmation!

I'm marking this issue as verified based on the verifications done and mentioned in comment 8 and the confirmation in comment 9.