Despite it being April Fool's Day, this is no joke. It's 4.1 on 4/1.

StrongMail EAS and Message Studio 4.1 are now available for download. These latest releases of the StrongMail software have a lot a great new features that will appeal to a wide range of users. Customers using Message Studio 3.2.x will be especially interested in the new Migration Tool that we have included which will make the transition from version 3 to version 4 a snap!

Here's a quick breakdown of some of the new features in each version--

StrongMail EAS 4.1

• Overflow to Disk
  Customers can now configure their injecting applications to send SMTP messages to a StrongMail server at a high sustained rate. The StrongMail server buffers the incoming messages to disk to avoid sending server busy messages back to the injecting application. There are two modes, Memory Queue and Disk Queue, that users can choose based on their business requirements.
  

• Pause/Resume Message Assembly API
  StrongMail has added the ability for applications to request that message assembly be paused temporarily but still allow the StrongMail server to continue to accept transactional mailing SEND requests and queue them up until a resume request is received. This enables users to make changes to the transactional mailing without having to shut down the entire transactional messaging process.
  

Message Studio 4.1

• Transactional Mailings
  Customers now have the ability to create, manage, and test transactional mailings through the Message Studio user interface.
  

• User-Defined Asset Lists
  Most menu categories now support user-defined lists. Users can select items and either right-click or drag-and-drop items into the list to create your a custom collection for browsing and organizing data.
  

• Expanded External Data Sources
  This release introduces support for connecting to the following external databases: PostgreSQL, Sybase, IBM DB/2.
  

• Automated Web Analytics Tags
  The Add Tracking Tags screen has been enhanced to allow users to easily add parameters to the tracking URLs that are utilized by web analytics applications. Users can create their own tags or modify the default tags for the following products: Omniture, Coremetrics, and Google Analytics. This feature works with any link-based web analytics software.
  

• Target Editor Enhancements
  The Target Query editor now supports grouping terms with parentheses and allows the of deleting specific terms from a query. Additionally, a data preview button allows users to browse the values contained in a database column and select the value into the query.
  

• Migration Tool
  A new migration tool enables the migration of data from existing Message Studio installations from versions 3.2.3 and 3.2.4 to version 4.1 (upgrades from 4.0 do not need to migrate any data). The migration utility is automatically invoked when you run the setup script for Message Studio 4.1 using the upgrade mode.
  

These are just the highlights. There's much more in each of these releases than I have room to list. If you are a current StrongMail customer, visit the Support Portal today or contact StrongMail Support to get ready for Version 4.1! If you are not a current StrongMail customer and want more information about version 4.1, contact our Sales team to learn more.

In my last post, I introduced the concept of using StrongMail's token capabilities as a way to add relevance to your messages. But as I alluded to in that post, tokens are versatile tools that in addition to inserting personalization data, can also aid in managing and modifying your content with minimal effort.

I'm going to illustrate two ways that you can use tokens, along with content blocks to minimize the amount of work you need to do to get your mailings out each time. The first one involves locking down the template and just editing the copy. The second one makes certain parts of the template reusable across multiple mailings.

METHOD 1: Locking Down the Template

Many of you out there have invested heavily in your email template(s). You've had designers re-do the layout and spent countless hours and dollars getting the design just the way you want it. All that remains for each mailing is plugging in the content specific to each mailing.

Now, you can edit the whole template for each mailing, which can introduce rendering issues and/or template breakage or you can identify which parts of the template change for each mailing and tokenize them. Then all you have to do is upload the part that has changed as a content block and reference it using tokens.

This keeps the layout HTML stable while letting you or your copy editors fiddle with the copy as much as you want. When you are done, just upload the content block file and send a test email to see how it all gets assembled. Using this method, you could even have multiple people working on different parts of the copy without having to worry about one person over-writing another.

This method does take a little extra effort to compartmentalize the template and set up the token/content block schema, but that's a one-time cost and moving to this method can greatly improve your content editing process, especially if your template has a lot of moving parts.

