View and manage form submissions

In short. Go to Forms → Submissions to see every entry every form has collected in one searchable list. Filter by form, traffic source, or date range. Click any row to see every submitted field plus the visitor's session trail. Trash spam in bulk, re-dispatch a failed integration from the detail view, and export to CSV when you need the data outside SGEN. Your email inbox already gets one notification per entry — this screen is the durable, filterable copy that stays inside SGEN.

On this page: Overview · Filter and search · Open a submission · Bulk-trash · Re-dispatch · Troubleshooting

How to read, filter, search, and trash the submissions your forms have collected

Overview

Submissions is a single searchable list of every form entry from every form. From here you filter by form, date range, or traffic source; search by submitted value or visitor email; open a single entry to see every field and the visitor's session trail; and trash or permanently delete entries you no longer need. It is also the launch pad for re-firing an integration (Slack, webhook, CRM) against an entry that failed the first time.

What it covers

The Submissions screen covers every entry collected by every published form on your site — from the moment a visitor clicks Submit to the moment you permanently delete the record. It covers:

• Reading and searching entries across all forms in one view.
• Filtering by form, traffic source, date range, or free-text search.
• Viewing the full field-by-field detail and visitor session trail for any single entry.
• Trashing and permanently deleting entries, including bulk actions.
• Re-dispatching a failed integration without re-opening the form.

It does not cover building or editing forms (see Build a form), viewing aggregated reports (see View form reports), or exporting to CSV (see Export submissions).

Reference

Every row in the submissions list exposes the following columns:

The detail view (click any row) adds: Submitted Values (every field), Visitor Details sidebar (IP, User Agent, Referrer, Landing Page), and — when SGEN captured the session — a Page View Timeline with per-page time-on-page and scroll depth.

The list itself is the heart of the screen. Click any cell with a pointer cursor in the mock below to see what each control does:

Examples

Finding a submission by email. A contact says they submitted a form but never heard back. Open Submissions, type their email in Search, set the date range to the relevant window, and click Apply. Click the matching row to see every field, the notification email status, and the visitor's session trail.

Cleaning up spam. Tick the checkboxes on obvious spam rows. In the Bulk Action dropdown pick Move to Trash, then click Apply:

Opening a single submission for details. Click any row's form title to open the detail view — a table of every submitted field on the left, plus a sidebar with Date, Status, Email Sent, User Agent, IP, and Referrer:

The right sidebar includes a Page View Timeline when SGEN captured the visitor's session — every page they visited before submitting, with time-on-page and scroll depth.

What NOT to use this for

• Not a customer database. The screen is read-only — you cannot edit submitted values. Export to your contact-management tool if you need to enrich or follow up.
• Not reliable for self-submitted test entries. Source detection uses the visitor's referrer and landing page. A test submission you make yourself shows as Direct.
• Not a safe place to keep data you still need. Trashed submissions are excluded from the default view and from exports. Permanent-delete from Trash is irreversible.
• Email Sent is not a delivery guarantee. A green check means SGEN handed the email to the mail system — spam filters, bounces, or a mis-typed To address can still swallow it.
• Re-dispatch is not a dry run. It re-sends the entry through every connected destination the same way a fresh submission would. Test on a staging form first.

How this connects to other features

Before you start

• You are signed in to SGEN as an Administrator.
• You have at least one published form.
• At least one visitor has submitted that form (otherwise the list is empty by design).

Where to go

1. Open the left navigation.
2. Click Forms → Submissions (or open /sg-admin/forms/submissions/ directly).

Steps — Filter and search

1. Click a status pill

Four pills sit at the top:

• All — every submission in every status.
• Submitted — submissions that completed.
• Draft — submissions saved as draft (only applies if a form has autosave enabled).
• Trash — submissions you moved to trash.

2. Filter by form

The All Forms dropdown narrows to a single form. Useful when one form is much higher-traffic than the others.

3. Filter by source

The All Sources dropdown narrows to a specific traffic source: Direct, Google Ads, Google Organic, Referral, Social.

4. Set a date range

The date range picker defaults to the last 6 months. Click it to open a calendar and pick a different range.

5. Search

The Search box matches against submitted values, visitor email, User Agent, referrer, and the form title. If your search term looks like an IP address, it also matches the visitor's IP.

6. Apply

