Tiger Forms

Submissions

Browse, search, filter and open form entries; see payment status + integration logs per entry; export to CSV.

3 min read Updated July 14, 2026

Every form submission is captured and stored in WordPress, so nothing depends on email arriving. Browse, search, filter, inspect and export entries from one place, and use it as the audit trail for payments and integrations.

Where: WP Admin → Tiger Forms → Submissions.

Browsing the list

The Submissions screen is a standard WordPress list table with a column for ID, Source (the page the form was on), Submitted (date, with a “… ago” hint), Status, Email, Payment and Actions. You can sort by the submitted date and by status, and rows are color-coded — spam, pending review and paid entries stand out at a glance.

Filtering & search

  • Statusstored, spam, pending review, pending payment, paid, payment failed or trash.
  • Paymentpending, requires action, paid, failed or refunded.
  • Source — narrow to the entries from one page or form.
  • Date range — a from/to window.
  • Search — full-text search across submitted field values, backed by an index written at submission time so it stays fast.

Viewing an entry

Open a submission to see everything captured for it:

  1. A header with the ID, date, source page, IP hash, user agent and a Status dropdown you can change inline.
  2. A two-column field values table, with composite fields (name, address) shown as readable labelled chips.
  3. Any uploaded files, each with its virus-scan status.
  4. The integration log — every provider call (Mailchimp, webhooks and more) with its status, attempt number, the exact payload sent, and a per-row retry button.
  5. A payment block (provider, amount, transaction, status, refund) and the anti-spam log.

Bulk actions & export

  • Delete entries, or Mark as spam / Mark as read in bulk.
  • Resend notifications for selected entries.
  • Export selected as CSV for reporting, a spreadsheet, or migration. (A full export of every entry lives on the Tools page.)

Payments & integrations as an audit trail

Because payments and integrations are recorded against the entry, Submissions doubles as your record of what happened: confirm a charge went through, see exactly what was sent to a provider and how it responded, and retry a failed delivery without asking the user to submit again.

Tip: clear out old or spam entries periodically — the Tools page cleanup and the GDPR retention sweeps both help keep the list tidy and the database lean.

Troubleshooting

An entry shows “pending payment” and never became paid

That status means the form submitted but the payment provider never confirmed the charge — the visitor abandoned checkout or the card failed. Open the entry and check the payment block; expired pending submissions are cleared automatically by the Tools cleanup after seven days.

My search doesn’t find text I know was submitted

Search runs against the indexed searchable fields written when the entry was saved, so submissions created before a field existed may not be indexed for it. Try filtering by source and date instead, or open the entry directly to read its full field values.

Frequently asked questions

On the entry’s detail view, as paid or failed, with the provider reference.

Yes — use CSV export from the Submissions screen.

Still stuck?

We’re here to help

Can’t find what you’re looking for, or hit something that looks like a bug? Reach the support team or ask the community.