I was wondering if there were any other special fields available in the Newsletter - maybe something like #displayname# or #emailaddress# ?

Having that would make it possible to personalize the newsletter like: 

• Hi #displayname#, we wanted you to know that pictures from our latest event have been posted on our website.

Would result in text like this:

• "Hi Joe, we wanted you to know that pictures from our latest event have been posted on our website."

If this is in the online documentation I cant find it - so a link to that info would be appreciated!

Hi Joe,

Any thoughts on when you might implement this feature?  The ability to personalise newsletters would be great.

Thanks,

Michael

+1 for firstname and lastname being usable tokens in the username (I suppose title would be usefultoo so we can have "Dear Mr Smith")

I suppose the ideal would be to be able to use any user profile entity as a token (plus firstname and lastname from the users table of course!)

I'd prefer blank if there's nothing to replace the token with, although I suppose the cherry on the cake would be some kind of conditional clause so that you could use one bit of text if the token existed and another if it didn't...

Using "subscriber" would work for me. 

Even better would be a setting in the feature or in the User.Config that could be changed from "subscriber" to something else like "fan" or "patron".

Regarding what to do if the referenced property is empty, there could be a simple convention in the token, such as #firstname#subscriber# or #firstname#valued crustomer#  where the optional second element is used to provide the text that would be used if the property was empty.