 |
instant download | bigsender home | free demo | features | support | languages | user survey | administrator guide | forum | testimonials | desktops | e-news gallery | version history | news2me
BigSender Administrator Guide
Personalizing Broadcast Messages
For greater impact, your BigSender Broadcast Messages may be personalized with data from each record in your list to distinguish it from other generic and impersonal mass-email messages.
To start with, all BigSender messages are always sent with your list recipient in the "To:" email header.
With BigSender, it is also easy to personalize the "Subject:" and the "body" of your Broadcast Message with data from each recipient's record.
BigSender's standard fields (email, name or fname and lname) along with the #DATE# Code and those associated with any Custom Fields you set in the BigSender Configurator may be used to personalize each Broadcast message.
Once a Custom Field is set in the Configurator, the Personalization Code for that field is immediately available for use in the BigSender Message Composer. (Note: To protect confidential data that may be contained in an "annotations" Custom Field Type, a field set as an "annotations" field type is not available for personalizing messages.)
For example, to personalize the plain-text version of your message with the recipient's name, use the Message Composer's "insert" pulldown selector and choose "name" and the text in your plain-text Composer field is appended with the #NAME# Personalization Code. Alternatively, you may simply type any valid Personalization Codes into the "subject," "plain-text" and "html-text" BigSender Message Composer fields.
If your records contain first names and last names in unique fields and you use the #NAME# Personalization Code, BigSender dynamically combines data from the "first name" field (if existent) and "last name" field (if existent) and puts a space between them) or you may use #FNAME# and/or #LNAME# Personalization Codes independently. If there is no data in the name field of a record, #NAME# is replaced with the "substitute" value you set in the Configurator.
For your convenience, Personalization Codes are not case-sensitive (#name# or #Name# or even #NaMe# works as well as #NAME#). To ensure any links in your BigSender Message are not "broken," personalization codes within a hyperlink must begin with two pound signs (##) and end with two pound signs (##). For example: <A HREF="http://yourdomain.com?name=##NAME##&email=##email##">click here</A>
During your Broadcast Session, BigSender automatically replaces all Personalization Codes in your message with data from each record.
|
|
|
|
