Closed Bug 1316136 Opened 4 years ago Closed 3 months ago
Allow for attribution on the full installer
As a product manager, I want to bring exe full installer new profiles originating from moz.org downloads to the light funnel so I can better understand the share of new profiles that originate from this part of the funnel and optimize adequately. As a product manager, I want to make the process of distributing Firefox through 3rd party partner sites simpler whilst retaining the ability to identify Firefox profiles originating from downloads made through distribution partner websites, so that setting up new distribution partners is less work. Acceptance criteria: - exe full installer attribution (MSI will be another phase) is supported on the full installer through addition of a dummy certificate when signing - A new partner repack mode is added to support attribution - Attribution is automatically added for any full installer download links used on moz.org pages (Bedrock) - should cover https://www.mozilla.org/en-US/firefox/installer-help and https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
There is work going on in bug 1259607 to add attribution to the stub installer. It would also be useful to add attribution to the full installer. Right now when we give builds to other websites to distribute, if we want to track it, we have to give them a custom distribution/partner build. I'd much rather have it work the same way as the stub installer and be able to create a custom build that just has the campaign stored in the full installer.
Very little of the work involved for this would be in the installer; all that's needed from that side is to move the function from the stub installer into shared.nsh and insert a call to it in the full installer. There would be much more work involved in getting full installers with attribution data created in the first place.
Priority: -- → P5
> There would be much more work involved in getting full installers with attribution data created in the first place. Can you provide more info? I thought the stub installers attribution was added dynamically. We can't do that with the full installers?
I think I implied more certainty there than I actually have; sorry about that. I didn't closely follow what was going on with stub attribution on the backend once the client issues were resolved, so I don't know those details. I just wanted to point out that, while there would be very little work involved in the installer/client code to make this happen (assuming the existing telemetry is sufficient for the uses you're thinking about), hooking up all the backend services is probably harder and certainly involves more people (cloud ops and web would have work to do, might need to involve product also).
This is something that is interesting for the China folks as well (and will be part of a new distribution strategy if we get one together) The primary usecase here is being able to pass some sort of distribution ID to a full installer just so when it runs for the first time, it stores that distribution ID internally so it can later be queried (I assume using the same mechanism as the campaign ID). Is this practical at all?
Well, attribution is really intended (and best-suited) for data that isn't available at build time. I don't know anything about the new distribution strategy you mentioned, but if it's structured so that the distribution becomes something that's sort of layered on top of a normal full installer, then attribution would be a good way to get the distribution ID and any other required information into that full installer. We'd have to add a better way to query that information individually within Firefox, because right now it really only supports telemetry, but that would be very simple to do. If the distribution stuff is still baked into the installer as part of the application files, then attribution probably isn't the right method.
I definitely want to move away from baking the distribution stuff in the installer. I picture a world where you download Firefox with a distribution ID passed to the installer and then the distribution is added dynamically.
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/7690541a2c14 Support post-signing/attribution data in full installer. r=mhowell
Flags: needinfo?(nthomas) → needinfo?(hoosteeno)
Flags: needinfo?(hoosteeno) → needinfo?(agibson)
You need to log in before you can comment on or make changes to this bug.