Design a Product Attribution Mechanism for Glean
Categories
(Data Platform and Tools :: Glean: SDK, task, P1)
Tracking
(Not tracked)
People
(Reporter: chutten, Assigned: chutten)
References
Details
One slice of the cross-product data pie that Glean as-yet does not satisfy is attribution: where did this install or acquired user come from? Do we know?
A related problem is distribution: did this install or user come to us via a partner relationship?
This bug is about designing a mechanism that can supply consistent yet flexible cross-product attribution and distribution recording and reporting in Glean.
|
Assignee | |
Comment 1•3 months ago
|
||
Initial Draft: https://docs.google.com/document/d/1TIZhpBeZcJSEnIZJwj0Cj9saL2Tfs0X6oi_4gFU35eM/edit?tab=t.0
For the first round of feedback I'm tapping Travis and Jan-Erik to both provide input on whether the proposal makes sense (grammatically, structurally, etc.) and is complete. Travis-specific input I'm looking for is API and pattern design for the Glean SDK. Jan-Erik-specific input I'm looking for is end-to-end matters like schemas and ingestion and tooling.
But of course consider the whole doc to be in-bounds for any critique large or small.
|
||
Comment 2•3 months ago
|
||
No additional comments from me on the doc to add to what Jan-Erik already pointed out. I think there will be some edge cases and places where we need to iterate, but overall this lays a good foundation for adding attribution info to most pings that need it.
|
||
Comment 3•3 months ago
|
||
Left comments and discussed it further with :chutten.
Removing the ni? until we get to round 2 of the review!
|
||
Comment 4•2 months ago
|
||
Since you submitted the proposal to the service review group: The proposal looks solid to me and I don't see any major concerns from the platform side of things. I guess some probe-scraper work and making some changes to the view generation to have ext under the client_info section (if that is desired) will be needed.
|
|
Assignee | |
Comment 5•2 months ago
|
||
Proposal's now accepted! We can start thinking about implementation now.
Description
•