|
| Home | Introduction | Quick Help |
|
[FAQ 911012] What is {Tags}? Address database {tags}: {FirstName} => Represent the receiver's first
name. Example: Many times use as a salute in the email body and/or Subject
matter. {LastName} => Represent the receiver's last name.
Example: Sometime in more formal emails this could be a part of the salute. {Company} => Represent the receiver's company
name. Example: Like found is question about the receivers company “{FirstName},
does {Company} use eBlast to stay in contact with it clients?” {Category} => Represent the receiver's category
list. Note: This is a tricky
{Tag} since it could be either one single category or it could be a group of
categories. Incase of a group of categories each category is separated by the
string “ – “. {Created} => Represent the date the Address
database record was created. Example: Not likely used but is included since it
is a part of the database and maybe the creation date is needed in the email. {Updated} => Represent the date the Address
database record was last updated. Example:
Not likely used but is included since it is a part of the database and maybe
the updated date is needed in the email. {LastMailing} => Represent the date of the last
email sent to the receiver. Example: Can be used to printout to the receiver
last should have received a newsletter. {Unsubscribed} => Represent the Boolean Yes/No
depending if the receiver has requested to be un-subscribed from the list. Example:
Not likely used but is included since it is a part of the database {BadAddress} => Represent the Boolean Yes/No
depending if the receivers email have been returned due too a bad email
address. Example: Not likely used but is included since it is a part of the
database File {Tags}: {Disclaimer} => Reads the “Disclaimer.Txt” file
found in the “Template” folder and uses the text as replacement for the {Tag}.
Example: This is where most users will put the information about
Spam-Act-of-2003 and that this message is sent in conforming to
Spam-Act-of-2003. For more about smart emailing see “How
to not Spam, why not?” and “Why not comply with
the CAN SPAM Act of 2003?”. {TagLine} => Reads the “TagLine.Txt” file found
in the “Template” folder and uses the text as replacement for the {Tag}.
Example: Most companies or organizations have a tagline. Here at NTS it is “An
Intelligent Alternative” which could be a part of the {Footer}. {Subscribe} => Reads the “Subscribe.Txt” file found
in the “Template” folder and uses the text as replacement for the {Tag}. Sometimes
your email is forward to other, especially if your message is educating or is
describing a product that some “friend” would need. This is why it can be smart to have a link
back to eBlast so the reader can subscribe from within the email. Example: Use
this link to receive this type of emails: [a href="mailto:ntsnews@sbcglobal.net?subject=On-eBlast-List&body=Please
add my name to the NTS eBlast Address List"] Click here [/a] Note: The “[“ and “]” symbols should be replaced by “<” and “>”, the
reason for using it here is that you will not see the text since the browser
would convert it to the actually link. {UnSubscribe} => Reads the “UnSubscribe.Txt” file
found in the “Template” folder and uses the text as replacement for the {Tag}.
To be conforming to Spam-Act-of-2003 (For more about smart emailing see “How to not Spam, why not?” and “Why not comply with the CAN SPAM Act of 2003?”.) all
emails should have a way that the receiver can Opt-Out. Example: At My Software
Company we respect your privacy. If you wish to eliminate yourself from our
mailing list please use this link: [a href="mailto:ntsnews@sbcglobal.net?subject=Off-eBlast-List&body=
Please eliminate my name from the
NTS eBlast Address List"] Click here [/a] Note: The “[“ and “]” symbols
should be replaced by “<” and “> , the reason for using it here is that
you will not see the text since the browser would convert it to the actually
link”. {Header} => Reads the “Header.Txt” file found
in the “Template” folder and uses the text as replacement for the {Tag}. Example:
This file could include the collection of standard company or organization top
banner or logo. Maybe even a standard
salute to the receiver. Sample: {FirstName}, here is your monthly eNewsletter –
Friday, September 15, 2006. {Footer} => Reads the “Footer.Txt” file found
in the “Template” folder and uses the text as replacement for the {Tag}.
Example: This file could be a collection of {TagLine}, {Copyright},
{Disclaimer}, {Subscribe} and {UnSubscribe}. {File:d:path\filename.ext} => Reads the ASCII “d:path\filename.ext”
file and uses the text as replacement for the {Tag}. Example: Should the above fixed names not cut
it then this is a way to insert simple text. The eNewsLetter may have three
text area; one for the message from the president, one article and then one
announcement. Then this three text areas
could be stored in three different ASCII files and eBlast will automatic insert
the text before the emails is sent. HTTP {Tags}: Internal {Tags}: Friday, September 15, 2006 => Will insert the current date in the
format of Mar 31, 2006. Example: All messages should have a date. Many times
the short date is used in the Subject matter where as the long date is used in
the email Body. {TrackingNo} => Will insert a unique Tracking
Number representing the sent email. Example: Sometimes you want the receiver to
email you back as a part of a promotional and at that time the eBlast internal
tracking number would be a great way to pinpoint witch message this came
from. Note: The tracking number is a combination of the Hard disk serial number +
date of the mailing + sequential number of the mailings. {FromName} => Will insert the value found in the
Setup on the Mailing Info tab field “From Name”. Example: Sometimes in the
{Disclaimer} one wants to include the sender name. {FromEmailAddress} => Will insert the value found in the
Setup on the Mailing Info tab field “From Email Address”. Example: Sometimes in
the {Disclaimer} one wants to include the sender email address. |
|
|||
|
Rev: Friday, September 15, 2006 Copyright (c) 2006 New:Team SoftWare, Inc.. All rights reserved. Reproduction in whole or in part in any form or medium without express written permission of NTS is prohibited. NTS, NTS Icons and the NTS logo are trademarks of New:Team SoftWare, Inc.. |