Closed Bug 1371816 Opened 7 years ago Closed 6 years ago

about:addons newsletter - signup form integration

Categories

(Marketing :: Email, task)

Product:
Marketing
Component:
Email
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jdavis, Assigned: jorgev)

References

Details

To track the work around integrating the optin/out for the about:addons newsletter with Basket/Salesforce CRM.

Notes here:
https://docs.google.com/document/d/1veKGukezRIV_898Y_L_ZJtTtlmLPK7lYfm1fNXMYmU8/edit#
Goal is to connect the opt-in forms within the Account settings on addons.mozilla.org with Basket - very similar to how we've handled Fx Accounts email opt-in out in the settings page. 

Rkelly, can you provide some insight into how y'all approached this integration for FxAccounts?

Cc'ing Pmac in case Jorge has questions.


Basket ID:
aboutaddons

This links incoming subscriptions to the field "AMO Email Opt In?" in Salesforce CRM.


Specs of how it should work is here:
https://docs.google.com/document/d/1veKGukezRIV_898Y_L_ZJtTtlmLPK7lYfm1fNXMYmU8/edit#


Basket documentation is here:
https://docs.google.com/document/d/1U1cNTSf9jVweQDMyaB3vxdglSsacOoK4ZJHxIacbaw4/edit#heading=h.nc9p3fo8lsaa


Info on how to set up a stand-alone opt-in form w/ sample email signup form code:
https://docs.google.com/presentation/d/1P9EBDy-i8ULF8cd7k0bN9a38pbI4ketTYMCbKEoEr5Y/edit#slide=id.g1e076a3623_0_0
Flags: needinfo?(rfkelly)
Jorge, assigning to you to triage and reassign as needed.
Assignee: nobody → jorge
See Also: → 1358527
> Rkelly, can you provide some insight into how y'all approached this integration for FxAccounts?

Sorry for the delay here.  Just to clarify, this is intended to be totally separate to the FxA newsletter opt-in, right?

The FxA integration has a lot of complications around capturing the opt-in right at the start of the flow, to cope with e.g. the user checking the checkbox and then not actually confirming their email.

We have a much simpler integration that manages the on/off toggle for the newsletter on the account settings page, which basically works as a simple proxy:

* The user toggles the checkbox on our settings page
* This triggers an authenticated request to our backend API saying 'subscribe' or 'unsubscribe'
* Our backend knows the name of the FxA newsletter and holds a secret API key, so it can translate these into calls to subscribe and unsubscribe at [1]

Happy to share some code if you're interested, but it's got a lot of extra complexity in it to do with OAuth and verification-event handling that you probably don't want to deal with...

[1] http://basket.readthedocs.io/newsletter_api.html
Flags: needinfo?(rfkelly)
Thanks, :rfkelly!  This info is great. This is indeed totally separate to the FxA newsletter opt-in. It's *just* for AMO developers who opt-into ongoing AMO Dev communications.  You nailed it with the info around the on/off toggle in the settings similarity.

Over to Jorge/AMO to dig in whenever the AMO team is ready.

Thanks!
Hey Caitlin & AMO crew!

This is the bug tracking the AMO + Basket integration.

Newsletter ID: about-addons

Github tracking here: https://github.com/mozilla/addons-server/issues/7808

Need for LCM support in an upcoming sprint acknowledged via email & during LCM weekly intake today:
https://docs.google.com/document/d/1hB-PHqLmWhjsoxmbP5Y-Tt0R6YqXoiy9cpmDcYrVhSA/edit#heading=h.fr62v6dcjhvi


We'll keep you posted when we're able to prioritize this story from our backlog.

Thanks!
Checked in with Caitlin today on this project - notes are here:

https://docs.google.com/document/d/10rrMM-aJXTmA4ez1C041tZ8xyqbx5WoLh1lrj_5UTi4/edit#


I'm recommending that we prioritize this for our next sprint (starts Monday, May 21) as the AMO team is actively developing on this integration and needs our help to get it live.


Clarification: This bug is for supporting the newsletter opt-in/out integration from AMO interface, Basket/Salesforce, and our main email preference center.

This does not cover work to sync all AMO data into Salesforce. Only the newsletter opt-in/out.
Integration work is underway & currently in QA testing! https://github.com/mozilla/addons-server/issues/7808

Caitlin, is this the 140 character description for about:addons to be in the email pref center?

"Stay up to date with news and events relevant to Firefox add-on developers"

Once this integration is live, I will make the email program public facing so that any subscriber to any Mozilla program can subscribe to it from their email preference center.


