Display Triggers

In the Behavior step of the In-App Automation Workflow, you must choose what will trigger your message to display in your app. Each trigger is detailed here.

Triggers

After making your initial trigger selection, you have the option to set additional triggers. Click the Add Another button, select a trigger, and continue with your specifications. Multiple triggers are handled as a Boolean OR.

Click the X at the end of any trigger row to remove it.

App Open

Display the message based on the number of times the user opens the app. Enter a number.

Note

App Open display timing varies depending on whether or not:

  1. The user has opened the app before.
  2. The app is currently open.

For a message with App Open value of 1:

  • If a user has never opened the app before, they will see the message the first time they open the app.

  • If a user has opened the app before and does not currently have the app open, they will see the message the next time they open the app.

  • If a user currently has the app open, the message will display during that session.
Tip

If you are configuring a "Welcome" message intended to display only the first time the app is opened:

For an onboarding message that should appear the third time the user opens the app, set the App Open display trigger value to 3.

Custom Event

Custom Event displays the message based on the number of times a specified event occurs.

Note

Custom events are used to capture key events in your app, e.g., screen views, media views, stories read, button clicks, items purchased or added to cart. Custom events are generated with a snippet of code, or routed en masse via an SDK connector to Google Analytics or mParticle.

  1. Type ahead to search custom events that occurred within the last 30 days, then click to select from the listed results. If there are no results for your searched term, click the Use [search term] button to use the event name as typed.

    If you would like to set multiple Custom Event display triggers, click the Add Another button and continue with your specifications. Multiple events are handled as a Boolean OR.

    Click the X at the end of any event row to remove it.

  2. Enter the number of times the event must occur before the message will display.

Filter

Optionally filter your custom event by a numeric value associated with the event, or by key/value properties attached to the event.

Example
You may have a custom event named “Purchase”, with a numeric value representing the dollar amount of the purchase 125.0, as well as key/value pairs for a product SKU 1359DUKS and a purchase category fedoras. Click on our properties/value button to add these criteria, potentially to target users spending more than $100 on fedoras.
  1. Click the + PROPERTIES/VALUES button.
  2. Click the Add Property or Add Value button.If you would like to set multiple filters, click the Add Property or Add Value button again and continue with your specifications. Click the X at the end of any additional row to remove it.

  3. Choose from the dropdown menu and complete the filter.
    • Enter a numeric value for:

      • Greater than
      • Greater than or equal to
      • Equals (value)
      • Less than or equal to
      • Less than
    • Property options only:

      • Equals (string): Enter an alphanumeric value.
      • Is: Select from true or false.
      • Contains: Enter an alphanumeric value.
  4. Optionally add an alternative by clicking the plus sign icon at the end of a row.
  5. Use the ALL/ANY dropdown menu to choose what criteria must be met.
    • ALL = all criteria must be met (Boolean AND)
    • ANY = any criteria must be met (Boolean OR)
      Note

      If set to ALL, filters with alternatives use a Boolean OR operator. If set to ANY, filters with alternatives use a Boolean AND operator.

  6. Click the Save button, or Cancel to discard.

Screenview

Screenview displays the message based on the number of times a specified screen is viewed. The app screen must be configured before it will be available in the search menu. See: Settings: Configuration: App Screens.

  1. Click the Add a screen name button, enter the screen's complete or partial unique ID, then click to select from the listed results.
    If you would like to specify multiple screens, click the Add another screen name button and continue with your specifications. Multiple screens are handled as a Boolean OR.
    Click the X at the end of any screen name row to remove it.

  2. Enter the number of times the screen must be viewed before the message will display.

App Update

Display the message based on the number of times the user opens the app after an App Update.

Select the radio button for either All app updates or Specific app updates, then enter the number of app opens.

For Specific app updates, either target a single version number or a range of versions. For each platform, select any version, is equal to, is between, is greater than or equal to, or is less than or equal to from the dropdown menu, then enter the version number(s). For Android apps, enter the versionCode. If you don't know this value, you can find it in your Google Play dashboard.

Note

Is between includes boundary values, i.e., entering versions 4.3 - 5.1 includes 4.3 and 5.1.

Note

An App Version number is required when you deploy to Apple’s App Store or the Google Play Store. Because this number often varies by platform, we provide two fields, allowing you to target a different version number on each platform.

Conditions

Additional conditions appear below the Display Trigger dropdown menu. Optionally specify that the message will be displayed only if these conditions are met.

Screenview

Display the message only if the user is currently viewing a specified screen. The app screen must be configured before it will be available in the search menu. See: Settings: Configuration: App Screens.

  1. Enable via toggle.

  2. Click the Add a screen name button, enter the screen's complete or partial unique ID, then click to select from the listed results.

If you would like to specify multiple screens, click the Add another screen name button and continue with your specifications. Multiple screens are handled as a Boolean OR.

Click the X at the end of any screen name row to remove it.

Tip

Use Case

You may not want to interrupt a user’s purchase flow when they qualify for a special offer, e.g., via a Custom Event trigger on a “purchase”, but instead wait until they navigate back to the app's home screen before displaying the message.

Elapsed Time

Display the message only if a specified amount of time has elapsed since the display trigger event(s) occurred.

Enable via toggle, then enter the minimum number of seconds or minutes that must elapse before a message becomes eligible for display.