Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.insito.app/llms.txt

Use this file to discover all available pages before exploring further.

The Triggers view lives at admin.insito.app → your project → Triggers. It’s a project-wide audit of every active trigger key, which survey it serves, and how many times it’s fired this month.

​
What you see

Each row in the table is one (active or inactive) trigger key, showing:
ColumnMeaning
Trigger keyThe string your app calls MicroSurvey.trigger(...) with
SurveyThe survey it serves — click to jump into the builder
Statusactive, draft, inactive
Fires this monthServer-side trigger count (not survey impressions — see below)
Last firedTimestamp of the most recent trigger call
“Fires this month” counts every call to MicroSurvey.trigger(yourKey), even when the API returned survey: null (audience filter, throttling, etc.). It’s not the same as the response count.

​
Use cases

​
Confirm a trigger is wired

After shipping a new version with MicroSurvey.trigger("upsell_seen"), open Triggers and look for the key. If it shows zero fires after a few hours of production traffic, something’s wrong:
  • The trigger key in the dashboard doesn’t match the string in your app exactly (case-sensitive, lowercase only).
  • identify() wasn’t called before the trigger.
  • The SDK isn’t initialised (check debug: true in dev).

​
Find orphan triggers

Surveys can be deleted but their app-side code stays. Triggers that no longer have a matching survey show as “Orphan” — the user-visible fires happen but no survey shows. Filter to Orphan to spot codepaths that need cleaning up.

​
Reset a trigger’s throttling

Per-survey: click the survey → Settings → Reset throttling. That clears seen_at for every user on this survey. See the throttling notes.

​
Auto-generated screen triggers

If you use screen tracking, the SDK fires screen_viewed:<pathname> automatically. These appear in the Triggers table with a 🗺️ icon — distinct from manual triggers so you can tell whether something is wired in app code or coming from the auto-discovery layer.