Sending Groups

Sending Groups

Historically, until version 2.0, when you wanted to send a campaign to more than one list/segment, AppMail would merge the selected lists/segments into a new list and would then send the campaign to that new list.

Performance wise, this is a very bad idea, because you end up duplicating a lot of data.
This also means AppMail would have to search in a lot of data, which means slower application overall.

When we implemented this functionality, it was the only viable option given the requirements at that time.
However, once we started working on AppMail 2.0, we had enough time to do something about this problem, in a way that is also backward compatible, and our solution is called Sending Groups.

With the arrival of AppMail 2.0, when you create a campaign, you can add it into a Sending Group.
You can add multiple campaigns in a Sending Group, each campaign targeting a different list and/or segment.

When AppMail sends a campaign that is part of a Sending Group, for each email address that is targeted in the campaign, AppMail does a lookup to see if that email address received any other campaign that is part of the same Sending Group.
If it finds the email address during the lookup, then AppMail marks the campaign for that email address as sent and moves on.
If it does not find the email address during the lookup, then AppMail will send the campaign to that email address and then move on.

This allows for great flexibility with a minimum performance cost.

Not only you can send campaigns to as many lists and segments as needed without worrying that email addresses that are part of multiple lists will get duplicate campaigns, but you can also modify each copy of the campaign and change its attributes, like subject, content, etc, so you can test the inboxing rate.
Another benefit is that you can add a campaign into a sending group at any time, even weeks or months after your initial send out to a Sending Group.

The Sending Groups feature is very powerful and it can help you target subscribers in ways that was not possible in AppMail 1.x.
As with anything in AppMail, we advise using this feature only if you really need it and you are sure it is going to help.

    • Related Articles

    • Understanding how the sending quota and limits work

      This subject is always brought into our attention by our customers. Setting quota and limits can be done from Backend->Settings->Customers->Sending tab. These settings will apply to all customers registered into the system which are not assigned to a ...

    • What tracking and sending domains actually are?

      TRACKING DOMAINS: If you have AppMail installed on email.a.com and you send campaigns, all your URL links will start with https://email.a.com and this is fine for most of the cases, but what if you want to handle emailing for b.com domain? In this ...

    • Enable the use of temporary queue tables when sending campaigns

      The main issue we have with huge AppMail apps is that the campaign_delivery_log table becomes huge (I’ve seen installs with hundred GB’s of data in that table alone) and we use that table to join against when we send the campaigns so that we can see ...

    • My campaigns don’t send, they’re stuck in “Pending-Sending” status

      When this happens, most likely the cron jobs that must run in order to pick up the campaigns and send them are not running, and no, it’s not something wrong with the application, but you simply need to feed the application with the right data in ...

    • Timewarp

      Timewarp is a feature that schedules email campaigns based on each individual subscriber’s time zone, so subscribers receive your scheduled campaigns at the correct time for them. We use the subscriber IP address in order to detect the right user ...