"getting into", not "being into" On Oct 23, 2015 11:23 PM, [email protected] wrote:
> This is being into the range of things that are much better discussed on a > legal bug than in an email chain. Please open a legal bug and take the > discussion there. > On Oct 23, 2015 9:31 PM, "Alex Davis" <[email protected]> wrote: > >> Hi Stefan, >> >> I'll plan a call for Monday so we can re-discuss and clarify all of this >> since there seems to be a misunderstanding despite all of our discussions. >> Perhaps confusion is on my end around a difference between iOS vs Android. >> Many discussions have taken place but I'm sure we'll sort it all out. >> >> In order to address some of the points mentioned by you and Ben, I'll >> just take a second to answer so nobody has to wait until then: >> >> (related to your #2) I had understood that we were doing that in addition >> to Adjust and that we were aligning iOS and Android on same practices. >> >> As per opt-in vs opt-out: >> This type of tracking is similar to the type of opt-out that is now >> standard in Unified Telemetry. This is how we measure retention with FHR >> currently and unified telemetry in the upcoming iOS. As a reminder, >> although Adjust is a 3rd party, we specifically pay for their service due >> to the control we have on the data and the policies that were agreed to. >> This would be a very different story had we been using a free service. >> >> Why wouldn't Unified Telemetry allow us to do this if we pass the >> referring source from Adjust? Although there will be benefits to having it >> in Unified Telemetry, unfortunately it is still far from real-time data and >> when spending millions of $ per campaign, we can't afford to wait 4-6 weeks >> to see the performance of our ad spend. We need to make decisions in >> real-time or we can easily blow away a lot of money. >> >> Why do we need to ping every time the app opens and we don't just rely on >> install numbers? We know for a fact that not all installs are equal. If we >> only optimize for installs, we may ignore that cheaper installs via 45-65 >> year olds actually have a really bad churn rate, and that despite being >> more expensive per install, 18-25 years retain much better. In the end, we >> don't want to optimize ads to drive installs, we want to optimize our >> spending around acquiring more Firefox users. >> >> >> In any case, I'll send of the invite immediately so we can get to the >> bottom of this. >> Have a good weekend everyone, >> >> >> -- >> Alex Davis >> Growth Team | Mountain View >> (415) 769-9247 >> IRC: adavis >> >> On Fri, Oct 23, 2015 at 5:52 PM, Stefan Arentz <[email protected]> >> wrote: >> >>> >>> >>> On Fri, Oct 23, 2015 at 7:50 PM, Ben Bucksch <[email protected]> >>> wrote: >>> >>>> Alex Davis wrote on 24.10.2015 00:26: >>>> >>>>> rather than sending only one ping to Adjust after install to optimize >>>>> our initiatives around installs, we will be sending a ping each time our >>>>> app is opened. >>>>> >>>> >>>> This makes it a completely different quality. It's no longer counting >>>> installs, it's a "phone home" feature. This *must* be opt-in (not opt-out). >>>> >>> >>> I too am surprised by this and from an engineering perspective we have >>> actually been working towards a different plan of implementation. >>> >>> I'm speaking from an Firefox for iOS perspective here, but it is my >>> understanding that this is something we also intend to do for Android: >>> >>> 1. We keep Adjust to track attribution - where did the download come >>> from. We send one ping after install back to Adjust. This is currently >>> implemented on iOS and if I understand correctly, also on Android. >>> >>> 2. We do not use Adjust for tracking retention and usage; instead that >>> will be done through Unified Telemetry. >>> >>> We have a good set of rules for Telemetry. What data can we send back to >>> Mozilla without Opt-In and what data specifically needs Opt-In permission >>> from the user. It was my understanding that continuous usage tracking would >>> be part of the opt-in data set. >>> >>> I feel very uncomfortable about sending continuous pings to a >>> third-party service. Even if we have vetted that service. >>> >>> S. >>> >>> >> >> _______________________________________________ >> mobile-firefox-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/mobile-firefox-dev >> >>
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
