Related tickets: #2994 & #2948
We need a plan to track and test these updates and other possible variations.
Other possible test could include more movement-y copy options: benchmarks here
Note Donate numbers from Will for the last year: 688 donations for $19,525

Compared to visits:

cc @beccaklam @xmatthewx
Hi @WillatMozFdn! Tagging you in this ticket. Some context: we are updating the nav to include a newsletter sign up button. It will be next to our donate button:

We want to set up tracking so we can see whether or not this design suppresses donations (compared to last year? or is there another control we could test against?). What would be the best way to do this?
@kristinashu not sure if we shoulld do A/B testing for this. My reservation is do we want to lose 50% of potential traffic? Or we time it for a specific period of time where we know we'll have high traffic to do a quick test? Alternatively, we A/B test for a longer period when it's slower so we don't lose out on potential sign ups during a high traffic period.
The other thing is that using last year's donate/newsletter sign up results against our new design is already sort of an A/B test in itself? @WillatMozFdn @stephaniemcv any thoughts here? Tagging you both for your testing knowledge but let me know if there's someone else I should talk to. @anilkanji Do you have thoughts about A/B testing and not showing the signup button to 50% of traffic?
Unfortunately I don't think this is reliably test-able, at all. Last year's overall conditions, site content, and traffic patterns were not the exact same as this year's will be, so, that's not a valid control. In theory, without our lean data policies, we could show the newsletter signup to 50% of our visitors, set cookies on whether or not they saw it, and then read back and record those cookies as they donate ... but our policies don't support that type of thing and we also don't have the infrastructure to implement it.
Also not sure about the use of usertesting.com. The UX/UI seems straightforward enough, and the above tests may be able to tell us enough about whether the design is effective. I can do some quick in person tests though and see how people do. Will go through analytics later today to see how most people end up on our landing page to think of possible user journeys.
Possible scenarios:
Unfortunately I don't think this is reliably test-able, at all. Last year's overall conditions, site content, and traffic patterns were not the exact same as this year's will be, so, that's not a valid control. In theory, without our lean data policies, we could show the newsletter signup to 50% of our visitors, set cookies on whether or not they saw it, and then read back and record those cookies as they donate ... but our policies don't support that type of thing and we also don't have the infrastructure to implement it.
@WillatMozFdn Could we do a plain A/B test then? And see if donations are higher for one version?
@WillatMozFdn The other question here is that the newsletter button could suppress donations a bit but in the long term does it actually get us more donations. Not sure how we would measure that?
@WillatMozFdn Could we compare total number of donations that came through email this year compared to last year? That may tell us if the newsletter button is working? Increased list growth + increased engagement + increased donations?
We could do:
Condition A is only the donate button up there, and we count the # of donations
Condition B is donate button plus newsletter signup up there, and we count the # of donations plus number of newsletter signups. (Assuming everything is tracked correctly.)
Caveats:
More context and caveats: we don't actually have the ability to A/B test this right now so I was hoping we could launch the newsletter signup to everyone and see if it made a significant drop in donations. Significant could mean lower than any other month in the last year??? Would this be bad to do?
@beccaklam I was thinking A/B and usertesting.com would be more for testing the movement-y copy in the future but in-person test could work instead of usertesting.com.
@kristinashu Oh I see! lol I totally took this in the wrong direction then. Sorry about that. @WillatMozFdn does ^ sound good to do?
Hi @WillatMozFdn, just following up with my previous comment. Looks like all we want to do is after we build the newsletter we want to compare last year's donations (month by month? or however long it takes to get statistical significance) to see if the newsletter button causes a significant drop in donations on the landing page. Would that be possible to do?
@kristinashu Oh so the A/B testing is for the copy just to confirm? I think we could do some usertesting.com for that.
Hey Becca - we won't ever get statistical significance on this, because it's not a well-controlled test. Sure, we'll be able to see if donations are up or down from a similar time period last year, but apart from the change to the nav there are numerous other factors that could drive movement in donations one way or the other. 1) Overall site traffic; 2) mix of content on the home page; 3) general changes in the outside environment (economy, US tax law, more competition from other nonprofits & political campaigns, etc) 4) Different mix & cadence of Mozilla emails (including fundraising asks) going out this year vs. last. So if we think this is a good idea, we need to just do it based on gut instinct -- as currently constructed we really cannot make a test out of it.
So after chatting with @WillatMozFdn, we've decided that we'll do a check-in at 6 months to see how the newsletter and donate buttons are performing and if the newsletter button is 'helping' or 'hurting' us overall. Helping being defined as newsletter sign ups are up and donations are ok, and hurting being defined as newsletter sign ups are not up and donations are down. Correct me if I'm wrong Will! Will also mentioned that we will need to add an source tag to on the newsletter sign up in order to gather this data.
Test Copy doc here: https://docs.google.com/document/d/1IlPX7GRa0xGqX5B2f276xi9ADX1WPUPFLZoH2mo9CS0/edit#
Usertesting.com test built here: https://www.usertesting.com/st/te-7QL5XQ6Jz2yM-85PC
After getting feedback from designers will launch next week!
We ran four tests, the user settings we selected were:
Users preferred the 'movement' copy vs our control copy for all six users: This was mainly because of two things:
Users with little knowledge of our issues/Mozilla felt:
Users with a high knowledge of our issues/Mozilla:
_"[Regarding the Internet] I didn't know it needed protecting! Is there a risk of it getting shut down?"_
_"I don't want piles of information 'cause that means I have to read through it and pick out what I want, you know. You kinda need a clearer message of what's the point of this."_
_"Why is my internet use unhealthy? I didn't know it was unhealthy."_
_"[Regarding IHR cup image] What the heck is _that_ on the landing page? [...] It looks like a meme gone wrong. [...] I don't know why that would be first thing [on the page]."_
_"[Regarding the home page] It screams millennial to me."_ (Note: Funny enough, the millennials who saw this page either didn't mind the cup image or liked it)
_"I'm actually really impressed that it [the movement text] changed my opinion [previously against signing up for email lists]. It's much more appealing to me."_
This is so awesome @beccaklam. Thanks for the excellent, succinct report on your findings.
Awesome summary and test! Sooo interesting to see.
Here are a few possible next steps:
I will open new tickets for:
I updated the report with the findings from the last two users. Results were starting to repeat so I think we're good on findings. Slacked Anil to confirm copy. Also! @xmatthewx @kristinashu About the cup image -- millennials did prefer it/indifferent to it. We should talk more about audience types. Older, younger, internet savvy, not internet savvy.
Anil confirmed copy (sticking with what we tested). Implementation ticket opened here: #3161
Most helpful comment
This is so awesome @beccaklam. Thanks for the excellent, succinct report on your findings.