Macro-throttling your email deliveries with HubSpot | Scribe

    Macro-throttling your email deliveries with HubSpot

    • Mike Donnelly |
    • 0 steps |
    • 3 minutes
    The first step is to create a workflow that starts on a specific date. You should select the date that you want your email to be sent.
    Click "Next"
    You'll then need to create your contact enrollment trigger. In this example, we're using a single "Active" list as the starting criteria.
    You'll then set the time that you want your email to start delivering to your recipients. In this example, we're selecting 10:00am based on our account's time zone setting.
    The date and time you select will also serve as the cut off point for any additional contacts who meet the starting criteria. For example, if a contact meets the starting criteria or is added to an "Active" list at 10:01am on the date selected, they will not be enrolled or sent an email. The easiest way to think about this is when you send a one-off / scheduled email in HubSpot, you have to select a time that you want your email to be sent and after that point, anyone who becomes part of the list(s) you selected will not be sent the email.
    Underneath the delay step, click on the "+" sign to add a workflow action step. Type "split test automation" in the search function inside your available workflow actions.
    Depending on how deeply you want to macro-throttle your email, you'll select either a two-way, three way or five way split. For example, you can throttle your email over two different hours selecting the two way split or up to five different hours selecting the five way split. We'd recommend using the five way split for throttling purposes as this will spread your email deliveries out further.
    Underneath the split test automation step, you'll then click on the "+" sign to add another workflow action step.
    First select "Value equals branch" to add this workflow action option and then click "Choose a property" to branch off then Click "2. Five cohort split test automation" and choose "cohort" as the branch option and then check the box to complete the branch. Click "Next" and then click "Save".
    You'll then select the "Send email" action and select the email you want to send.
    Underneath the "Cohort A" branch, click the "+" to add another workflow action step.
    Underneath "Cohort B", "Cohort C", Cohort D" and "Cohort E", you'll follow similar steps which are to click the "+" sign underneath each branch to add workflow actions steps. Select the "Delay" step first and choose a corresponding hour that is later than when the first email was sent. For example, the "Cohort A" will have it's emails delivered at 10:00am, so for Cohort B, we'll select 11:00am, for Cohort C, we'll select 12:00pm, for Cohort D, we'll select 1:00pm and for Cohort E, we'll select 2:00pm.
    You should never see contacts flowing down the "None met" branch as this means there was a network communication error between HubSpot and Seventh Sense. That said, if you want to take a belt and suspenders approach, you can always treat this as a default branch and point it to the "A cohort".
    Click the "+" sign underneath the "None met" branch to add an action step and select the "Go to other action" step. Point it at the "Send email" step underneath "Cohort A".
    For the remaining branches, you'll follow the same process. Underneath each delay in each branch, click the "+" sign to add another workflow action and select the "Go to other action" step and point it at the "Send email" step underneath the "Cohort A" branch.
    Click "Review and publish" in the top right to turn on the workflow. You'll want to also enroll contacts who meet the criteria when the workflow is turned on.
    If you want to macro-throttle additional email deliveries in the future, you can simply clone the workflow, update the date and time that you want the workflow to start delivering your email, update the email being sent and you'll be off to the races!
    This Scribe is in tip-top shape!Leave feedback if there are any issues with this Scribe