Trigger Events

Introduction

Trigger Events add another layer of control to target the right users at the exact right time while they are using your product. Refiner offers different Trigger Event options that allow you to fine tune the timing of your in-product survey.

Trigger Events for Web-Client

Below you’ll find a description of all Trigger Events that are available for In-Product Surveys powered by our Web-Client. The available options might be slightly different depending when you operate our Web-Client in Anonymous Mode.

Immediately

Setting the trigger event to Immediately is the equivalent of not using any trigger event. As soon as a user matches your Target Audience setting, they’ll see the survey. This option can be a good fit if you are making use of user segments in your Target Audience that providing precise enough targeting.

Time Delay

The Time Delay Trigger is our most popular launch trigger and a great fit for a lot of use-cases. The idea is simple: For users matching your Target Audience, Refiner waits for a specific amount of time to pass before showing your survey to them.

Combining the Time Delay trigger with Segment Based Targeting gives you a lot of control over when exactly a survey should appear. For example, you could create a user segment “Signed up 30 days ago” for your Target Audience and combine it with a Time Delay trigger of “3 minutes after starting a new session”.

The Time Delay Trigger offers the following options:

  • Wait Time: This is the time interval that needs to pass. Depending on your use-case, the Wait Time can be set to anything between a couple of seconds up to several days (more info below).
  • Reference Moment: You can choose between different moments in a user’s journey which will be used as some kind of anchor point in time. You can choose between:
    • User start a new session
    • User enters your Target Audience
    • User was seen for the first time

When you are operating our web-client in Anonymous Users Mode, the reference time for the Time Delay trigger is always “First Seen”. This is the moment a visitor landed on your web application for the first time.

Page Visit

The Page Visit Trigger is a simple way of launching a survey once a user performs a specific action in your web application. This trigger option is only available for Web-app Surveys.

The Page Visit Trigger launches a survey when a user in your Target Audience visits a certain page (URL) of your app.

Some scenarios where this launch trigger comes in handy:

  • Your user just purchased your product and gets redirected to an order confirmation page
  • A user looks at your pricing page which indicates that they are considering purchasing your product
  • A user just performed an important action in your app (e.g. created their first project)

The Page Visit Trigger event can be set up by adding one or multiple Page Rules as shown in the screenshot below.

Each rule has a comparison method followed by a comparison value. The supported comparison methods are:

MethodDescriptionExample Value
EqualsTriggers on pages where the full URL equals exactly the provided value.https://app.domain.com/account/billing
Starts withTriggers on all URLs that start with the provided value.https://app.domain.com/account
ContainsTriggers when the provided value is located somewhere in the page URL./account/
Matches PatternTriggers on URLs that match a provided wildcard pattern. You can use * to indicate that variable parts of a URL.https://app.domain.com/*/something/*

When you add multiple rules, a match occurs when at least one rule returns a positive result.

A survey is shown to a user when any of the page rules match for the first time. If you want to launch the survey each time one of the rules matches (e.g. on a checkout page), you can set the “Recurring Survey” to “Repeating”.

Tracked Event

The Tracked Event trigger lets you to launch a survey when a user performed a certain action in your app for a certain number of times. You can learn how to track events for your users on our Event Tracking page.

Please note that only events tracked with our Web-Client or Mobile SDKs are processed in real-time. Events tracked through a backend integration (Segment, API, etc.) are processed with a slight delay of a couple of minutes.

Manual

There are some use cases where you want to launch a survey ad-hoc at very specific moments. For these situations we are providing the “Manual” trigger option which lets you launch a survey by executing code in your app.

To launch a survey ad-hoc you can execute the “showForm” method of our Javascript Web-Client. A code example is shown in the survey editor as shown in the screenshot below.

To identify your survey, you can either use the survey ID that was automatically generated by Refiner, or define an alias. Using an alias allows you to swap out a survey without changing your code, or launch the same type of surveys in different projects / environments (testing vs prod).

By default, the survey is shown to the use only once. All subsequent “showForm” method calls won’t result in any additional survey views. The Target Audience, Page Rules and Survey Throttling settings are taken into account..

You can also launch a survey every time the Javascript method is called. To enable this behaviour, set the “Recurrence” option to “Repeatedly”.

If you want to launch a survey without any checks, for example for testing purposes, you can add an additional “force” parameter when executing the Javascript command.

Trigger Events for Mobile SDKs

Below you’ll find a description of Trigger Events that are available for In-Product Surveys powered by our Mobile SDKs.

Immediately

Setting the trigger event to Immediately is the equivalent of not using any trigger event. As soon as a user matches your Target Audience setting, they’ll see the survey. This option can be a good fit if you are making use of user segments in your Target Audience that providing precise enough targeting.

Time Delay

The Time Delay Trigger allows you to delay a survey a couple of minutes. For users matching your Target Audience, Refiner waits for a specific amount of time to pass before showing your survey to them.

Please note that the Mobile SDKs are not automatically checking our backend API if a survey should be shown or not. To make this Trigger Event work, you’ll need make sure that the SDKs is “pinging” our servers regularly by calling either the ping, trackEvent or trackScreen method.

Combining the Time Delay trigger with Segment Based Targeting gives you a lot of control over when exactly a survey should appear. For example, you could create a user segment “Signed up 30 days ago” for your Target Audience and combine it with a Time Delay trigger of “3 minutes after starting a new session”.

The Time Delay Trigger offers the following options:

  • Wait Time: This is the time interval that needs to pass. Depending on your use-case, the Wait Time can be set to anything between a couple of seconds up to several days (more info below).
  • Reference Moment: You can choose between different moments in a user’s journey which will be used as some kind of anchor point in time. You can choose between:
    • User start a new session
    • User enters your Target Audience
    • User was seen for the first time

Screen Visit

The Screen Visit trigger s only available for mobile surveys powered by one of our Mobile SDKs. It functions similar to the Page Visit trigger described above. The only difference is that instead of matching website URLs, it matches the tracked screen names of your app.

Tracked Event

The Tracked Event trigger lets you to launch a survey when a user performed a certain action in your app for a certain number of times. You can learn how to track events for your users on our Event Tracking page.

Please note that only events tracked with our Web-Client or Mobile SDKs are processed in real-time. Events tracked through a backend integration (Segment, API, etc.) are processed with a slight delay of a couple of minutes.

Manual

There are some use cases where you want to launch a survey ad-hoc at very specific moments. For these situations we are providing the “Manual” trigger option which lets you launch a survey by executing code in your app.

To launch a survey ad-hoc you can execute the “showForm” method of our Mobile SDKs. Code examples are shown in the survey editor as shown in the screenshot below.

To identify your survey, you can either use the survey ID that was automatically generated by Refiner, or define an alias. Using an alias allows you to swap out a survey without changing your code, or launch the same type of surveys in different projects / environments (testing vs prod).

By default, the survey is shown to the use only once. All subsequent “showForm” method calls won’t result in any additional survey views. The Target Audience, Page Rules and Survey Throttling settings are taken into account..

You can also launch a survey every time the Javascript method is called. To enable this behaviour, set the “Recurrence” option to “Repeatedly”.

If you want to launch a survey without any checks, for example for testing purposes, you can add an additional “force” parameter when executing the Javascript command.

Additional options

Recurring Surveys

If you want to collect more than one response from each user, you can enable the “Recurrence” option. Depending on the Trigger Event you chose, different options are available as described on this page.

On-show Delay

In the Page Rules section you’ll also find an On-Show Delay option which gives you the possibility to slightly delay the display or your survey. Usually, setting the delay to 3-5 seconds is a great way to give your users some time to settle in, without risking lower response rates.

Was this helpful? Let us know with a quick a vote