Closed Bug 1501037 Opened 6 years ago Closed 5 years ago

[Growth] Attribution Field Documentation

Categories

(Data Science :: Documentation, task)

x86_64
macOS
task
Not set
normal
Points:
2

Tracking

(data-science-status On-hold)

RESOLVED INACTIVE
Tracking Status
data-science-status --- On-hold

People

(Reporter: shong, Unassigned)

Details

Brief description of the request: Document exactly what attribution means, how it gets filled, and what we should expect in Telemetry Link to any assets: Is there a specific data scientist you would like or someone who has helped to triage this request: assigned to shong by shong
current work here: https://github.com/SuYoungHong/firefox-acquisition/blob/master/docs-attribution.md need to get review from subject matter experts and figure out best place to publish
Status: NEW → ASSIGNED
Blocks: 1518925
data-science-status: --- → On-hold
Points: --- → 1
Points: 1 → 2
Summary: Document How Attribution Works → [Growth] Attribution Field Documentation

Summary:

Write documentation in DTMO (specifically in DTMO!) explaining how the Attribution field works. This documentation should have:

  • Overview of pipeline from GA to telemetry
  • Logic in GA on what info gets passed
    • Direct nav
    • Referral sources
    • Whitelist
    • (any changes to logic from the past)
    • Rough explanation of what ISN'T covered (i.e. 3rd party sources? FTP? non-Win OS?)
  • How it gets passed to Telemetry
  • How it works in Telemetry
    • What time / version it is reliable after
    • behavior on paveover
No longer blocks: 1518925

unassigning from myself as I'll be on PTO / leave until Oct 13th.

Going to leave this open if anyone wants to pick it up, otherwise I'll re-assign to myself when I'm back / have bandwidth.

Assignee: shong → nobody
Status: ASSIGNED → NEW

Work for the DS team is now tracked in Jira. You can search with the Data Science Jira project for the corresponding ticket.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.