Use universal behaviors (UB) to capture information about all mobile app interactions between the Acoustic Campaign platform and mobile app users.
Before you begin
Before you create a universal behaviors event query to find mobile app data, you must complete these requirements:
- Create and register the mobile app and add it to Campaign.
- Organization must be push-enabled.
- User must be mobile app-enabled.
- Use a flexible database that is mobile app-enabled and has mobile app messages custom field.
Relationship between universal behaviors and SDKs
The iOS and Android SDKs send events to the MCE servers to indicate that certain actions related to your mobile app have happened. Some of these events get translated into universal behaviors (UB) that are sent to the servers.
These events are all treated the same within the MCE system and generate an API call that gives a metric or report. Events are not generated internally for sending push notifications because the server sends a large amount. When the MCE server is finished handling the event, it is passed to the Acoustic translation layer, which is a piece of the system that knows how to transform each event it receives into a universal behavior. The translation layer forwards it to Campaign through their APIs. Of all of the events that are received, only a well-defined subset is recognized and forwarded to Acoustic.
Create universal behavior event queries using mobile app criteria
You can build a query with mobile app interactions in Campaign's queries or programs to find mobile push data.
- Go to Data > Queries > Create.
- Select your push-enabled database, name your query, and then click OK.
- Click Behavior and select Universal behavior.
- Select one of the behaviors for your push contact(s).
- Click Done.
- Now you can build your criteria based on select attributes. Event types may have different attributes. See the individual event type for details.
Note: Not all events are enabled by default. More details are available under each event.
Location-based universal behavior events
The query filters contacts in the mobile app database. After creating a query, you can use this query anywhere queries are available in the Campaign, such as programs, mobile app messages, and emails.
All location event attributes are configured in the device location awareness (DLA) application. If an attribute was configured and does not display, the DLA service may be down and an error message may appear. By default, location dwell and exit events are disabled for all organizations. To enable these events for your organization, contact Support.
In Data, create a query and configure the settings as defined below:
- Choose database to query: Click Browse and select your mobile app-enabled database.
- Save query as: Name the query.
- Location: If you want, you can save the query in a shared folder so all users in your organization can access the query.
- Type: Select Query.
- Click OK to open the query builder.
Select the query's behavior criteria based on the Locations criteria, as defined below. After you create the query, click Save. You may also Save & calculate to determine the number of contacts in the database who meet the criteria or Save & close to close the criteria page.
- Hover over Behavior and click Universal behavior.
- Select Has if you want to include contacts who performed a behavior; otherwise, select Has not.
- In Choose universal behavior, click a location event.
- Configure the event type parameters based on the target attributes. You can click the plus (+) icon to add an unlimited amount of additional attribute criteria. You may add an attribute more than once (this creates an AND condition).
There are multiple operators for each attribute:
is equal to
– Select a value from the list or enter a value in the text field.contains
– Enter a value in the text field.contains one of the following
– Select more than one value from the list or enter a value in the text field.- Additional operators for the Radius attribute displays a text field where you can enter a value.
Note: Not all events are enabled by default. More details are available under each event.