Automation

Automation is a set of conditions that your audience must meet before they receive a message.

Automation is initiated by a trigger, such as a tag change, entering or exiting a location, or inactivity. You can further refine your audience with Cancellation EventsEvents that prevent an automation from sending a message if a custom event occurs while the automation is in a delay period. and ConditionsTags that must or must not be present on a device (or channel_id) for members of your audience to receive a message from an automation or journey. The message is not sent if your conditions are not met. .

It may be helpful to think of automation as an order form for messages, or even a fulfillment of messages — once the conditions are set, Airship looks for the triggers that you define and delivers the messages according to the rules you put in place.

There are many uses for automation:

  • Schedule a specific message to be sent to users who are predicted to delete your app, and a different message to your most loyal users.
  • Send a “How was your visit?” message 24 hours after a mobile device enters a defined location.
  • Send a Thank You message when a user opts in to web notifications in their browser.
  • Send a web push notification to users who haven’t visited your website for five days.

You can set up automation in the dashboard or the API. Automation supports all channels and message types.

See also: Configure Triggers.

Message Frequency Limits

Automation limits cap the number of automated messages a named user can receive within a time frame, preventing you from over-messaging your audience. Each automation and message in a journey counts toward the automation limit. Automation limits are set at the project level.

Rule limits cap the number of messages a named user can receive from an automation within a time frame, preventing you from over-messaging your audience. Rule limits are set per automation and apply at the named user level.

 Note

Automation and journey limits determine the total number of messages you can send. They do not determine the total number of active journeys and automations your project supports. The total number of active automations you have appear under Messages » Messages Overview » Ongoing.

Custom Event Automation and Templates

You can trigger automation based on Custom EventsEvents that indicate that a user performed a predefined action, such as adding an item to a shopping cart, viewing a screen, or clicking an Unsubscribe button. Custom events can trigger automation and journeys. You can code them into your app or website, or send them to Airship from an external source using the custom event API. Custom events contain properties that you can use to personalize messages. . When you set up automation using the Custom Event trigger, you can reference event properties in your message using Airship’s Dynamic ContentVariable message content using handlebar syntax that you populate at send time. Use dynamic content to personalize messages for each member of your audience. syntax.

For example, if you have a custom event representing a purchase, you can send an automated message confirming the purchase and providing information about what the user bought.

Custom Event

{
   "occurred": "{{event_time}}",
   "user": {
      "named_user_id": "user"
   },
   "body": {
        "name": "purchase",
        "subscribe": true,
        "properties": {
            "customer_name": "user",
            "total": 48,
            "cost_units": "USD",
            "purchase": [
                {
                    "qty": 4,
                    "item": "MLB regulation baseball",
                    "per": "$12",
                    "total": "$48"
                }
            ]
        }
    }
}

Message Content

Hi {{$def customer_name "valued customer"}}!

Thanks for your purchase of:
{{#each purchased}}
{{qty}}x  {{per}}  {{item}} = {{this.total}}
{{/each}}
total: ${{total}}

Is being processed. We'll message you again when it ships!