Export form submissions

How to download your submissions as CSV files for spreadsheets, CRMs, and offline analysis

SGEN lets you export form submissions as CSV files inside a ZIP archive. Two export paths are available: a basic export with just the submitted field values, and a full export that also includes the visitor's landing page, referrer, traffic source, IP, and the pages-visited trail captured at submit time. Both are triggered from the Submissions screen. Use the basic export when you just need the answers; use the full export when you need attribution detail.

What is this for?

Exporting is your portable copy of form submissions. SGEN keeps submissions in its own database — the Submissions list is where you browse them in place — but for anything outside SGEN (loading a CRM, handing data to sales, archiving for a legal hold, aggregating in a spreadsheet), you need the data in a CSV.

Two formats suit two different needs:

• Submissions only — one CSV per form inside a ZIP. Columns are the field names on that form (Name, Email, Message, Company) plus Entry ID, Form Status, and Date. Use this when you just need the answers.
• Submissions with session data — same per-form CSV structure, but each row also gets the landing page, referrer, detected source, session ID, and a page-view timeline of the visitor's browsing before they submitted. Use this when you need attribution.

Good use cases

Example 1: Weekly backup. Every Friday, go to Forms → Submissions, set the date range to "last 7 days", pick All Forms, click Export Entries. Save the downloaded ZIP to your shared drive or cloud backup. Weeks of submissions archived outside SGEN — safe against accidental trash or migration.

Example 2: Load leads into a CRM. Sales wants this week's Lead Capture submissions in their CRM. Filter to the Lead Capture form + last 7 days, export. Unzip, open the CSV, upload to the CRM with the column mapping the CRM expects.

Example 3: Source-level attribution review. Marketing wants to know which source drove last month's demo requests. Filter to the Demo Request form + date range = last month. Export with session data. Open the CSV; Source column shows Direct / Google Ads / Google Organic / Referral / Social per row. Pivot in a spreadsheet.

Example 4: Follow-up call prep. A sales rep is about to call a lead who submitted last Tuesday. Open the submission in Forms → Submissions, or export last week's Lead Capture data and find the row in the CSV. The Page View Timeline column shows every page the lead viewed before submitting — "Pricing" + "Compare" + "Form" suggests a different hot-lead profile vs "Blog Post" + "Home" + "Form".

What NOT to use this for

• Do not export customer data casually. Submissions contain personally identifiable information. Treat exports as sensitive: store on a drive your privacy controls cover, delete when you're done with them, don't email them as attachments.
• Do not expect the export to respect SGEN permissions downstream. Once a submission is in a CSV, anyone with the CSV can see it. If you need tighter access control, use SGEN's submissions list in place.
• Do not use the export to edit submissions. The CSV is a read-only snapshot. Changing values in it does not change SGEN's stored submissions; re-importing the CSV is not supported.
• Do not rely on exports for real-time data feeds. Each export is a manual snapshot. For a live data feed into another system, use a per-form Integration (webhook or CRM connection) that fires at submit time.

How this connects to other features

• Submissions — the Export Entries button lives in the top-right of the Submissions list. Every filter you have active (form, date range, source, search) narrows what gets exported.
• Reports — exports give you the raw data behind the Reports charts. Same underlying submissions, different format.
• Traffic sources — the Source column in the "with session data" export is the same classification you see on the Submissions Source column and the Reports doughnut.
• Notifications / Email — exports do not include the admin notification email's send status beyond what's already on each submission row. To re-check who got emailed, open the submission in SGEN.

Before you start

• You have at least one Published form with submissions you want to export.
• You know which form(s) / date range / source you want to export. Empty exports (zero rows after filters) return an error rather than an empty ZIP.

Where to go

1. Open the left navigation.
2. Click Forms → Submissions (or open /sg-admin/forms/submissions/ directly). The Submissions list is the export launch pad.

Steps — Export submissions (basic)

1. Narrow the list

Pick a status pill (All / Submitted / Draft / Trash). Pick a form filter (one form or All Forms). Set a date range. Optionally type a search term. Click Apply.

2. Click Export Entries

The Export Entries button sits in the top-right of the Submissions screen.

3. Save the ZIP

Your browser downloads exported-submissions.zip. Inside the ZIP is one CSV per form. If your filter narrowed to a single form, you get one CSV; if you exported All Forms, you get multiple CSVs, one per form.

Each CSV has these columns:

• Form Name — the form each submission came from.
• Entry ID — SGEN's internal identifier for the submission.
• Form Status — Submitted / Draft / Trash.
• Date — when the submission was received.
• One column per form field (Name, Email, Message, Company, ...) with the submitted value.

Steps — Export submissions with session data

The richer export path is at the same entry point but produces a file with extra columns. The Submissions page either uses it automatically when you're on the Submitted pill, or exposes it via an alternate export link.

The extra columns you get:

• Session — a unique ID for the visitor's session.
• Landing Page — the first URL on your site the visitor opened.
• Referrer — the previous page / site they came from.
• Source — the detected traffic source (Direct / Google Ads / Google Organic / Referral / Social).
• Page View Timeline — one column with a structured record of every page the visitor viewed before submitting, including time on page and scroll depth.

The file name is submitted-entries-with-session-data-YYYYMMDD_HHMMSS.zip.

What success looks like

• Clicking Export Entries downloads a ZIP within a few seconds. For larger date ranges, the download can take up to a minute.
• Unzipping the ZIP reveals one or more CSV files with readable headers.
• The row count in each CSV matches the row count you saw in the Submissions list under the same filters.
• Opening the CSV in a spreadsheet shows every field from the form as a column with the submitted values.

What to do if it does not work

• The export returns "There are no entries available for export." Your filters returned zero rows. Widen the date range, clear a form filter, or switch status pills (for example, from Trash back to Submitted).
• The downloaded file has an unusual extension or my browser warns about it. Save the file anyway, then rename the extension to .zip if needed. CSVs inside are standard.
• The CSV opens in Excel but special characters look wrong. Excel sometimes misreads UTF-8. Open the CSV in Excel's "Import Text" wizard (or open in a modern editor like Google Sheets) and choose UTF-8 as the encoding.
• The session-data columns are blank for submissions I made myself. Submissions made directly against the form (without a real visitor session) have empty session data. Real visitor submissions record the landing page / referrer / timeline automatically.
• Page View Timeline column looks like one big line of JSON. That's expected — the timeline is structured data, not a flat column. Parse it in a script or pivot it out in a spreadsheet formula if you need to chart it.

Next step