Click Apply. The table updates with the filtered set. Active filters persist in the URL — copy the address to a teammate and they land on the same filtered list.

Steps — Open a single submission

Click any row to open the detail view at /sg-admin/forms/submissions/view/N. You see:

• A Submitted Values table — every form field and the value the visitor entered.
• A Visitor Details sidebar — Date, Status, Email Sent status, User Agent, IP, Referrer.
• A Page View Timeline — if SGEN captured the visitor's pages-visited trail before submit, it shows as a timeline with per-page time-on-page and scroll depth.
• A Re-dispatch to integrations action — re-fires the saved submission through every connected destination. Use this when you fixed a broken webhook and want to replay the missed lead.
• A Delete Permanently link — irreversible.

Steps — Bulk-trash submissions

1. Tick rows

Every row has a checkbox. Use the header checkbox to tick or clear every row on the current page.

2. Pick an action

The Bulk Action dropdown offers these actions depending on which pill you are viewing:

• Move to Trash — soft-deletes the selected rows (recoverable from Trash).
• Mark as Read — marks rows as read without moving them.
• Mark as Unread — marks rows as unread, surfacing them in your daily triage.

When viewing the Trash pill, Delete Permanently also appears.

3. Click Apply

The page refreshes. For Move to Trash, ticked rows move to the Trash pill and the Trash count rises. For Mark as Read / Unread, rows stay in place and their read indicator updates.

4. Delete Permanently from Trash

When viewing the Trash pill, the Bulk Action dropdown shows Delete Permanently. SGEN shows a confirmation modal before the delete runs:

Click Yes, delete N submissions to finish. Click Keep them to back out.

Privacy note. For a privacy request (GDPR, CCPA), export the submissions first, then permanently delete. Document both steps — export and empty — in your compliance log with the date, row count, and the admin who acted.

Steps — Re-dispatch a single submission

1. Open the submission

Click any row in the list. The detail view loads at /sg-admin/forms/submissions/view/N.

2. Confirm Email Sent or integration status

Look at the Email Sent indicator in the sidebar. Red or "not sent" means the original dispatch failed — re-dispatch is the next step.

3. Click Re-dispatch to integrations

The action lives in the top-right of the detail view. It re-runs the same code path a fresh submission would, against the form's currently configured integrations. SGEN responds with a toast confirming success or naming the integration that failed:

Tips for keeping your inbox useful

• Skim once a week. Five minutes on the All pill catches forms that have gone quiet (often a sign a form is broken on its page) and spam waves before they pile up.
• Search by IP to spot bots. When the same address submits multiple rows in an hour, a quick IP search makes the pattern obvious.
• Re-dispatch sparingly. A steady replay need signals an unhealthy integration — fix the webhook or rotate credentials rather than replaying failures repeatedly.
• Export before deleting. If you need to clean out a year of old submissions, export the CSV first. Permanent-delete is permanent; the CSV is your insurance.

What success looks like

• The list loads with submission rows (or an empty-state if nothing matches your filters).
• Clicking a pill narrows the table; the active pill turns red.
• Clicking any row opens the detail view with every field plus session details.
• Ticking rows and applying Move to Trash sends them to the Trash pill.
• Re-dispatching posts a green-toast confirmation and the result panel shown above.

What to do if it does not work

• The list is empty but submissions arrived. Check your date range — the default is the last 6 months and narrowing it can hide older entries. Also check the Trash pill.
• A submission is missing. Someone on your team may have trashed it. Click the Trash pill.
• Source says Direct but the campaign was Google Ads. Ad-blockers, privacy tools that strip referrers, or a link without UTM parameters all look Direct.
• Email Sent is green but the recipient got nothing. Check the recipient's spam folder. If the To address in the form's Mail Settings has a typo, SGEN logged success but the mail server never delivered.
• Delete Permanently is not in the dropdown. It only appears when viewing the Trash pill. Move the submission to Trash first, then switch to Trash.
• Re-dispatch returned ok=true but the destination has nothing. Check the destination's own activity log — if SGEN reported success, SGEN handed the payload off correctly. The integration may be silently dropping it (channel archived, webhook URL changed, credentials rotated).
• Trashed submissions come back the next morning. An integration may be recreating them. Pause the integration, trash the entries again, then resume.

Next step

• View form reports
• Export submissions
• Manage the Forms list