Investigate referral code being added from the playstore install

[porteron]

Description

Historically we've accepted that referral codes do not get captured from our google paid digital advertising into our internal analytics system. More specifically we are missing out on referral data from the Google Playstore install, we'd like to investigate the reason for this because it looks like we have the proper code in place getInstallReferrer() to extract this data.

A couple places to leading thoughts:

• Is the referral code captured and added to the usage ping before the user sends their first usage ping?
• Is there any other information in the getInstallReferrer response that we can use? (campaign name, id, ref url)?
• We are calling getInstallReferrer()docs. Is this being called at the correct time and added to the users local-state so that it is included in the usage ping? And does it persist for 90 days?
• Is referral link being passed through to install and do we have a valid refcodes in campaign setups, format XXX123? ?

cc @anthonypkeane @laurentiugruia

Issue reproduces how often

• Seems to be almost all the time

Version/Channel Information:

• Can you reproduce this issue with the current Play Store version? Yes
• Can you reproduce this issue with the current Play Store Beta version? Yes
• Can you reproduce this issue with the current Play Store Nightly version? Yes

Device details

• All android core it seems