Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Non-referral downloads should use generic refcode - iOS #1022

Closed
anthonypkeane opened this issue Apr 1, 2019 · 7 comments
Closed

Non-referral downloads should use generic refcode - iOS #1022

anthonypkeane opened this issue Apr 1, 2019 · 7 comments
Labels
enhancement QA/No release-notes/exclude won't have Requirement which the project team has agreed it will not deliver

Comments

@anthonypkeane
Copy link

Description

All Brave browsers should add a universal "default" Brave refcode into the user profile at first run time (if not already present from a referral download/installation process) and act from that moment forward exactly as any referred download would act.

Desktop Link: brave/brave-browser#2547

@jhreis
Copy link
Contributor

jhreis commented Aug 8, 2019

What is the ref code desired here, is it hardcoded?

@srirambv
Copy link
Contributor

srirambv commented Aug 8, 2019

Desktop currently uses BRV001 for non-referral downloads.

cc: @bbondy

@mandar-brave
Copy link

@aekeus please comment
are we tracking iOS organic differently than rest; we should.

@aekeus
Copy link
Member

aekeus commented Aug 8, 2019

iOS is reporting generic referral installs to the 'none' ref code from what I can see on stats.

@jhreis jhreis added enhancement blocked: needs info Needs further information before work can commence QA/Yes release-notes/exclude labels Aug 9, 2019
@jhreis
Copy link
Contributor

jhreis commented Aug 9, 2019

@mandar-brave is this desired? If not, please advise.

@mandar-brave
Copy link

Yes @jhreis - we track organics and since platforms are already filtered, none makes sense!

@jhreis jhreis added QA/No and removed QA/Yes blocked: needs info Needs further information before work can commence labels Aug 9, 2019
@jhreis
Copy link
Contributor

jhreis commented Aug 9, 2019

Sounds, closing then as behavior is already correct. Thanks for clarification 😄

@jhreis jhreis closed this as completed Aug 9, 2019
@iccub iccub added the won't have Requirement which the project team has agreed it will not deliver label Aug 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement QA/No release-notes/exclude won't have Requirement which the project team has agreed it will not deliver
Projects
None yet
Development

No branches or pull requests

6 participants