Skip to main content

Hi all,

I noticed that newly created emails in Customer.IO send to {{customer.email}} by default, but our service mandatorily collects first and last name so I’m thinking of doing this instead:

 

{{customer.first_name}} {{customer.last_name}} <{{customer.email}}>

 

Is there a benefit to doing it in one way or the other? For some reason, it just feels right to me that, if we have their first and last name, we’d use that in our email TO line. But maybe I’m missing something.

One more question: is it possible to change the CIO default, so I don’t have to update it to the above every time?

Thanks!
TOM

Hi @divinetomedy ,

We would recommend that you use {{customer.email}} as we’re looking for the email address in this field. So, inputting John Smith john.smith@example.com in the To field would cause the email to fail as this is not the correct email address syntax that email providers are expecting.

If you’d like to increase the personalisation of that email, you can include {{customer.first_name}} in the subject or in the body content for example. ;)

At the moment, I’m afraid it isn’t possible to change the default “to” field to a different attribute. 

Hopefully, this helps to clarify!

 

Best,

Penny

 


Hi Penny!

Thanks for the reply. I’m curious though. I actually have it working right now (and it doesn’t look like there are any deliverability problems) when I put the following format in the TO field:

{{customer.first_name}} {{customer.last_name}} <{{customer.email}}>

Example:

Tom Clifton <tom@getscreenable.com>

It’s currently working great...I think? Am I missing something?

Thanks!
TOM

 


Hi Tom,

Apologies, I missed out on seeing that you’re using the angular brackets for the {{customer.email}} field. 

In this case, if you do specify the email address within the angular bracket <{{customer.email}}>, this would work as expected! 

Sorry about that but I hope this helps to clarify!


Great, thanks Penny! Much appreciated.


Reply