Announcing the “Has been sent” Segment Condition

I am very pleased to announce the newest condition for our segment builder, the “has been sent” condition.

The segment builder is a floating feature that allows you to create super targeted segments of your contacts from multiple places in the platform.

The segment builder is used in many places throughout the platform. It’s used to create If/Else statements in automations, Goal conditions, contact and deal scoring, segmenting campaign lists, advanced search, and more. So, when segment conditions are added to the segment builder, it’s a big deal because it enhances the capabilities of many different features.

For more information about the Segment Builder, I suggest reading our education guide “Using the Segment Builder in ActiveCampaign.”

Master the Segment Builder

Starting today, you have a new very important condition that you can use anywhere you have access to the Segment Builder; the “Has been sent” condition.

This means that you can now segment contacts based on if they previously been sent a specific email, or any campaign at all. These emails can come from larger campaigns, or they can be one-off emails sent from an automation.

Has been sent is available to all plan levels, and is already live in your account.

Examples use cases:

Add a “heat score” warning to contacts, to prevent over-sending:

In this example, we are going to create a contact score, that increments everytime we send the contact a new message. We will let points expire every 3 days.

Whenever the contact receieves a new email campaign, either from a newsletter style campaign or within an automation, it will increase their “heat score” by 1 point.

This will allow us to exclude contacts from newsletter campaigns that have already received several messages this week, or create automations that “wait until” the heat score is safe enough to send again.

Setting this up is incredibly easy.

  • From your contacts tab, click on the down arrow and select “manage scoring.”
  • Click on Create a new score, and choose “Contact Score.”
  • Add a new score condition, and select “has been sent” as the condition
  • Choose “any campaign”
  • Add one point
  • Have points expire after 1 week.
  • Your score is now setup to record how many messages/week a contact has already received.

Protect coupon code abuse:

A common practice in ecommerce stores is to provide a coupon code for new users, to encourage them to opt-in to an email list. I utilize this practice with great success in my demo store.

I rotate these coupon codes each month to test the effectiveness, and to create a sense of urgency.

One thing I noticed though, was that users were claiming a coupon code, and then returning the following month in an incognito browser to get the new coupon code.

These are people that still show intent to purchase (Yay retention!), so I want to help drive that, but I don’t want to create an offer that cuts into my margin as much as their first purchase.

In this example, we want to prevent contacts from abusing the coupon code system, and we will do so by taking advantage of the “has been sent” segment condition.

  • Create a new automation that acts as an autoresponder to deliver the coupon code.
  • Include an If/Else condition “has been sent” that matches the coupon code email
  • If this is the contact’s first time receiving a code, send them the original offer.
  • If this is the contact’s second time through, send thank them for their loyalty, and send a less lucrative offer.

Seasonal Specials:

Many ecommerce companies will also run seasonal sales or campaigns promoting a specific type of product. For example in June, many [US] customers may want to run an “Independance Day Sale” promoting products that for the fourth of July.

With the new “has been sent” campaign, you can send an early campaign in mid-june, but create an automation for all new contacts that subscribe after the email has been sent.

Any new contacts that fill out any of the special offer forms during the month of June, will be entered into a new “Fourth of July” automation. Using an If/Else statement, check if they have been sent the Fourth of July campaign email.

If they have, proceed as normal. Otherwise, make sure to send them another email that matches the fourth of July email.

To prevent sending a campaign with information they’ve already seen, I can do a simple check on whether the contact received the feature announcement from the campaign.

This will also work well for SaaS companies that send new feature announcements, and include those features in follow-up automation emails.

 

Let us know in the comments how you plan on using this new segment condition.

A trial is worth a thousand words.
Get started today, no credit card required.