Closed Bug 1536484 Opened 7 years ago Closed 7 years ago

CRM/Email Marketing Request: Activate

Categories

(Marketing :: Email, task)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: couci, Unassigned)

Details

Mozilla Team/Department
Community Development Team in Open Innovation
What kind of relationships are you looking to develop?
We already have a email program that got reactivated back in October. Right now it is only in English and we are looking to activate it in 5 more locals.

In order to do so we need to firstly add the first 5 languages on our newsletter landing page as an option and to ensure that salesforce is getting the language information from the activate site when a user is adding their language.

Both language and country drop down will be optional and there will be a message informing the subscribers that sometimes they will receive information in those languages.

How will you nurture these relationships?
By creating content for the first 5 Firefox locals: German, Spanish, french, Portuguese and Russian
How will success be measured?
By seeing more engagement on the specific locals we are localizing content for
What is the risk to not doing this?
Disengage communities and new contributors that don't feel confident interacting in English
Also this is blocking us from doing the
What's the timeline for launch?
We are planning for the big launch next week
Any other info we should know?
In order to launch the language information we need to have both the welcome email and the double opt in emails localized.

The welcome email is localized here: https://docs.google.com/spreadsheets/d/1Mx4n5Dmf_z0E8x8Zj2Ye9IanNEP-MKIGvrKvwWy7lRE/edit#gid=55987274
The opt in email is missing two locals, I am working with the l10n team to have it ready by the end of the week or earlier.

What we are asking from the email marketing team is help once everything is ready on our side (early next week) to test that the language information is passing through

Opt in emails are ready as well, those can be found here: https://drive.google.com/open?id=1JWuWKX0Kvioikrc6anSvDbPYuG6Er6JeX1An4GSBsQA

@bhaack should I add them on the folders you indicated manually? Or is this something you will do? And once this is done, will you do the testing ?

Since we are already 2 weeks late, I would appreciate if we could make it happen by the end of the week.

thanks :)

Flags: needinfo?(lwright)
Flags: needinfo?(bhaack)

(In reply to Konstantina Papadea [:couci] from comment #1)

Opt in emails are ready as well, those can be found here: https://drive.google.com/open?id=1JWuWKX0Kvioikrc6anSvDbPYuG6Er6JeX1An4GSBsQA

@bhaack should I add them on the folders you indicated manually? Or is this something you will do? And once this is done, will you do the testing ?

Since we are already 2 weeks late, I would appreciate if we could make it happen by the end of the week.

thanks :)

Hi Konstantina! In the confirmation email doc, I only see ID?

Flags: needinfo?(bhaack)

Hey :bhaack I apologize wrong copy paste.

Here you go https://drive.google.com/drive/folders/18cHANwiN9rBI07zvC-Bha0aWjxPBbf1q

Flags: needinfo?(bhaack)

Hi Konstantina -

  • The welcome emails have been coded in DE, ES, FR, pt-BR and RU
  • The confirmation email have been coded in ID, zh-TW, pt-BR and RU

I have sent proofs to you + the l10n teams for review, except for the zh-TW confirmation email as I don't have any contacts this locale. Is this something you can help facilitate?

Welcome emails live here: Content Builder > Shared Emails > 02 Automated Sends > Triggered Sends > Welcome Emails > Mozilla Communities

Confirmation emails live here: Content Builder > Shared Emails > 02 Automated Sends > Triggered Sends > Confirmation Emails > Foundation

Once we get the green light from the l10n teams, I will set up the triggers in Marketing Cloud, add the emails to Basket and test them.

Flags: needinfo?(lwright)
Flags: needinfo?(bhaack)

thanks @brynne I will send over to contributors for zh-TW

btw would it be also possible to test e-mails from this link: https://activate.mozilla.community/newsletter

This would be the link that we will give to individuals to sign up so I want to ensure it comes through correctly

thanks :)

(In reply to Konstantina Papadea [:couci] from comment #5)

thanks @brynne I will send over to contributors for zh-TW

Great, thank you! Please let me know if they have any edits.

Hi Konstantina -

Yes, we'll test everything behind the scenes before it goes live, as well as once it's live :)

Brynne

thanks a lot :bhaack

