Closed
Bug 1429538
Opened 8 years ago
Closed 8 years ago
CRM/Email Marketing Request: Mozilla Newsletter - Issue #1-2018
Categories
(Marketing :: Email, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mjkelly, Unassigned)
Details
Attachments
(1 file)
|
53.94 KB,
image/jpeg
|
Details |
>> Mozilla Team/Department
Mozilla Marketing - Conscious Choosers Durable Team
>> What kind of relationships are you looking to develop?
Brand relationships with conscious chooser consumer audience that increase email retention and engagement
>> How will you nurture these relationships?
Send regular emails with useful, interesting, actionable content
>> How will success be measured?
Open rate, CTR, comments on blog, sharing of content
>> What is the risk to not doing this?
Reduced audience for our content
>> What's the timeline for launch?
Wednesday, Jan. 17, 2018
Copy and visual will turn over on Friday, Jan. 12.
>> Any other info we should know?
User story: [Newsletter Issue 1] As a Mozilla email subscriber, I'd like to get New Years resolution tips to be more in control of my online privacy.
| Reporter | ||
Comment 1•8 years ago
|
||
Here's the copy. Michael will post the header graphic this morning.
https://docs.google.com/document/d/1JZ1SXoq6I3U-MSAIrysZUjCoWV2H-XQeoRhoFT5bKz4/edit
| Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(mham)
Comment 3•8 years ago
|
||
We received a green light on the email proof.
Issue #1 is scheduled to deploy to the Mozilla EN audience tomorrow morning, 1/17/18 at 6am PT.
A/B subject lines:
- 3 steps to better digital fitness
- Digital cleanse in 1, 2, 3
I'll circle back once I've confirmed the sends have gone out successfully!
Comment 4•8 years ago
|
||
The test launched as planned!
A) 3 steps to better digital fitness (9.33% open rate)
B) Digital cleanse in 1, 2, 3 (10.4% open rate) - WINNER
Closing out this bug, and will send more detail on email performance via email soon.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•