Experience is a MOCA term and in short, experiences are what the end user sees, how they see it, where they see it and when they see it. It's what you wish the user to Experience.
Experiences are an integral part of Automation Campaigns: you can choose if this experience will be triggered by in-app behavior, or a geofence, or a beacon placed anywhere in the real world. You'll choose if you want a small message, a rich in-app HTML or a completely custom action for your app.
Creating your first Experience
This example follows the creation via our MOCA Console and starts off after the campaign is created.
To reach this screen please follow these steps:
- Log into the MOCA Console.
- Go to your App.
- Go to Campaigns and create a new Automation Campaign.
- Now create a new Experience.
You'll reach this screen:
Experience actions are the ways the MOCA SDK enabled applications have to deliver content to the user's device. These trigger when the campaign and experience conditions meet the requirements (e.g. enter defined Place or browse to the defined in-app Screen).
This action is the most simple form of communication. It sends a notification containing text and emojis.
- Write Message - Write a local push notification message for this action. This text will also be seen as the notification alert text. If your app is in background when it's received, when the notification is tapped it'll automatically open your app.
URL sends a URL to the targeted segment.
- Add URL - Field to add the URL that will be sent to the users.
- Background alert - Set the notification alert text. By clicking the notification, the user will open the app and be directed to the URL.
HTML sends HTML5 code to the targeted segment.
- Add HTML code - HTML code to be delivered to the users.
- Background alert - Set the notification alert text. By clicking the notification, the user will open the app and see the HTML. Keep it fresh and enticing to drive that CTR up!
IN-APP sends HTML5 code to the targeted segment for it to be displayed as an in-app notification.
- Add HTML code - HTML code to be delivered to the users when this experience is triggered.
When the event is launched the system will tag your users with the selected tag.
- Select Tag - Select an already existing tag from the Tags section.
- Tag Action Value - Mathematical expression that applies to that tag once it's triggered. Accepts +, - and =. Examples: "+1", "-2", "=3". It's an ideal mechanism to count users (e.g. tag users with certain segment close to a specific Beacon) or manage their state (e.g. set to 1 if user enters geofence, and 0 if user leaves geofence).
This advanced automation feature is launched when the conditions are met, and allows for the ultimate Experience.
- Custom action - When the experience is triggered, the text added into the Custom Action box will execute within your App: this allows you for the ultimate customization, and is great in gamification use cases. More about custom actions can be found in the developer documentation.
Each content above mentioned can be triggered either by Proximity events (when a user enters, exits or dwells in Geofences or Beacons) or via Event Triggers (when a user generates a specific event within the app). Please review each support article for an in-depth description.
Once you have set the content and the trigger, you can set a key business rule: cool downs. A MOCA Cool Down is defined as a time frame in which we assure you that the Experience will not trigger again, no matter if the user meets the requirements to receive the Experience. This is the key component to control how much you impact your audience.