When are Emails Sent?
The successful sending of a campaign email for a Prefinery project relies on all of the following factors:
Email Message Settings
When creating or editing a campaign email, under the Settings tab you can setup a trigger, delivery delay and delivery conditions for that particular email message.
These can affect how your email is sent:
Trigger - A trigger can be an action taken by you (e.g. imported, invited, activated or rejected a user) or by a user (e.g. applies or signs up, refers a friend). The action taken must correspond to what is set as the trigger as part of the condition for the email to be sent.
Delivery Delay - Adding a delivery delay allows the email to be sent after a specified delay. There is no delay set by default, but other factors still apply.
Delivery Conditions (Optional) - These conditions must all be true for the email to be sent (as long as other factors allows it). One or more conditions can be set.
Here's the list of currently supported triggers for reference:
Note: This table includes all possible triggers, so you may not see all these options in your account, depending on the type of project, and whether double opt-in is enabled or disabled, among other things.
|Trigger||Event Description||Who receives the email|
|is imported|| You import a new user (user enters the
||The user who is being imported|
|applies (opt-in confirmation requested)|| With double opt-in enabled only, a new user signs up to the project pending opt-in confirmation (user enters the
||With double opt-in enabled only, the user who signed up to the project|
|applies (opt-in confirmation completed)|| With double opt-in enabled only, an existing
|| With double opt-in enabled only, the
|applies||With double opt-in disabled only, a new user signs up without having to confirm opt-in, or if imported has followed the confirmation link in your import opt-in email||With double opt-in disabled only, the user who signed up to the project or has confirmed being imported|
|refers a friend||Someone applies (opt-in confirmation completed) after having clicked an existing user’s viral referral link||The user whose viral referral link was clicked (referrer)|
|is rejected|| You reject a user, taking them off the waitlist (user enters the
||The user who is being rejected|
|is invited|| In a pre-launch type project only, you invite the waitlisted user to use your app/service/beta, taking them off the waitlist (user status changes from
||The user who is being invited|
|is activated|| In a pre-launch type project only, user is activated, indicating they've accepted the invitation and/or being active (User status changes from
||The user who is being activated|
|is idled|| In a pre-launch type project only, a user becomes inactive (User status changes from
||The user who is being idled|
|is invited by a friend|| In a pre-launch type project only and with invite-a-friend enabled, an existing
||The friend who is being invited by the user (invitee)|
|invites a friend|| In a pre-launch type project only and with invite-a-friend enabled, an existing
||The user who sends the invitation (inviter)|
When the Trigger occurs, as long as there's no issue with the other factors mentioned here, the email is added to the delivery queue with the specified Delivery Delay unless there is no delay set in which case the email is queued immediately. For example, if you have set a delay of "3 days" then the email is added to the queue to be sent in three days.
Now, what happens when the delay elapses? Just prior to actually sending the email Delivery Conditions get evaluated. If all the conditions are met and there's no issue with other factors, the email is sent. If not, the email is thrown away and not sent.
Can I edit an email that's queued for sending already?
When an email is sent, we send the email message as it appears at that time of sending. So, even if an email is triggered (e.g. a reminder email to share the referral link 3 days after signup), queued for delivery, and sits in the queue for 3 days, then after the 3 days has elapsed is finally sent, we send the email message as it stands at that point of sending (not at the time it was queued).
This all means that, yes, you would be able to edit the email message at any time within those 3 days and the changes will reflect by the time the email is sent.
Some exceptions though:
- If you're looking to change delivery delays, if the email is already in the queue, a change to the delivery delay would only apply to triggers in the future, but not the past. It's not possible to change the delay of an email that's already sitting in queue for sending.
- A change in the delivery condition could cause the email sitting in queue not to be sent since we evaluate those conditions after the delivery delay elapses. You can use this behavior to change who the email should be sent to in particular. For example, if initially the queued emails were to be sent to all users that has signed up, you can change the condition so that it is only sent to those with custom variable X. Then, by the time the delivery delay has elapsed, we evaluate the latest conditions you've set and send the email to the user if they fit those conditions. If not, the email is discarded.
Email Message Status
Prior to sending the email, considering message settings and factors allows the email to be sent, the message is also checked whether it is Active or Inactive. If Inactive or paused, the email is thrown away.
Newly created email messages are set to Inactive by default until you activate them. Make sure that the message is Active if you intend it to be sent by clicking on the blue Action dropdown button for that particular message and selecting Activate.
Sender Address Status
Before a campaign email can be sent, make sure that you've already verified your email address and domain. If you're getting a warning on your email message like the one below, it means you'll need to sort out the address verification issue first.
Verifying your domain will ensure that your sent email arrives in your users' inboxes. Additionally, emails signed by your own domain will look as if they've been sent directly from you, rather than delivered by prefinery.com.
Plan Subscription Status
If you are already on any of our paid plans, then you will have no issue here.
But if you are currently on the free plan, you can send up to 500 total emails, and once you've reach the limit, email delivery is automatically disabled and any queued emails are stopped. You'll also get the following notification in your dashboard:
To reenable email delivery, you will need to subscribe to any of our paid plans which will allow you to send an unlimited number of emails and also unlock additional features and significantly increased maximum number of managed users/subscribers.