the contributor from Taipei made some changes on the zh-TW doc, you can find them in column F. He basically explained to me that usually when they speak they flip the sentence.

Let me know when we are ready to launch

Thanks! I have updated the zh-TW confirmation email if you want to pass along a final version to the contributor. It lives here:

Content Builder > Shared Emails > 02 Automated Sends > Triggered Sends > Confirmation Emails > Foundation > MoFo_GLOBAL_MOZ_2019_TRAN_HTML_Confirmation_ALL_zh-TW_EML

Hi Konstantina - I have everything set up for DE, ES, FR, RU and pt-BR on my end. Can you have your team push things live to a staging/sandbox area for testing before going live? Let me know when we're ready to test :)

Thanks,
Brynne

thanks :bhaack, adding Michael here that is the contributor who is doing the tests for us

:bhaack we have our staging website here: https://activate-test.michaelkohler.info/
Should we just start subscribing with different emails and different language combinations to see if we go through? Or what is the usual process

Flags: needinfo?(bhaack)

(In reply to Konstantina Papadea [:couci] from comment #13)

:bhaack we have our staging website here: https://activate-test.michaelkohler.info/

https://activate-test.michaelkohler.info/ is updated so it's pt-BR instead of pt, as well as using native names for the languages. IMHO this is ready for you to test from my side.

Hi Michael and Konstantina! I ran into a Salesforce snag while testing and am waiting for their support team to resolve. I'm hoping to wrap up testing tomorrow. Will provide an update as soon as I can :)

Flags: needinfo?(bhaack)

Hey :bhaack do we have a status update here?
apologies for the late pings but we would like to launch this week.

Sorry for the delay! I was able to successfully test DE, ES and FR but received the following errors for pt-BR and RU:

Select a valid choice. pl is not one of the available choices. (I believe this should be RU, not PL)

Select a valid choice. pt-BR is not one of the available choices.

I'm also wondering if we should add English to the drop down list? I know we have the disclaimer that we'll default to English, but I think it might make sense to add it as well.

Please let me know when RU and pt-BR are updated and I'll test again :)

Brynne

(In reply to bhaack from comment #17)

Select a valid choice. pl is not one of the available choices. (I believe this should be RU, not PL)

Yes, indeed, my fault. Will update once the question below is answered so I can do all together.

Select a valid choice. pt-BR is not one of the available choices.

What would the valid choice be? Just pt?

I'm also wondering if we should add English to the drop down list? I know we have the disclaimer that we'll default to English, but I think it might make sense to add it as well.

That's for Konstantina, but I think this indeed would make sense.

Correct, the back end value should just be PT.

Thanks, RU and PT is now fixed on https://activate-test.michaelkohler.info/

Hi Michael and Konstantina -

DE, ES, FR and RU have all been tested and are good to launch.

I have successfully test pt-BR on the back end, but when I test via the staging site it doesn't work.

@Michael, can you double check that it's set up correctly? If it looks good on your end, let's try "pt-BR" instead of just "pt" (my point of contact for help on this is out on PTO this week, otherwise I'd run it by him vs. trial and error).

@Konstantina, let us know if you're okay with adding EN to the language drop down.

Thanks,
Brynne

So the language on the sign up will be: we might send to other languages if you want to hear from us in those languages let us know. But I understand people might get confused by not seeing English so yes let's add it for simplification and confusion avoidance

(In reply to bhaack from comment #21)

@Michael, can you double check that it's set up correctly? If it looks good on your end, let's try "pt-BR" instead of just "pt" (my point of contact for help on this is out on PTO this week, otherwise I'd run it by him vs. trial and error).

I've now added both for testing purposes:

  • PT: Português
  • pt-BR: Português do Brasil

Also, if we add English, would that be EN or en-US? ;)

(In reply to Michael Kohler [:mkohler] from comment #24)

Also, if we add English, would that be EN or en-US? ;)

English is EN

PT is working \o/ (let's go ahead and remove pt-BR)

(In reply to bhaack from comment #26)

PT is working \o/ (let's go ahead and remove pt-BR)

Done, and I've added English.

English is working :)

With all the locales testing out okay, you can go ahead and push these updates live!

Brynne

Sounds like we can close out this bug now. Please re-open if anything else comes up on this. Thanks!

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.