Trigger - Repeat Days

Repeat days, in general, specifies how many days to wait to re-invite a user to participate in a survey. There are two options:

  1. repeatDaysAfterComplete: This defines the number of days after a user has completed a survey before they are eligible to be re-invited. The client can disable this feature by removing it from the foresee_configuration.json file.
  2. repeatDaysAfterDecline: This defines the number of days after a user has declined an invitation (or abandoned a survey) before they are eligible to be re-invited. Again, the client can disable this feature by removing it from the foresee_configuration.json file.
  3. repeatDaysAfterAccept: This defines the number of days after a user has received a local notification that the SDK will transition into the DECLINED state.

Once repeat days have elapsed, the state of the SDK will be reset (and tracking/recording will resume) the next time the app is started from scratch. Once the state is reset, the original criteria must be re-met before an invite is shown.

Other articles in this section:

  1. Trigger Overview
  2. Invite Modes
  3. Invitation API
  4. Page Views
  5. Repeat Days (current article)
  6. Sampling
  7. Multiple Measures
  8. CPP's
  9. Localization