FAQs

Below are some of the most frequently asked questions.

Do I need to add code to my app?

If you use Google Tag Manager or Segment, no. Otherwise, you'll need to install our SDK and identify users (see Orbital: Client SDK Docs)

How do I target a specific user segment?

You'll need to create a segment and implement orbital('identify', ...) in code. Read more here: Orbital: Target a User Segment

How do I configure the initial prompt?

The initial prompt can be configured in the admin per discovery.

Can I offer incentives?

You can configure the initial prompt to specify what type of incentive you're offering.

Think about your user flows and where in your product would be most appropriate to intercept the experience.

Yes, you can do this with our no-code option in the discovery config, or through manual SDK implementation of orbital('trigger', ...)

I already have a feedback flow – can I recruit on the back of that?

Yes, you can either trigger the popup normally, or jump straight to the scheduling page (see Client docs)

Can I implement a triggering delay?

Yes, if you implement the trigger manually

How do I screen participants?

Screeners can be added per discovery during creation.

The popup theme (light / dark / user preferred), primary color and position can all be configured from the admin settings.

The popup screen position can be configured from the settings page.

How do I reschedule a session?

You'll find a rescheduling link in the both the calendar event and the email notification.

Can participants reschedule/cancel?

Yes, they'll also have access to the rescheduling link in the both the calendar event and the email notification.

How do I pause a discovery?

This is possible from the discoveries overview and discovery page in the admin

How do I customize the calendar event?

The following calendar properties can be set per discovery from the admin:

Event name
Description
Location

Orbital intelligently limits the popup display rate over the course of the recruitment period based on the number of remaining available slots. You don't need to worry about your users being “spammed” by the popup. And of course once the slots are filled, Orbital will stop recruiting until another slot opens up.

Do I need to be worried about Orbital spamming my users?

No, there's a default cool-down period of 14 days per discovery that you can extend in the admin.

How far into the future can participants schedule with me?

The default is 14 days, which can be configured from the admin. Shorter is usually better as it provides you more agility to change the recruitment criteria when your needs change, and the no-show rate tends to drop with a shorter advance scheduling period.