Automation Composer Tutorial

Automated Messages are messages that are automatically sent to users when certain conditions are met. Learn more in the Composer Overview.

What You’ll Do

In this tutorial, you will:

  1. Define who will receive your message and why.
  2. Choose which message type to send and enter its content.
  3. Direct the users’ next step after they tap or swipe the message.
  4. Decide how and when you want the message delivered.
  5. Preview and start the automation rule.

Features and options are explained along the way.

Steps

Choose your app from the Urban Airship dashboard, then click the Create button and select the Automation composer.


Setup

  1. Enter a descriptive Automation Name.
  2. Select an Event Trigger from the dropdown menu.

  3. Optionally modify which Platforms are included in your audience. All platforms configured for your app will be listed and are enabled by default, but you can toggle to limit your audience to specific platforms. You must select at least one.

  4. Set Event Trigger Options.
  5. Click Content in the header to move on.

Content

  1. Choose which message type to send, or choose Silent Push Notification to send a push without notification text. After you make your selection you have the option to combine message types, then click the Continue button to confirm your choice(s).

  2. Enter the text that will display in your message. A preview will display as you type.
  3. If you chose to combine a Push Notification and In-App Message, an In-App Message Text section appears below the message truncation indicator. By default, the In-App message’s alert text is the same as the Push Notification text. If you’d prefer to use a different message, select the radio button for Write alternative, and enter your text in the box that appears below.
  4. Select a Message Action from the dropdown menu.

    The Message Actions listed in the dropdown menu differ depending on which message type you chose and if you chose to combine message types. See:
    Message Actions: Availability.


  5. Optionally Set a tag.
  6. Set Optional Features.
  7. Click Delivery in the header to move on.

Delivery

  1. Optionally Delay message delivery. This specifies a waiting period after the trigger occurs and before the message is sent. Toggle to enable, then enter a value for your dropdown choice of Minutes, Hours, or Days. The maximum delay period is 90 days.

    Delay is required for First Open triggers, with a minimum delay of one hour to ensure delivery.


  2. Select delivery timing from the dropdown menu. Delivery will be after the trigger occurs and delay has elapsed. If you enable a delay, “after delay” is appended to each choice listed in the dropdown menu.

    • Send immediately: Your message will send as soon as the rule is evaluated, though after a delay, if specified.

    • Schedule: Choose an exact time of day to send the message. The system chooses the first appropriate scheduled time after the triggering event and after a configured delay period has elapsed. All messages are delivered in the device’s local time zone.

      Check the box per day of the week, or All days. Click and drag the circle on the timeline to select delivery time. Hours are in 15-minute divisions. If you would like to deliver the message at multiple hours of a day on multiple days of the week, click the Add Another button and continue with your specifications.

    • Send during available window: Configure message delivery windows by specifying valid hours of the day and days of the week. If no delay is configured and the triggering event falls within an available window, the message will be delivered immediately. If a delay is configured, the system evaluates for an available window the moment the delay period has elapsed.

      Check the box per day of the week, or All days. Click and drag the circle on the timeline to constrain the delivery window. Hours are in 15 minute divisions. If you would like to define multiple windows for delivery, e.g., to support separate hours during weekdays vs. weekends, click the Add Another button and continue with your specifications.

      If the triggering event (plus delay, if specified) falls outside of an available window, by default it will deliver the message during the next available window. You may choose to discard the message by selecting the radio button for Do not send.

      It may take a few minutes for Urban Airship to process which time zone a device is in upon first registration, and we default to not sending to devices whose time zone is unknown. Including a delay with a Schedule/“Send during available window” automation may help with this and is highly recommended for automations that are intended to be sent shortly after first app open.

  3. Set Optional Delivery Features.

  4. Click Review & Start in the header to move on.

Review & Start

  1. Review the information on the left side of the screen, and click through the images in the previewer. The platform and display type are dynamically updated above.
    If you would like to make changes, click the associated step in the progress header, make your changes, then return to Review & Start.

  2. Choose whether to create this Automated message as Active or Paused. Select Paused if you’d like to create the message but aren’t quite ready to activate it.
    Toggle to choose the desired Active/Paused state. After starting the rule, you may edit it at any time via the dropdown menu in the Status column in Messages » Messages Overview » Automated.

  3. Start your Automation rule! Click the Start Automation button at the bottom of the window.