Choose when and to whom a mobile survey appears

Two cards on the Share → Mobile app tab decide whether a survey appears: When to show sets the moment and Who sees it sets the audience. Both are checked on the user’s device, so no data about the user is sent anywhere to make the decision.

When to show

A trigger is something that happens in the app. When it happens and the user is in the audience, the survey opens.

The When to show card with an event trigger that has a property condition, a screen trigger and the delay

Click Add trigger and choose its type.

TriggerThe survey appears whenYou enter
EventThe app reports an event, such as a finished purchase.The event’s name, exactly as the app sends it.
ScreenThe user opens a screen.The screen’s name, exactly as the app sends it.
App launchThe app starts.Nothing.

An event trigger has two more options:

  • From occurrence no. The survey waits until the event has happened this many times on the device. With 3, it appears at the third purchase, not the first.
  • Property conditions. Click Add property condition to react only to some events, for example purchases where total is at least 50. All conditions have to be true.

A survey can have several triggers. It is considered when any one of them matches.

Delay is the number of seconds between the trigger and the survey. Use it to let a screen settle before the survey slides in. For a screen trigger, the survey is skipped when the user has left that screen in the meantime.

Note: A survey without a trigger never appears on its own. It is shown only when the app opens it from code. Your developer can read about it in Show a survey manually.

Who sees it

The audience narrows the survey down to some users. Every setting left empty means no restriction.

The Who sees it card: platforms, the list of users, a condition on the plan attribute, languages, app IDs and the share of users

SettingLimits the survey to
PlatformsiOS, Android or both. With none ticked, both.
UsersEveryone, identified users only (the app knows who they are, usually after login) or users who are not identified.
User attributesUsers whose attributes match your conditions, such as plan is pro. With more than one condition, choose whether all of them or any of them has to be true.
LanguagesUsers of the listed languages, separated by commas: en, pl, pt-BR. pt also matches pt-BR.
App IDsThe listed apps, when your team has more than one app or a separate test build.
Share of usersA percentage of installs. With 20, one install in five can see the survey, and it is always the same ones.

Conditions

OperatorTrue when
isThe attribute equals the value. Upper and lower case do not matter.
is notThe attribute differs from the value, or is not set at all.
contains, does not containThe value is, or is not, part of the attribute’s text.
is set, is not setThe attribute has any value, or none.
greater than, at least, less than, at mostThe attribute compares that way, as a number or a date.

Important: is not and does not contain are also true for users who do not have the attribute. To reach users whose plan is known and is not free, add two conditions joined with All conditions: plan is set and plan is not free.

Attributes come from the app. See Identify app users and pass data to responses.

Names have to match exactly

Event names, screen names and attribute names are compared exactly as written, including upper and lower case. Copy them from your developer rather than typing them from memory. See the naming table in Install the Responsly Mobile SDK in your app.

Save and wait a moment

Click Save. A note next to the button shows when there are unsaved changes.

The switch that shows the form in the mobile app, with the Unsaved changes note next to the Save button

Apps pick up new rules within about 10 minutes, the next time they start or come back to the foreground. To see a change at once on a test phone, reinstall the test build or ask your developer to reset the SDK.

Different rules for the same form

One set of rules is enough for most surveys. When the same form should appear in two places with different rules, for example after a purchase for everyone and on the settings screen for paying users only, click Add another configuration below the Appearance card.

Two configurations of one form, After purchase and Settings screen, with the Name field and the Delete this configuration link

A row with the configurations appears under the switch. Click a name to open that configuration. Each one has its own switch, triggers, audience, frequency, appearance, activity numbers and Survey ID. Give each a Name so you can tell them apart. Save saves all of them at once.

  • Responses from every configuration go to the same form.
  • The app counts displays separately for each configuration. A person who completed the survey through one can still see it through another, also with Once and Until completed. To prevent that, give the configurations audiences that do not overlap.
  • A form can have up to 10 configurations.
  • Delete this configuration removes the configuration and its activity numbers. Responses stay in the results. The first configuration cannot be deleted: switch it off instead.

Examples

GoalTriggerAudience
NPS for loyal customersEvent purchase_completed, from occurrence no. 3Identified users only
Feedback on a new screenScreen NewCheckout, delay 5 secondsShare of users 25
Why free users do not upgradeEvent paywall_closedplan is free
A survey for one marketApp launchLanguages de

How often a survey may come back is a separate setting: Set how often a mobile survey appears. The full list of rules and the order in which they are checked is in the developer documentation: Targeting.

FAQ

Can the same form have different rules in different places of the app?

Yes. Click Add another configuration on the Mobile app tab. Each configuration has its own triggers, audience, frequency and appearance, and all responses go to the same form.

Can a survey have more than one trigger?

Yes. Add as many triggers as you need. The survey is considered whenever any one of them matches.

What happens if a survey has no trigger?

It never appears on its own. It is shown only when the app opens it from its own code, for example from a Give feedback button.

How fast do new targeting rules reach the app?

Within about 10 minutes. The app refreshes its survey settings when it starts or comes back to the foreground with settings older than that.

Is user data sent to Responsly to decide who sees a survey?

No. The rules are checked on the device. Attributes and events are not uploaded for targeting.

Need help or have more questions?