ForeSee Developer Portal

Everything you need to set up and optimize your ForeSee product. Home of developer documentation, implementation guides, and question/answer forums.

Blueprint

SDK Overview

The ForeSee® Mobile SDK ships as two AAR files that contain ForeSee’s mobile product: Trigger. The current version of the SDK supports Android 5.0+.

Trigger

The Trigger module allows clients to define loyalty criteria, which is the number of pages viewed to qualify, and track a user’s progress towards fulfillment. Once fulfilled, the user is automatically invited to participate in a satisfaction survey.

Instrumenting Your App

Once the client has incorporated the SDK into their app (see the Getting Started article) they are responsible for instrumenting the app. There are two main decisions the client needs to make:

  1. Defining the loyalty criteria - All configuration is done through the provided foresee_configuration.json file that added in Step 2 of Instrumenting your code section of the Getting Started article. Please consult the Configuration article for more information.

  2. Checking if the user has met the loyalty criteria - The Trigger module automatically tracks the users progress towards fulfilling the loyalty criteria, but the client must decide when to check if the user has become eligible for a survey. There is a single API method, ForeSee.checkIfEligibleForSurvey() that the client can call to check the user’s current eligibility status. If the user has fulfilled the loyalty criteria and is in the sampling pool, an invitation is presented. It is recommended to call ForeSee.checkIfEligibleForSurvey() when the app is launched and when the app is resumed.

Other Resources

  • Sample projects: These can be found on Github and provide examples of how to implement the SDK in a number of different scenarios.

  • API docs: These are included in the SDK, but also found here. These documents explain the various functions available within the app and how to use them.