Add First and Last name to Newsletter intake form

[jendefig]

I would like to add fields from First and last name to the intake form for the DVC Newsletter on the site so that I can better personalize email messages.

[julieg18]

This form?

I don't remember when exactly, but didn't we discuss whether we should do this in the past? I think I remember someone mentioning adding extra fields to the form may have some cons 🤔 cc @iterative/websites

[rogermparent]

I don't remember when exactly, but didn't we discuss whether we should do this in the past?

I was thinking the same thing, but I can't find the exact Issue. I think first and last may make it seem a bit intrusive and/or cumbersome. I could see a single "name" field working better, but even then without any deeper personalization it may deter more users than it does increase open rates for.

There's also the issue of how we handle all the subscribers we have that don't have names input, as well as people that don't input names- do MailChimp templates support logic for optional fields?

That all said, I'm not to attached either way so if we all agree we want it then the implementation shouldn't be too difficult given MailChimp supports it, which I'm pretty sure it does.

[jendefig]

I think first and last may make it seem a bit intrusive and/or cumbersome. I could see a single "name" field working better, but even then without any deeper personalization it may deter more users than it does increase open rates for.

I'd be totally ok with just first name. I think the original reason was to not be intrusive. We are collecting more for Studio and that makes sense. In this case with the open source tools, I think being less intrusive is desirable, but I would like to make people feel more welcome and part of the Community instead.

There's also the issue of how we handle all the subscribers we have that don't have names input, as well as people that don't input names- do MailChimp templates support logic for optional fields?

On this, I think I can set up a tag once the change happens on new ones. Or a stage for items that have the first name field filled out. So there would be a newsletter to the pre-change list with no merge "Hi Friend!" and the new ones with the tag would get the same newsletter, but personalized.

[shcheklein]

I thought we have a mailchimp pop-up or a separate page when you click signup button. It would have made sense to include name there. Have mixed feeling about the main page itself 🤔 any good examples with multiple fields like this on the main page?

at least we'll have to design it a bit ...

[VinayakRugvedi]

I just tested this flow of subscriptions and I have an important note to consider.

@rogermparent @shcheklein @jendefig I believe we are missing an important intermediate step of verification for the entered email. Usually, after entering the email, a verification link needs to be dropped to the provided email address which further confirms the subscription and adds the email to the list of subscribers.

As of now, I can provide any email address and it straight away gets added to the list of subscribers which I don't think is a good way.

When it comes to taking in the name, I don't really think it's necessary as this subscription is completely voluntary. What matters more than the personal touch is the profound content that eventually lands in the inbox. As a starter, the "subscription confirmed" email can be glorified to be informative and attractive with a pinch of curiosity.

Thanks!

[jendefig]

Thanks @VinayakRugvedi! Indeed it is customary to have a verification step. We should definitely consider that.

[dberenbaum]

@jendefig Lowering the priority of this one. Do we still need it? Do we even still want this intake form?

[jendefig]

It would be better. But now I just say "Hi friend" in the emails. So it's ok with a lower priority. It's something that should be addressed in rebranding.

[yathomasi]

Adding fields beside email will have a negative impact on the number of people signing up for the newsletter. And, if we want to greet people, using general ones like "Hi friend", "Hey", or "Hey there" should be fine.

Generally, the ones with proper greetings are the ones that are subscribed once the user registers/signs up to the platform/app/website. So, this is similar to when a user signs up for "Iterative Studio" in our case.

[jendefig]

I think it may make a difference to how the email is accepted by email clients as to whether it goes to promotions (not desirable) or directly to inbox (desirable). I don't know the ins and outs of this. I haven't had time to study.