For simple functionality’s sake, we generally want our phpList messages to contain at least a small amount of customization. For example, even the default footer, which phpList attaches to messages, contains three placeholders, customizing each message for each recipient:
—
If you do not want to receive any more newsletters, [UNSUBSCRIBE]
To update your preferences and to unsubscribe, visit [PREFERENCES]
Forward a Message to Someone [FORWARD]
The placeholders [UNSUBSCRIBE],[PREFERENCES], and [FORWARD] will be replaced with unique URLs per subscriber, allowing any subscriber to immediately unsubscribe, adjust their preferences, or forward a message to a friend simply by clicking on a link.
There’s a complete list of available placeholders documented on phpList’s wiki page at http://docs.phplist.com/Placeholders. Here are some of the most frequently used ones:
You might combine several of these placeholders to add a standard signature to your messages, as follows:
—
You ([EMAIL]) are receiving this message because you subscribed to
one or more of our mailing lists.
We only send messages to subscribers who have requested and
confirmed their subscription (double-opt-in). You can adjust
your list membership at any time by clicking on [PREFERENCES]
or unsubscribe altogether by clicking on [UNSUBSCRIBE].
—
Some placeholders (such as [LISTS]) are only applicable in confirmation messages (that is, “thank you for subscribing to the following lists…”). These placeholders allow you to customize the following:
Apart from the built-in placeholders, you can also use any member attributes to further personalize your messages. Say you captured the following attributes from your new members:
You could craft a personalized message as follows:
Dear [FIRST NAME],
Hello from your friends at the Funky Town Restaurant. We hope the
[LAST NAME] family is well in the friendly town of [HOMETOWN].
If you’re ever in the mood for a fresh [FAVORITE FOOD], please
drop in – we’d be happy to have you!
…
This would appear to different subscribers as:
Dear Bart,
Hello from your friends at the Funky Town Restaurant. We hope the
Simpson family is well in the friendly town of Springfield.
If you’re ever in the mood for a fresh pizza, please drop in – we’d
be happy to have you!
…
Or:
Dear Clark,
Hello from your friends at the Funky Town Restaurant. We hope the
Kent family is well in the friendly town of Smallville.
If you’re ever in the mood for a fresh Krypto-Burger, please drop
in – we’d be happy to have you!
…
If a user doesn’t have an attribute for a particular placeholder, it will be replaced with a blank space. For example, if user “Mary” hadn’t entered any attributes, her message would look like:
Dear,
Hello from your friends at the Funky Town Restaurant. We hope the
family is well in the friendly town of .
If you’re ever in the mood for a fresh , please drop in – we’d be
happy to have you!
…
If the attributes on your subscription form are optional, try to structure your content in such a way that a blank placeholder substitution won’t ruin the text. For example, the following text will look awkward with blank substitutions:
Your name is [FIRST NAME], your favorite food is [FAVORITE FOOD],
and your last name is [LAST NAME]
Whereas the following text would at least “degrade gracefully”:
Your name: [FIRST NAME]
Your favorite food: [FAVORITE FOOD]
Your last name [LAST NAME]
I remember deciding to pursue my first IT certification, the CompTIA A+. I had signed…
Key takeaways The transformer architecture has proved to be revolutionary in outperforming the classical RNN…
Once we learn how to deploy an Ubuntu server, how to manage users, and how…
Key-takeaways: Clean code isn’t just a nice thing to have or a luxury in software projects; it's a necessity. If we…
While developing a web application, or setting dynamic pages and meta tags we need to deal with…
Software architecture is one of the most discussed topics in the software industry today, and…