Your application needs to implement a mechanism to ask users for their preferences in relation to receiving in-app messages and save these settings in a configuration file. Based on these preferences there are several ways to control the delivery of ReachOut campaigns.
Option 1
If your preferences include an on / off switch only, you may use this setting to enable or disable automatic ReachOut campaign delivery when your application calls ruiCreateConfig() or ruiSync(). This means that once the user opts out of receiving in-app messages, the Usage Intelligence SDK will not check for available ReachOut campaigns with the server. This option is suitable if you never want campaigns to be delivered to opted out users and their preference cannot be overridden.
Option 2
You may choose to save the user’s preference as a Usage Intelligence custom property by calling ruiSetCustomProperty(). In this case your application will continue to check for ReachOut campaigns with the server, however when building your campaigns you must add filtering criteria based on this custom property. This option allows you to have more control on the delivery of ReachOut messages and has the following benefits:
- You are not limited to an on / off switch but can provide further options such as choosing to opt in for marketing messages, product updates and company announcements. Therefore if a user selects product updates only, then you would only send them messages related to the product and not marketing material or company announcements.
- You may still send ReachOut messages to all users, such as in case of an emergency release due to a serious bug fix where you want to notify all your users regardless of their opt in preferences.
- You will be able to report on your users’ preferences through the Usage Intelligence Dashboard.
More information about custom properties can be found in What Type of Data Can I Store in Custom Properties?
NOTE: A user may opt out from being tracked completely, in which case it is recommended that your application calls ruiOptOut() to disable all tracking and communication with the server. You will also not get any usage data for such clients.
Related Articles
Can Users Opt Out of Reach Out Campaigns? 3Number of Views What Happens to ReachOut Messages if a User Is Offline? 3Number of Views How Can I Test ReachOut Messages? 3Number of Views How Quickly Will a User See a ReachOut Message? 3Number of Views Can I Collect Opt-Ins via a ReachOut Campaign or Is That Hardcoded? 3Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago