Trigger Events add another layer of control to target the right users at the exact right time in their product journey.
Without a Trigger Event, a user would see a survey widget the moment they match your Target Audience. While this can be sufficient for some cases, you most likely want to tweak the timing of your survey.
Please: Trigger Events only apply to users that are matching your Target Audience. Trigger Events won’t have any effect if a user does not match the Target Audience of your survey.
Time Delay Trigger
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.
When a survey is shown depends on two things:
- 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
Whenever possible, we recommend to keep the Wait Time rather short and to move time conditions (e.g. “Signed up 30 days ago”) to your Target Audience. For example, if you want to survey users 30 days after they signed up, we recommend to create a Segments using that condition and use it as a Target Audience.
An important thing to understand is that the Wait Time is measured cumulative. For example, if you set the Reference Time to “User was first seen” and Wait Time to “2 minutes”, users will usually see the survey after 2 minutes. However, if a user leaves your app or website before the 2 minutes elapsed, and then comes back one day later, they’ll be prompted with the survey right away.
Please note: When you operate Refiner in “anonymous mode” (e.g. when surveying anonymous website traffic), the Reference Time is always “User was first seen”.
Page Visit Trigger
The Page Visit Trigger is a simple way of launching a survey once a user performs a specific action in your app or your website.
The Page Visit Trigger launches a survey when a user in your Target Audience visits a certain page (URL) of your app or website.
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:
|Equals||Triggers on pages where the full URL equals exactly the provided value.||https://app.domain.com/account/billing|
|Starts with||Triggers on all URLs that start with the provided value.||https://app.domain.com/account|
|Contains||Triggers when the provided value is located somewhere in the page URL.||/account/|
|Matches Pattern||Triggers 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.
While our “Page visit” and “Time delay” do a great job for most of our customers, there are some use cases for which launching a survey “ad-hoc” makes sense.
One popular scenario for this trigger method would be permanent “Feedback” button inside your app. Whenever a user clicks on this button, a survey is launched allowing them to send in their feedback.
To identify your survey, you can either use the survey ID that was automatically generated by Refiner, or define your own custom identifier. Using your own custom identifier 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).