Closed
Bug 1054316
Opened 11 years ago
Closed 11 years ago
Trigger FxAccounts Welcome in Right Language and Format
Categories
(Websites :: Basket, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jdavis, Assigned: pmac)
References
(Blocks 1 open bug)
Details
Once a Firefox Account has been confirmed (not just created), an API call should send the user's information into ExactTarget (Bug 1051806) and a Firefox Account welcome email should be triggered in the correct language and format (similar to Bug 874607 & Bug 884598).
Internal naming convention of email is as follows:
Language(2)_Name_of_Trigger_EmailFormatIfText
For this feature it will be:
ES_FxAccounts_Welcome
or
PT_FxAccounts_Welcome_T
*Note: Language is only 2 characters (PT or ES), not 5 (pt-BR or es-ES)
Actions:
1) Pmac to hard-code this functionality into the new basket API endpoint (Bug 1051806)
2) Jess to create trigger infrastructure inside of ExactTarget with naming convention above
3) Jess to create content bug & plan for this welcome email and any follow-up emails (Bug to come)
Updated•11 years ago
|
Summary: [basket] trigger FxAccounts welcome in right language and format → Trigger FxAccounts Welcome in Right Language and Format
Updated•11 years ago
|
Product: Other Applications → Websites
| Assignee | ||
Comment 1•11 years ago
|
||
Unless the user has previously signed up for a newsletter we won't know their email format preference at the point we receive the registration call from FxA (they don't collect that). Should we default to HTML or Text?
Flags: needinfo?(jdavis)
| Reporter | ||
Comment 2•11 years ago
|
||
Default to HTML please. (This is similar to how we have the Marketplace Signup form setup after chats with Legal - Bug 874932)
Flags: needinfo?(jdavis)
| Assignee | ||
Comment 3•11 years ago
|
||
One more question. We'll be collecting their language from FxA as well. There could theoretically be a situation where they have a different language in ET than what they set in FxA. What should we do in that case? I'd think we could trust the value from FxA, but it might be odd for them to start getting newsletters in a different language after having set it in FxA signup.
My suggestion is that we send the welcome message in the lang that comes through from FxA, and set that language in ET only if they don't already have one set there.
| Assignee | ||
Updated•11 years ago
|
Flags: needinfo?(jdavis)
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → pmac
Comment 4•11 years ago
|
||
Commit pushed to master at https://github.com/mozilla/basket
https://github.com/mozilla/basket/commit/92f1d35b2963179c2cf3017297a751ee6bd4764a
Bug 1054316: Trigger welcome email for fxa registeration.
| Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 5•11 years ago
|
||
(In reply to Paul McLanahan [:pmac] from comment #3)
> One more question. We'll be collecting their language from FxA as well.
> There could theoretically be a situation where they have a different
> language in ET than what they set in FxA. What should we do in that case?
> I'd think we could trust the value from FxA, but it might be odd for them to
> start getting newsletters in a different language after having set it in FxA
> signup.
After chatting with pmac on IRC, it's important to avoid overwriting a newsletter subscriber's language (limited to 9 options at the moment), with their Firefox Account's language (unlimited possibilities based on browser locale). The language for a Firefox Account should be passed through to this new field:
FXA_LANGUAGE_ISO2
This work is outlined in Bug 1066655.
Flags: needinfo?(jdavis)
You need to log in
before you can comment on or make changes to this bug.
Description
•