1158021 - FxA/JourneyBuilder integration

Status: RESOLVED FIXED

(Cloud Services :: Server: Firefox Accounts, defect)

Description

[Ryan Kelly [:rfkelly]]

This is a new meta-bug to try to get the whole story straight on how we'll proceed with FxA/JourneyBuilder integration aka "Project FUEL".  It is similar to, but IIUC broader in scope than, the FxA/Basket integration in Bug 1041074.

The high-level desired outcome is that:

1) We can reliably link accounts in FxA to entries in the Basket db, and hence to ExactTarget/JourneyBuilder.
2) We can solicit engagement email opt-in during the FxA signup process, and allow users to manage subscriptions from the FxA settings page.
3) We can notify JourneyBuilder of user activity events that might trigger journey-related emails.


Support for (1) is more-or-less working as of now, although we've got broad plans to rework it to be simpler and more reliable per Bug 1109809.  Short-term I think we can leave the existing implementation in place and prioritize the other work below.

To support (2) we need to make the Basket API accept OAuth tokens for authentication, as in Bug 1051808.  When that's in place we can have the FxA signup process solicit newsletter opt-in as in Bug 1140528, and can offer UI for modifying subscriptions (bug to be filed).

To support (3) we need a way of getting at interesting user activity events and shuffling them over to ExactTarget.  The notification server noted in Bug 1109809 will support some of this, but it's not designed to handle the kind of private internal tracking-level events we're interested in here, such as "user X made a hello call".

However, we are spinning up a new metrics project for FxA, the "account activity ping", which will support a variety of internal metrics and executive dashboards.  This system *is* designed to handle tracking-level data of the sort required for JourneyBuilder.  So it may make sense for us to tap into that stream and send the relevent events over to JourneyBuilder as they happen.

Short-term, we may implement an ad-hoc API for just the initial events of interest while we wait for account activity ping to come together.  For example, having the relevant servers POST an activity blob to an API in basket, which will forward it to ExactTarget.

That's a brief summary of where my head's at.  Let's fill in more details here a
s various meetings proceed over the next week.

Ben, have I missed anything above?  ISTM that (1) and (2) are known and underway, but we really need to figure out the technical details of (3).

Comment 1

[Ryan Kelly [:rfkelly]]

See also: https://github.com/mozilla/fxa-content-server/issues/2443

Comment 2

[Ben Niolet]

Our next iteration in this project is to help Sync users understand the full value of the service by encouraging them to sign in on more than one device. This can be two desktops, a desktop or mobile or some other combination.

Comment 3

[Ryan Kelly [:rfkelly]]

We shipped the integration and it was awesome.  I don't think there's anything left for us to cover in this bug.