METHOD 2: Reusable Pieces

Maybe you don't have a single template that you use for all of your mailings, but you do have parts that get re-used over and over in different mailing. Things like the mast head or side bar or unsubscribe text. If that's the case, you can start tokenizing the elements that get reused from mailing to mailing.

There are two ways to approach tokenizing the content elements. The first involves creating a single content block file that has all of the reusable elements in it. This option has the benefit of keeping things simple; there's only one one file to keep track of and everything is all in one place. The trade-off is that when a change needs to be made to one element in the content block, you have to edit the file that has ALL of the elements, which could increase the risk of unintentionally modifying one of the other elements.

The second option involves putting each reusable element into its own content block file. Going this route protects you against accidentally corrupting other elements and also lets you use the individual files as building blocks, but it also means keeping track of more files for each mailing.

Once you select how you want to manage the reusable elements, you can easily call those assets from the content block(s) using tokens and then, as in method 1 above, focus on the parts of the email template that change from mailing to mailing.

Whichever method you use, the goal is to make executing your mailings easier, while providing flexibility and control over your content. If you need more information about how to use tokens and content blocks, take a look at Chapter 6, Customizing a Mailing, in the StrongMail System Administrator's Manual.

Many email marketers want to encourage their subscribers to reach out to people that they know and encourage them to either subscribe to the newsletter or go to the website. This can be accomplished two ways--the recipient uses the forward feature of their email software to send a copy of the email to others or they click on a link in the email which sends another email to the address(es) that the original recipient enters.

The first method is certainly the easiest for both the marketer and the recipient, but it has several shortcomings:

• No tracking
  Every click on the forwarded email looks like a click from the original recipient
  
  
• Lack of control over the offer
  If you are segmenting your list, recipients may be receiving content or offers that are not matched to their preferences or for which they are not eligible
  
  
• Unintentional unsubscribes
  When a recipient forwards their email to another person, the links for the original recipient remain in the email, which could lead to the unintentional removal (or profile change if there is a subscription management link in the email) of the original recipient if one of the forwardees accidentally or intentionally clicks on the unsubscribe link
  
  
• Broken templates
  While using the forward function of an email application is fine for sending primarily text correspondence, it can wreak havoc with the design and layout of commercial HTML email, which doesn't present your message or your brand in the best light

What marketers want is the second option--an easy way for their recipients to initiate a new message to be sent to people they know that will increase the opportunity that the new recipient will either sign up to receive future communications or make a purchase on a website. This is commonly referred to as Forward to a Friend (FTAF). The StrongMail Transactional Server can be used to facilitate FTAF capabilities in concert with a standard mailing sent via either StrongMail Server or Message Studio. Here's a high level view of how it would work:

1. Set up a standard mailing in Message Studio or StrongMail Server
2. Set up a mailing on the StrongMail Transactional Server with the same template/header (or a different one if you want to send a separate mail to FTAF recipients) 
3. Create the following web pages and host them on a web server:
   1. FTAF landing page with form elements to collect information on who to forward the email to
   2. Confirmation page to notify the sender that their FTAF email was successfully sent
   3. Error page to notify the sender that there was a problem with sending the FTAF email 
4. Configure the form on FTAF landing page to send an API call to the Transactional Server to send the transactional mailing to the recipient(s) indicated in the form
5. Place a link in the standard mailing template that takes recipients to the FTAF landing page
   

In addition to the standard setup described above, there are a number of variables that you could modify to enhance how the FTAF works:

• Control the number of FTAF recipients permitted from a single FTAF request to reduce abuse and spam complaints
  
• Determine whether the same FTAF landing page could be used for multiple mailings (reduces the effort required to execute FTAF mailings)
  
• Design the FTAF landing page and the forwarded email to permit the original recipient to include a comment to the FTAF recipient
  
• Decide whether the FTAF recipient receives an identical or modified version of the email
  

There are many ways to configure FTAF using the StrongMail Transactional Server. Identify what you want to accomplish with your FTAF program and then choose the option that best suits your needs.