[Web Install] Can this information be provided via the install_url?

[dmurph]

This is definitely less robust, but could this attribution information be stored from the install url if this api shape is followed:
https://bit.ly/web-install-api-shape-install-url

https://teams.microsoft.com/app/lightweightinstallurl?utm=campaignid&....

[HowardWolosky]

While this is related to the information that Acquisition info would report, this is ultimately a question of how this information is captured during Web Install. As such, changing the title to make that a bit more clear.

[kyerebo]

This seems like a question regarding the browser install/Web Install portion of the API! I agree that while this option would be less robust, there is even a certain advantage in it considering that having the acquisition information be a part of the install URL means that parties can even access campaign ID through their web server logs, which they could then corroborate with referral information retrieval.

However, I do think that keeping the referral information as its own property makes for a clearer division of what information needs to be captured for acquisition. If we were to add more parameters other than campaign ID to the install URL, it might start becoming unclear which parameters are related to acquisition.
Additionally, websites that do not need to specify a separate install URL for their PWA wouldn't have one, so it seems like an awkward use case if a website adds an install URL only for the purpose of specifying acquisition.

I'd love to see what thoughts @diekus has about it as well.

[diekus]

+1 to what @kyerebo states. I think acquisition info scales better. Using install_url would certainly allow to track campaign id and it can't hurt if it is used like this by some developers, but future-proofing in case more information needs to be added passing this information as a parameter seems best.