Skip to content
Open fromusers

In-product survey triggers

In-product surveys

Triggers define when an eligible in-product survey appears. Page targeting must already match before a trigger can fire.

In-product survey Distribute tab with trigger configuration

TriggerFires when
Time on pageThe visitor stays for N seconds
Element clickThe visitor clicks a specified element
Element hoverThe visitor hovers a specified element
Element inputThe visitor interacts with an input you specify
Scroll depthThe visitor scrolls to a configured depth
Exit intentThe visitor shows desktop exit intent behavior
Custom JS eventYour app signals an event the SDK recognizes
  1. Open the survey’s trigger settings.
  2. Choose the trigger type.
  3. Fill required fields (seconds, CSS selector, scroll percent, event name).
  4. Save.
  5. Test on staging with the SDK installed.

Use for calm moments: dashboards after load, thank-you pages, article mid-reads. Avoid very short timers on pages that still load content.

  • Prefer stable selectors (data attributes) over brittle auto-generated CSS classes.
  • Hover is desktop-oriented.
  • Input triggers suit “after user starts typing in search” moments, not every keystroke survey spam. Combine with frequency caps.

Good for long marketing or documentation pages. Set depth high enough that visitors saw the content you ask about.

Desktop technique for last-chance feedback. Provide a mobile alternative trigger if mobile traffic matters.

  1. Instrument your app to call FromUsers.trackEvent (see JavaScript API).
  2. Use the same event name in the survey trigger.
  3. Fire the event only after the user completes the meaningful action.
ScenarioTargetingTrigger
Docs feedbackURL starts with /docsScroll depth 75%
Export completeApp websiteCustom event export_done
Pricing questionsURL contains /pricingTime on page 20s
Abandon checkoutCheckout URLsExit intent (desktop)
  • Trigger fires once per your frequency rules, not on every scroll tick.
  • Selector still matches after front-end deploys.
  • Custom event name spelling matches exactly.
  • Mobile path tested for non-hover, non-exit-intent designs.

Common questions

What is a custom JS event trigger?

Your application dispatches or reports a named event (often via FromUsers.trackEvent). The survey can show when that event fires on an eligible page.

Can I use more than one trigger idea?

Configure the trigger that matches the moment you care about. Keep the setup simple so QA stays reliable.

Why is exit intent incomplete on mobile?

Exit intent relies on desktop pointer behavior. Prefer time, scroll, or custom events for mobile audiences.