Skip to content

Progress ​

The Progress tab in the Survey Analytics workspace (/s/analyze/survey/{surveyId}/progress/progress) tracks the delivery, engagement, and completion funnel of a survey's invitation runs.

It is designed around a strict privacy boundary: organizers see who was invited and how far they progressed, but survey responses remain anonymous and are never linked to an invitation, token, or email address.

The Analytics Progress page showing the run card, funnel metrics, and Reminders history card
The Progress workspace displaying the active invitation run, funnel counters, rates, and reminder history.

Run Selector Cards ​

Each invitation wave sent from Share → Distribute appears as an interactive card at the top of the page. Clicking a card loads its funnel counters and reminder log.

Each run card displays:

  • Audience name: The name of the team audience the run targeted.
  • Sent timestamp: When the run started sending.
  • Summary metrics: invitedCount, submittedCount, and the computed response percentage.
  • Run status:
    • sending — batches are actively being dispatched.
    • active — initial send completed; links are live and scheduled reminders are active.
    • paused — automatically paused by the deliverability/reputation guard (high bounce or complaint rate after 1,000 sends) or a mail provider failure.
    • cancelled — stopped by an editor; links that have not landed are deactivated and no further batches or reminders are sent.

Run Toolbar Actions ​

The header toolbar provides run-level controls for the currently selected run:

ActionAvailabilityDescription
RefreshAlwaysReloads the run's funnel counters and, if open, refreshes the per-recipient table.
Download status CSVTeam Owners, Admins, EditorsExports a CSV (invitation-progress-{surveyId}.csv) of the run's recipients containing masked email addresses, statuses, timestamps, and reminder counts. Never includes full email addresses or survey answers.
Send reminder nowActive / Sending runsRuns a dry-run check (remindInvitationRun with dryRun: true) to count eligible recipients, prompts for confirmation with the exact count, and dispatches a manual reminder pass.
Send remainingWhen sentCount < invitedCount (and not paused/cancelled)Sends the next batch of invitations when a large run was partially deferred by the 20,000/day team email cap.
Resume runPaused runs onlyClears the pause state on a run so remaining invitations and reminders can resume.
Cancel runNon-cancelled runsPrompts for confirmation, marks the run cancelled, invalidates invitation links that have not landed, and stops any remaining batches or scheduled reminders.

Run Detail: Funnel and Rate Tiles ​

The Run detail card renders two aligned rows of lapp-stat metric tiles read directly from the run document's aggregate counters.

Row 1: Monotonic Funnel Stages ​

Each stage tile includes a progress bar showing its ratio against Invited. Downstream stages are cumulative (an invitation that opened or submitted also counts toward earlier stages):

Stage TileCounter FieldDefinition
InvitedinvitedCountTotal eligible recipients frozen into the run at creation time.
SentsentInvitationCountInvitations accepted by the mail service (stage >= 1).
DelivereddeliveredCountInvitations confirmed delivered by the mail provider webhook (stage >= 2).
Email openedopenedCountRecipients whose mail client loaded the Mailgun open-tracking pixel. This is a read, not a survey visit (stage >= 3).
Survey startedlandedCountRecipients whose unique /v2/{surveyId}/i/{token} link was validated and who therefore landed on the survey.
Started answeringstartedCountRecipients whose survey app loaded and whose respondent actor was created (stage >= 4).
SubmittedsubmittedCountRecipients who completed and submitted the survey (stage 5 / submittedAt present).

An email open is not a survey landing: Mailgun's tracking pixel can fire without the recipient visiting the survey. landedCount is the direct evidence; an invitation that started or submitted also counts as landed, which keeps runs recorded before the split readable.

Row 2: Rates and Negative Outcomes ​

TileFormula / FieldDefinition
Response rateSubmitted ÷ InvitedPercentage of invited recipients who submitted the survey (formatted to 1 decimal place).
Completion rateSubmitted ÷ Started answeringPercentage of recipients who submitted after starting to answer the survey.
Drop-offmax(Started answering − Submitted, 0)Number of recipients who started answering the survey but have not submitted yet.
BouncedbouncedCountInvitations that hard-bounced (or reached three consecutive soft bounces). Added to the customer-wide suppression list.
UnsubscribedunsubscribedCountRecipients who used the one-click unsubscribe link. Added to the customer-wide suppression list.
ComplainedcomplainedCountRecipients who reported the email as spam. Added to the customer-wide suppression list.
FailedfailedCountSends rejected by the mail service before delivery (cleared if a later retry succeeds).

Recipient Details Grid ​

Per-recipient rows are loaded on demand when a team owner, admin, or editor clicks Load details. Survey guests and non-team collaborators see the aggregate funnel tiles only.

The Progress tab with the recipient details table expanded
The recipient details grid showing masked addresses, status badges, and row-level Remind, Resend, and Reissue link actions.

Loading details performs a single read of the run's invitation documents so the browser grid can filter and sort across the entire run without server paging.

Columns and Filters ​

ColumnHeader ControlDescription
NameText filter + SorterRecipient's name (or — when unset).
EmailText filterMasked email address keeping only the first character of the local part and the domain (for example, j***@accessiblesurveys.com). Full addresses are only visible in Team Settings → Audiences.
LanguageSelect filterLanguage code used for the recipient's invitation.
StatusSelect filterExclusive lifecycle status badge: invited, sent, opened, started, submitted (green), unsubscribed (amber), bounced (red), complained (red), or failed (red). Note that provider delivery (delivered) displays as sent in the status column.
Last activityColumn sorterTimestamp of the most recent lifecycle event for that invitation.
RemindersStatic headerTotal reminders sent to this recipient, plus a (N failed) note if any reminder attempts failed.
ActionsRow action buttonsPer-recipient recovery and reminder actions (see below).

Per-Recipient Row Actions ​

ActionEnabled WhenBehavior
RemindStatus is not submitted, unsubscribed, bounced, complained, or failedSends a manual reminder to this recipient (remindInvitation). Enforces a 24-hour cooldown since the last reminder, a maximum of 2 manual reminders, and a maximum of 5 total reminders per recipient.
ResendStatus is not submitted, unsubscribed, bounced, or complainedRe-sends the invitation email with the recipient's existing link (resendInvitation). Used to recover from a failed send or a lost email.
Reissue linkStatus is not submitted, unsubscribed, bounced, or complainedPrompts for confirmation, immediately invalidates the old invitation token, generates a new /v2/{surveyId}/i/{token} link, and emails it to the recipient (reissueInvitation).

Reminders History Card ​

The Reminders card at the bottom of the page lists every scheduled and manual reminder pass recorded on the run (reminderHistory):

  • Pass: Reminder 1, Reminder 2, Reminder 3 (for scheduled passes) or Manual (for editor-triggered passes).
  • When: Local timestamp of the pass.
  • Who: Scheduled job or the editor who triggered a manual pass.
  • Sent: Number of reminder emails accepted by the mail service during the pass.
  • Failed: Number of reminder emails that failed during the pass.

If scheduled reminders fail three times in a row (reminderErrorAt), the card displays a warning banner advising the editor to inspect the recipient list and mail settings before retrying.