A great use of these events is to add subscribers who engage to a group, which you can later use to segment a subsequent mailing.

Ad insertion tags are:

• <$BlogItemMarqueeAd$>
• <$BlogItemBannerAd$>
• <$BlogItemRectangleAd$>

Specify these in a mailing to insert the relevant ad type. These work even when you have email ads disabled account-wide: ads will still be inserted.

Contrariwise, if you have ads enabled by default, the shortcode <$BlogNoAd$> turns them off if it’s in the mailing / template.

FeedBlitz’s mailing short codetags and personalization reference is documented here:

https://developer.feedblitz.com/docs/rest-api/api-reference/mailing-templates/ 

So I’m excited to announce the following changes to the RSS feed API:

• It tells you more! Including time stamps, etag and diagnostic data.
• Fetches may be filtered by a status parameter, so you can (for example) home in on feeds where the source is failing.
• Core elements may now be edited via the API via POST.
• DELETE is also supported for when a feed has reached the end of its useful lifetime.

But once you set keepalive to be on, things change. Instead, when the sequence completes, the subscriber stays on the funnel as if the funnel was a regular list. They won’t get any more entries (even if some are added later), but you can mail the list en masse and that will include everyone who’s finished the list as well as those active upon it. When keepalive is off (which is the default) a mass mailing will only include subscribers who are currently active within the sequence.

So setting keepalive on means you can mail subscribers on the funnel as if it were a list. So you can think of it as a funnel that’s also a list. Or a list that’s also a funnel.

A hybrid. A mashup of both. A frankenfunnel

An example use case is a new customer onboarding sequence. You might have the default sender be your support service, giving tips and advice. But at certain points in the sequence you want an executive to check in on the new customer. This capability allows you to change the sender information for that step, so that it seems to come from, say, the CEO instead of the customer service team. Simple and easy and effective, it means all your onboarding sequence can be set up in the same funnel, no matter from whom the email is nominally sent.

In addition, the core call to send an email has been extended to allow you to request delivery and / or read receipts (although you might not get them; sending these notifications is optional).