Feedbackly
v.5.0.2
v.5.0.2
  • Getting started
  • REST API
    • Authentication
    • Responses
      • GET Responses
      • GET Response by id
    • Response chains
      • GET Response-chains
      • GET Response-chain by id
    • Questions
      • GET Questions
      • GET Question by id
    • Surveys
      • GET Surveys
      • GET Surveys by id
    • Touchpoints
      • GET Touchpoints
      • GET Touchpoint by id
    • Notes
      • Entity relationships
      • Pagination
      • Question types
  • Website widgets
    • Getting started
    • Attaching custom metadata to responses
    • Triggering surveys via custom properties
    • Debugging website widgets
Powered by GitBook
On this page
  • Overview
  • Set up custom triggering parameters in the Feedbackly dashboard
  • Adding a custom triggering property to the Feedback widget via the Javascript API
  • Removing a single custom triggering property
  • Clearing all custom properties
  1. Website widgets

Triggering surveys via custom properties

PreviousAttaching custom metadata to responsesNextDebugging website widgets

Last updated 5 years ago

Overview

Custom triggering properties are used to have a more fine-grained control over the triggering properties of a Feedbackly website widget.

For instance, you might want to trigger a survey based on whether a customer is logged in to the members' are in your website. This can be easily accomplished provided that there is Javascript access to the information required to set the triggering behavior.

Set up custom triggering parameters in the Feedbackly dashboard

In the website triggering options, open up Advanced targeting and add the property under Custom Properties like so

Adding a custom triggering property to the Feedback widget via the Javascript API

When the Feedbackly widget is installed, run

FBLY.action("addCustomProperty", KEY, VALUE)

Example

Let's assume the information of the logged in status is stored in a Javascript variable accessible in the namespace the widget command is run. For this example, we'll assume it's stored in user.loggedIn variable.

Running FBLY.action("addCustomProperty", "loggedIn", "true") will tell the widget that the user is logged in. If the widget triggering settings has that property set, the survey will then trigger (if no other restrictions are set)

Removing a single custom triggering property

When you want to prevent further surveys from displaying because of a custom property

When the Feedbackly widget is installed, run

FBLY.action("removeCustomProperty", KEY)

Example

Following the previous example, if we want to remove a custom triggering property (let's say the user logs out) we would run this command:

FBLY.action("removeCustomProperty", "loggedIn")

Clearing all custom properties

This command clears all custom triggering properties of the visitor

FBLY.action("clearCustomProperties")