Please let me know when a welcome email is coded and ready in SFMC for this newsletter, and we'll set it up to trigger when new subscribers come in. This doesn't block the AMO Dev user integration from going live, but it's nice to have if we can do it :)


Also not a blocker for this part of the integration, but good to know before you can use the "about-addons" signup code on places not-behind a Firefox Account login, these 3 things will need to happen:

1) AMO team to fix: https://github.com/mozilla/addons-server/issues/8320
2) SFDC setup to trigger a "confirm" message
3) Double opt-in setting in Basket admin to be turned on


Holler if you have questions. Thanks!
Flags: needinfo?(cneiman)
> Caitlin, is this the 140 character description for about:addons to be in the
> email pref center?
> 
> "Stay up to date with news and events relevant to Firefox add-on developers"

Very minor edit: 
"Stay up to date with news and events relevant to Firefox extension developers." 

> Please let me know when a welcome email is coded and ready in SFMC for this
> newsletter, and we'll set it up to trigger when new subscribers come in.
> This doesn't block the AMO Dev user integration from going live, but it's
> nice to have if we can do it :)

The email's name is SF is MoCo_GLOBAL_AMO_2018_NEWS_HTML_WELCOME-TO-ABOUT-ADDONS_ALL_EN_EML. It's good to go pending final sign off by Jess, Michele, and Amy. 

\o/
Flags: needinfo?(cneiman)
Amy just signed off on the welcome email. We're ready to roll!
Wait! "up to date" should have hyphens: "up-to-date", and should be "on" instead of "with". Thanks
Jorge & Andrew - y'all on tap to do an export and import (aka manual refresh) once this goes live tomorrow? I can let you know when it's live.
Flags: needinfo?(jorge)
Flags: needinfo?(amorales)
I uploaded the new data on Monday, per bug 1462050.
Flags: needinfo?(jorge)
Jorge, would it be possible to do one last data pull tomorrow? Andrew hasn't done the import yet, and the integration is set to go live tomorrow. If we use the current pull from Monday, we risk 5 days of unsync'ed data - is that risk acceptable?


Caitlin & Amy, the email preference center on production has been enabled for "about:addons" (about-addons) with the description:
"Stay up-to-date on news and events relevant to Firefox extension developers." 


Once I get confirmation we're live and running well tomorrow (in https://github.com/mozilla/addons-server/issues/7808 ), and the db is refreshed (Jorge/Andrew), I'll turn on the public facing setting for this email program. Then you'll be able to send your emails using the our standard email preference center links and anyone who visits their email pref center can opt-into this email program :)

I'm holding on implementing the welcome email until our databases are linked and refreshed (to avoid accidentally welcoming people who have been subscribed for awhile).
Flags: needinfo?(amorales) → needinfo?(jorge)
The integration was pushed live today, but it's gated behind a flag. We can't turn it on until the SF data sync happens.

I can do an export whenever; takes like 15 mins. But I need some idea of when the import will happen.
Flags: needinfo?(jorge)
Thanks, Jorge. I heard the flag won't be turned on till tomorrow am. Does that mean you + Andrew should coordinate a refresh for tomorrow morning?  Or if Andrew can refresh it today, it can go live today?
Flags: needinfo?(jorge)
I just talked with Andrew and Jorge; we're going to run another export from AMO and send it over to Andrew today for a refresh either today or tomorrow.
The data is now refreshed. Andrew, please proceed with the import. One note: I'm running into some upload problems due to file size, so I had to split the addons.csv file into three files. Hope that's not a problem.

> I heard the flag won't be turned on till tomorrow am.

We need QA to test it when the flip the switch, and they are generally only available early in the day. So, we need the data to be ready by tomorrow morning or wait until next week to turn it on.
Flags: needinfo?(jorge) → needinfo?(amorales)
Hi All, the last job is running now and should be done within the next hour or two. I will let you know if I see any issues, otherwise we should be good to go for the send next week.
Flags: needinfo?(amorales)
Woooot! 

Issue 7808 (https://github.com/mozilla/addons-server/issues/7808#issuecomment-391727327) on Github has been updated with instructions for the AMO engineers + QA folks to turn on the integration on Monday, My 28 and test. Because Monday is a US holiday, Jess and I are on standby to troubleshoot on Tuesday.
See Also: → 1465620
Integration is live and AMO newsletter sent! \o/

Going to close this out as the "signup form" integration is complete.

Filed new bug to implement the double opt-in & welcome email process for new about:addons developers:
Bug 1465620 - Enable about:addons welcome & subscription confirm process
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.