As a marketer, you're always looking for proven ways to increase customer retention and brand loyalty. If you have a mobile app, integrate it with Acoustic Campaign so you can easily engage and reward anyone who uses your app. Take a look at these use cases to get you started:
- Send a mobile message when you want to notify your app users of a sale or a new product launch
- Set up a mobile campaign to push details to your contact's device for a conference, event, or other location of interests
- Use your mobile push notifications to get mobile app users to opt-in to another campaign
- Send your app users a coupon for a restaurant near an event location
Put it to use
With a mobile campaign, you can deliver personalized, interactive mobile app messages. You can include images, video, webpage and call links, and sounds. You can even target your users with messages based on when they are near a location of interest. If you simply need to update background data in your app, you can do so without your app users knowing about it. Check out these use cases.
Types of mobile messages
Let's look at the different types of mobile app push notifications and messages:
- Want to capture the app user's attention? You can use permission-based push notifications to get the mobile app user's attention when they're not active in your app.
- Are you interested in reaching your user's inbox? Mobile app inbox-only messages reach your entire app audience and provide users with the convenience to store messages for later use. Use them to deliver rich, full-page content inside of your app that can be stored within an inbox for a specified amount of time.
- Want to leverage user actions and behaviors? When you send an in-app message, users will see it when they are actively using the mobile app.
- Do you want to quietly update your app? Data-only notifications update background data in the app. The data payload is sent to the device but is not shown to the user.
- Why not deliver a push notification with inbox action to a mobile device? When the user slides the notification, the mobile app's inbox opens on their device.
Mobile user roles
In most Acoustic Campaign organizations, there are different user roles that help set up, create, and send mobile app messages and notifications. These user roles are typically the organization administrator, developer, and marketer.
User permissions must be set up before users can work with mobile app messages and Device Location Awareness (DLA).
- Builds the mobile app, including any customization for Universal Behavior (UB) events in the app
- Connects the Push Notification SDKs
- Registers the mobile app
- Configures the app by providing the Apple Push Notification Service (APNS), and Firebase Cloud Messaging (FCM) keys
- Defines and configures the app groups and any custom actions or action categories
- Configures the Inbox, In-app, Data and extensions, and Simple templates
- Creates mobile app messages
- Creates HTML content blocks for certain mobile app messages
How it works
To get mobile app messages working in Acoustic Campaign, you'll need your mobile app developer to:
- Integrate the Acoustic Mobile SDK into your company's app
- Register the app
- Configure the app in Campaign's mobile app development area.
Next, your Acoustic Campaign organization administrator will need to set up user permissions. Then you or your company's technical marketer can create and enable the mobile database that will store contact data. Finally, you're ready to use the mobile message composer to create and send messages.
You can select the audience that you want to send messages to by querying specific customers based on their profile data, behavioral data, and previous mobile interactions. After you send the mobile message, sit back and measure the effectiveness of your messages using Performance Insights where you'll see customizable reports that track user engagement.
Acoustic Campaign's CRM integrations were built around the email channel. As a result, the SMS or mobile app message channels are not productized with CRM and require customization to function properly. For more information, please contact your Client Service Manager.
Set it up
Important: Steps that include more than one task can occur at the same time.
|Mobile app messages are enabled for the organization.||Provisioning team|
|2||Build a mobile app.||Mobile app developer|
|3||Register the app:||Mobile app developer|
|4||Download the SDK:||Mobile app developer|
|5||Set up the mobile app in Acoustic Campaign:||Acoustic Campaign org admin|
|6||Implement the SDK within the app:||Mobile app developer|
|7||Test the implementation:||Mobile app developer|
|8||Customize the app using advanced options (Optional).
Include the custom Universal Behavior (UB) events in the app:
|Mobile app developer|
|9||Set up the mobile app in Acoustic Campaign.
The mobile app developer adds each mobile app to Apps in Acoustic Campaign and sets up mobile push app groups using the GCM Google API Key, APNS Certificate file and password, and Client Secret. Developers also must configure default and custom actions and message templates.
For more information about Mobile Push APIs, see APIs for Integrations.
|Mobile app developer|
Create, schedule, and send a mobile app message in Acoustic Campaign.
Important: Developers must implement actions and messages before marketers can create content.
The mobile marketer will make sure that a flexible database is configured for mobile messages, create and set up a mobile campaign, enter message details, and add settings to the mobile message. Then, the marketer will test, finalize, and schedule the message. Finally, the marketer will confirm the message details and send the message.
|Mobile app marketer|
Let's look at the most common tasks when working with mobile messages.
|How do I...||Go to|
Get access to Mobile app messages
|Organization administrator: Setting up mobile app user permissions
Note: This is an org admin task and setting.
Set up a mobile-enabled database
Create reports and view data
|Push notification reports|
Create a mobile push notification that shows in the mobile user's device
|Create and send a simple notification|
Create a mobile push notification that displays in the inbox of the mobile app
|Create and send a simple push notification with an inbox action|
Create a message that only displays in the inbox of the app, even if the mobile app user disabled push notifications
|Create and send an inbox-only message|
|Create a message that shows in the mobile app when it's opened||Create and send an in-app message|
|Update background data in the mobile app||Create and send a data-only notification|
|Track events based on mobile app user behavior||Finding Mobile Push Notification Data using Universal Behaviors|
|Identify users who receive (or opted to not receive) mobile messages and notifications||Understanding mobile app consent|