Company Blog Support
Frank Hagan
posted

Contents

    Back to Top

    Campaign Builder Actions

     

     

     

    About

    Action elements do something with your Contact. The following Action elements are available:

    • Add to Campaign
    • Add to Sequence (Legacy feature)
    • Update Contact (any editable field)
    • Change Tags
    • Send Email
    • Send SMS
    • Send to Fulfillment
    • Assign Task
    • Send Postcard
    • Give WordPress membership access
    • Remove WordPress membership access
    • Add to Facebook Custom Audience
    • Cancel open orders
    • Recharge transactions
    • Add product to purchase history
    • Add to lead router
    • Notify Someone with SMS
    • Notify Someone with Email
    • Webhook

    Actions available to Campaigns

    Add to Sequence and Add to Campaign Actions

    Actions happen immediately when the Contact reaches them, and the Contact progresses to the next Campaign element automatically in most cases. Two Action Elements have special timing considerations, the Add to Sequence and Add to Campaign elements.

    The Add to Sequence Action sends the Contact to the Sequence and waits until the Contact returns to continue on the Campaign. If the Contact never returns then they never progress past the Add to Sequence element. 

    Step Sequences: For legacy ONTRAPORT accounts, you must configure Step Sequences to  "Unsubscribe contact after last step":

    1. In the Step Sequence editor, click the Settings button 

      Step Sequence settings

    2. Check the checkbox next to "Unsubscribe contact after last step"

      check the unsubscribe after last step checkbox

    3. If you want to keep the Contact on the Step Sequence indefinitely, use a Fork element in the Campaign to send the Contact to the Step Sequence and continue on the Campaign at the same time.

    Date Sequences: Add a Rule Step to unsubscribe the Contact from that specific sequence after the last scheduled step in the Date Sequence. If the Date Sequence is an evergreen sequence that runs the date steps every year, they will stay on the Date Sequence indefinitely and never progress. Use a Fork element to send the Contacts to the Date Sequence and simultaneously have them continue on the Campaign Map. 

    use a Fork filter prior to the Sequence element to avoid timing issues with Date Sequences

    The Add to Campaign element will also wait until the Contact returns from the other Campaign. The Contact will have to reach an End or a End with Exit element before returning and progressing on the Campaign Map. If this is not the desired outcome, use a Fork element before the Add to Campaign element as explained above.

    Filtering Action Elements 

    Other Action elements are very straight forward, and act on any Contact who reaches the Action element. To apply an Action to only a portion of your Contacts on the Campaign Map use Filter Elements prior to the Action.

    To make everyone Wait before the Action: Use a Wait filter just before the Action. 

    wait filters make the Contact wait for a specified number of days and hours

    Note: Each day is a full 24 hours. If the Contact reaches the Wait element at 10:30 AM, and the Wait is configured to "Wait 1 day and then wait until 10 AM" the Wait will pause the Contact for a full 24 hours, until 10:30 AM the next day, and then wait until 10 AM is next seen (the following day). 

    To Split Test an Action: Use a Split element just before the Action. On each leg of the Split, insert the Action you want to test. You can configure the Split to send equal or unequal percentages down the legs of the Split (50/50, 60/40, 80/20, etc.), insert Wait elements in each leg (or just one), etc. 

    a Split divides up the Contacts into two paths in the campaign

    Conditional Action While Continuing On in the Campaign: In cases where you want to have an Action conditioned on some other achievement but still have the Contact progress through the rest of the Campaign, use a Fork. The Contacts all go down both legs of a Fork, so you can have them branch off to wait for an event using a Goal while continuing on in the main Campaign. A Fork is especially helpful if you use a Add to Sequence or Add to Campaign element (see the Add to Sequence and Add to Campaign Actions section above). 

    a fork sends the contact down both paths

    Use a Condition to Separate the Contacts Prior to the Action: To segment the Contacts based on any condition prior to applying the Action element to them, you can also use a Condition.

    a condition splits the Contacts based on a yes/no equation

    EndAdding an End stops the contact on that path. You can optionally have the End element also remove the Contact from the Campaign Map Path they are on (shown as an "Exit" End). Note this action will NOT remove the contact from all paths on the Campaign Map, and only removes them from that individual path.

    the End - Exit element on a Campaign Builder Map

     

     

     

    Articles in this section

    Have more questions? Submit a request

    Comments

    Powered by Zendesk