MOCA enabled applications can implement Experiences as part of Proximity Campaigns. These experiences trigger when the device enters a delimited area in the physical world or performs an action within the application (like, subscribe, reach a checkout page and so on). These experiences range from a simple local push notification which serves as a message, rich HTML 5 content and even custom actions offered by your custom App.

In short, experiences are what the end user sees, how they see it, where they see it and when they see it.

Creating your first Experience

Experiences can be both configured via the UI of our MOCA Console or programmatically Every experience is part of an existing campaign. This example follows the creation via our MOCA Console and starts off after the campaign is created.

Click on Create New Experience and you will reach this screen:

Experience Actions

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).

MESSAGE

• Write Message - Write a local push notification message for this action. The content will also be shown to the user on lock screen, so keep it short and sweet (between 5 to 10 words is preferred).

URL

URL sends a URL to the targeted segment.

• Add URL - Field to add the URL that will be sent to the users. It can be a deep link within your application.
• Background alert - When the app is in background mode or closed, the background notification alert will be delivered instead. By clicking the notification, the user will open the app and be redirected to the URL.

HTML

HTML sends a full screen interstitial HTML5 to each user of the targeted segment.

• Add HTML code - HTML code to be delivered to the users. Supports JS, CSS and HTML5.
• Background alert - When the app is in background mode or closed, the background notification alert will be delivered instead. By clicking the notification, the user will open the app and see the HTML.

IN-APP

In-App sends an in-app pop up screen to each user of the targeted segment. This one has no push notification or similar, so no Background Alert is needed.

• Add HTML code - HTML code to be delivered to the users. Supports JS, CSS and HTML5.
  

TAG

• Select Tag - Select a predefined tag from the Tags section. Is null if no Tag was created.
• Tag Action Value - Mathematical expression to add to the tag per detection. Accepts +, - and =. Examples: "+1", "-2", "=3".
  

CLOUD ACTION

This on-demand feature enables MOCA SDK embedded into the client mobile App to deliver location-triggered actions directly to a third party campaigns module and deliver segmented and personalized content to end users.

• Select Cloud Action - Here you select the cloud hook API endpoint set for your account. 
  

CUSTOM

This advanced feature invokes the custom action callback you define in your code. It can be whatever you code it to be, and can be used for a variety of actions based on the proximity trigger (example: make the device vibrate for a gamification feature in the app).

• Custom action - When the experience is triggered, there will be a callback to the custom action you have indicated. More about custom actions can be found in the developer documentation.