As a first you’ll need to install our SDK in your mobile app. You can find detailed installation methods directly in the Github code repositories.<\/p>\n\n\n\n
Each repositories also include a sample application showing you how to load and initialize the client. <\/p>\n\n\n\n
Right after loading the SDK, you’ll need to initialize the client by providing your Refiner environment ID. You can find the ID under “Settings > Mobile SDK” in the Refiner dashboard.<\/p>\n\n\n\n
You can also activate a debug mode during development. When activated, all communication with our backend server is getting logged.<\/p>\n\n\n\n
All Mobile SDKs provide the same set of methods which you can use to identify users, track user behaviour, or launch surveys ad-hoc. <\/p>\n\n\n\n
Below we explain what each method does and how you can use it. Please consult the SKD specific documentation for the syntax and code examples.<\/p>\n\n\n\n
All users of your app need to be identified with a unique identifier using the “Identify User” method.<\/p>\n\n\n\n
If possible, we recommend to identify your users with an ID that you are also using in other tools (your user database, email marketing tools, etc.). You can also choose to identify users with their device ID if your app doesn’t require users to sign in.<\/p>\n\n\n\n
Next to a unique identifier, you can also provide additional user traits. The provided user traits can be used to segment users in your Refiner account and create custom target audiences for your surveys. You can also use our API to provide the same user traits through a backend integration.<\/p>\n\n\n\n
Refiner has a couple of reserved fields<\/a> you should be aware of. These fields can’t be overwritten or have a certain behaviour attached to them.<\/p>\n\n\n\n You can find examples on how to identify your users for each SDK version here:<\/p>\n\n\n\n When a user logs out from your app or changes user accounts, you can call the “Reset User” method.<\/p>\n\n\n\n If you are using our multi-language surveys feature, you can provide a “locale” string to show surveys in a specific language.<\/p>\n\n\n\n Lastly, you can provide a Identity Verification<\/a> signature for increased level of security in a production environment.<\/p>\n<\/div><\/div>\n\n\n\n The start time of the current user session can be used as the reference time in the Time Delay<\/a> and Tracked Event<\/a> survey trigger.<\/p>\n\n\n\n We try to automatically detect when a user starts a new session in your application. A new user session is detected when a user returns to your app after at least one hour of inactivity. <\/p>\n\n\n\n You can choose inform Refiner that a new session started with the startSession<\/em> method as shown below. You can call this method for example right after a user logs in to your application.<\/p>\n\n\n\n You can track whenever a user performs an important key action in your app (log-in, purchase, …). User event tracking<\/a> can be used to created User Segments<\/a> and Target Audiences<\/a> in Refiner.<\/p>\n\n\n\n Whenever your user navigates to a specific screen in your app, you can use the “Track Screen” method to surface that information to Refiner. <\/p>\n\n\n\n Tracking screens will allow you to launch surveys in specific areas in your app. In the Refiner dashboard, you can create a set of screen rules for each survey which determines on which screens a survey should be launched.<\/p>\n\n\n\n You can choose screen names freely and you don’t need to systematically track each screen. We recommend to track screens on which you might want to show a survey one day.<\/p>\n\n\n\n Next to providing user traits, it is also possible to attach contextual data to survey responses using the “addToResponse” method.<\/p>\n\n\n\n Please note that common information like the the current screen a user is on, their language, etc. can also be attached to survey responses using our built-in metadata collection<\/a> option.<\/p>\n\n\n\n Depending on your setup, you might want to initiate regular checks for surveys that are scheduled for the current user. For example when you are using time based trigger events<\/a>, when using our Follow-Up Mode<\/a>, or when a target audience is based on user data received by our backend API.<\/p>\n\n\n\n The ping<\/em> method provides an easy way to perform such checks. You can call the Ping method at key moments in a user’s journey, such as when the app is re-opened, or when the user performs a specific action.<\/p>\n\n\n\n Sometimes you might want to show a survey programmatically, directly from your application\u2019s code, instead of relying on targeting rules defined in the Refiner dashboard. The mobile SDK exposes a “Show Form” method that allows you to do exactly this.<\/p>\n\n\n\n Please make sure that your survey is using the “Manual” trigger event in “Targeting” section of the survey editor.<\/p>\n\n\n\n The “Set User” method acts as an alternative to the “Identify User” method described above.<\/p>\n\n\n\n In contrast to the Identify User<\/em> method, the Set User<\/em> method does not immediately create a user object in your Refiner account. The provided user Id and traits are kept locally in your app and no data is communicated to our servers at first. Only when the user performs a meaningful action in your app (e.g. Track Event<\/em> or Track Screen<\/em> is executed) will a user object be created in Refiner. Provided user traits will be attached to the user object when a survey is shown.<\/p>\n\n\n\n The purpose of this alternative method is provide a way to identify users locally when the SDK is initialised but keep the number of tracked users in your Refiner account to a minimum.<\/p>\n\n\n\n You can instruct the SDK to stop querying our servers and prevent any surveys from being displayed.<\/p>\n\n\n\n This method allows you to dynamically change the Refiner environment<\/a> of your app during runtime. <\/p>\n\n\n\n Registering callback functions allows you to execute code at specific moments in the lifecycle of a survey. Our SDK let you register the following callbacks:<\/p>\n\n\n\n\n
Start session<\/h3>\n\n\n\n
\n
Track event<\/h3>\n\n\n\n
\n
Track screen<\/h3>\n\n\n\n
\n
Advanced options<\/h2>\n\n\n\n
Add data to response<\/h3>\n\n\n\n
\n
Ping server<\/h3>\n\n\n\n
\n
Show survey programmatically<\/h3>\n\n\n\n
\n
Deferred user identification<\/h3>\n\n\n\n
\n
Disable & enable client<\/h3>\n\n\n\n
\n
Change environment ID<\/h3>\n\n\n\n
\n
Callback methods<\/h3>\n\n\n\n