mozilla-services / mozilla-services/stubattribution
Support `action` as part of attribution data
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
As part of Bug 1970637 we'll be introducing a new action key to attribution information. This allow us to carry user's consent for certain actions (like set default and/or pin to taskbar) from the bedrock download page. We're coordinating with Bedrock to set this key for downloads initiated there if the user opts into one of these actions. The attribution service will need to be able to ensure it ends up in the build.
The current proposed approach is to to pass a third parameter from the marketing page, attribution_action, in addition to attribution_code and attribution_sig. Then we'd convert attribution_action into the action param to be passed along in the modified installer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the service handles attribution_code and attribution_sig and passes data into the modified stub installer. Add support for the proposed attribution_action input and ensure it becomes the installer’s action parameter; verify the existing attribution flow still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100