Form Submissions

View and manage all form submissions in one place. Track where submissions came from, monitor webhook delivery status, and analyze submission data across your organization.

Accessing Submissions

Submissions Dashboard

Navigate to Submissions in the sidebar to view all form submissions across your organization.

What you'll see:

• Chronological list of all submissions
• Form name for each submission
• Submission date and time
• Submitter information (if captured)
• Landing page source (if applicable)
• Webhook status (success, pending, failed)

Submissions Per Form

To view submissions for a specific form:

1. Navigate to Forms in sidebar
2. Click on a form
3. Click "View Submissions" tab
4. See all submissions for that form only

Submission List View

Default View

Submissions are displayed in a table with columns:

Sorting and Filtering

Sort by:

• Date (newest/oldest first)
• Form name (A-Z)
• Status (success/pending/failed)

Filter by:

• Specific form
• Date range (coming soon)
• Landing page source (coming soon)
• Webhook status (coming soon)

Pagination

• Default: 25 submissions per page
• Navigate with Previous/Next buttons
• Jump to specific page
• Change items per page (coming soon)

Viewing Submission Details

Opening Details

Click any submission to view full details:

1. Submission Info

   • Submission ID
   • Form name
   • Submitted date and time
   • Landing page source (if applicable)

2. Submitted Data

   • All form field values
   • Displayed as key-value pairs
   • Copy individual values
   • Copy all data as JSON

3. Metadata

   • IP address
   • User agent (browser/device info)
   • Referrer URL (previous page)
   • UTM tracking parameters (if present)
   • Landing page ID and slug

4. Webhook Status

   • Delivery status (success, pending, failed)
   • Attempt count
   • Last attempt time
   • Error message (if failed)
   • Next retry time (if pending)

Submission ID

Each submission has a unique ID (e.g., sub_abc12345):

• Use for tracking and reference
• Include in support requests
• Use for manual processing if needed

Understanding Submission Data

Data Structure

Submission data contains:

Top Level:

{
  "submissionId": "sub_abc123",
  "formId": "form_xyz789",
  "formName": "Contact Form",
  "submittedAt": "2024-01-15T10:30:00Z"
}

Submitted Values:

{
  "data": {
    "name": "John Smith",
    "email": "john@example.com",
    "company": "Acme Inc",
    "message": "Interested in learning more..."
  }
}

Metadata:

{
  "metadata": {
    "ipAddress": "192.168.1.1",
    "userAgent": "Mozilla/5.0 ...",
    "landerId": "lander_abc123",
    "landerSlug": "product-landing",
    "referrer": "https://google.com",
    "utmSource": "facebook",
    "utmMedium": "cpc",
    "utmCampaign": "spring-2024"
  }
}

Field Values by Type

Text Fields:

"name": "John Smith"
"email": "john@example.com"
"message": "This is a message..."

Select/Radio (Single Choice):

"companySize": "11-50"
"plan": "pro"

Checkboxes/Multi-Select (Multiple Choices):

"interests": ["marketing", "sales", "product"]
"preferences": ["email_updates", "newsletter"]

Number Fields:

"quantity": 5
"budget": 50000

Date Fields:

"eventDate": "2024-06-15"
"birthDate": "1990-01-01"

File Uploads:

"resume": {
  "filename": "resume.pdf",
  "size": 524288,
  "url": "https://storage.flysuper.com/uploads/abc123.pdf",
  "mimeType": "application/pdf"
}

Metadata Explained

IP Address

The submitter's IP address:

• Used for rate limiting
• Geographic insights (coming soon)
• Fraud detection
• Privacy: Not shown to end users

Example:

192.168.1.1
2001:0db8:85a3:0000:0000:8a2e:0370:7334 (IPv6)

User Agent

Browser and device information:

• Browser name and version
• Operating system
• Device type (desktop/mobile/tablet)
• Used for analytics and debugging

Example:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Parsed info:

• Browser: Chrome 120
• OS: Windows 10
• Device: Desktop

Referrer

The URL of the page the user came from before submitting:

• Track traffic sources
• Understand user journey
• Measure campaign effectiveness

Examples:

https://google.com/search?q=project+management+tool
https://facebook.com
https://yoursite.com/blog/post-name
(direct) - No referrer (direct traffic)

Landing Page Tracking

If submitted through a landing page:

• landerId: Landing page ID
• landerSlug: Landing page URL slug
• domainId: Custom domain ID (if applicable)

Use case: Know which landing page generated the submission.

UTM Parameters

Track marketing campaign performance:

• utmSource: Where traffic came from (google, facebook, email, etc.)
• utmMedium: Marketing medium (cpc, social, email, etc.)
• utmCampaign: Specific campaign name (spring_sale, product_launch, etc.)
• utmContent: Content variant (ad_variant_a, button_blue, etc.)
• utmTerm: Search keywords (for paid search)

Example URL:

https://yourdomain.com/landing-page?utm_source=facebook&utm_medium=cpc&utm_campaign=spring_2024&utm_content=variant_a

Captured as:

{
  "utmSource": "facebook",
  "utmMedium": "cpc",
  "utmCampaign": "spring_2024",
  "utmContent": "variant_a"
}

Use case: Measure ROI of specific campaigns and channels.

Webhook Status

Status Types

✅ Success (Delivered)

• Webhook delivered successfully
• Received 2xx status code response
• No further action needed

⏳ Pending (Retry Scheduled)

• Initial delivery failed
• Retry scheduled according to retry schedule
• Will retry up to 5 more times
• Shows next retry time

❌ Failed (All Retries Exhausted)

• All 6 attempts failed (initial + 5 retries)
• No more automatic retries
• Manual intervention needed

— No Webhook Configured

• Form doesn't have webhook configured
• Submission stored but not sent anywhere

Viewing Webhook Details

Click on a submission to see webhook status:

For Successful Webhooks:

• ✅ Success indicator
• Response code (e.g., 200 OK)
• Response time (e.g., 150ms)
• Delivered timestamp

For Pending Webhooks:

• ⏳ Pending indicator
• Attempt count (e.g., "Attempt 2 of 6")
• Last error message
• Next retry time (e.g., "Retrying in 3m 45s")

For Failed Webhooks:

• ❌ Failed indicator
• Total attempts (6)
• Last error message
• Failure reason (timeout, 500 error, etc.)
• Option to manually retry (coming soon)

Common Webhook Errors

Timeout (30s):

Endpoint did not respond within 30 seconds

Fix: Optimize endpoint to respond faster, or process asynchronously.

500 Internal Server Error:

HTTP 500: Internal Server Error

Fix: Check endpoint logs, fix server-side error.

Connection Refused:

Connection refused to https://yourendpoint.com

Fix: Ensure endpoint is running and publicly accessible.

Invalid SSL Certificate:

SSL certificate verification failed

Fix: Ensure valid SSL certificate on your endpoint.

403 Forbidden:

HTTP 403: Forbidden

Fix: Check authentication, verify webhook secret, check IP whitelist.

Exporting Submissions

Manual Copy

For individual submissions:

1. Open submission details
2. Click "Copy as JSON"
3. Paste into spreadsheet or text editor

Bulk Export (Coming Soon)

Export multiple submissions:

• Select date range
• Choose format (CSV, JSON, Excel)
• Include/exclude metadata
• Download file

Use cases:

• Import into external tools
• Backup submission data
• Analyze in spreadsheet
• Generate reports

Analyzing Submissions

Submission Volume

Track submission trends:

• Submissions per day/week/month
• Submissions per form
• Submissions per landing page
• Peak submission times

Use case: Understand which forms and pages are performing best.

Conversion Tracking

Calculate conversion rates:

Conversion Rate = (Submissions / Page Views) × 100

Example:

• Landing page views: 1,000
• Form submissions: 50
• Conversion rate: 5%

Benchmark: 2-5% is typical for B2B forms, 5-15% for simple signups.

Source Attribution

Understand where submissions come from:

• Which landing pages generate most submissions
• Which traffic sources convert best (organic, paid, social, etc.)
• Which campaigns drive submissions

Use case: Optimize marketing spend and double down on high-performing channels.

Form Completion Insights (Coming Soon)

Analyze form completion:

• Field completion rates
• Drop-off points (which fields cause abandonment)
• Time to complete
• Error rates per field

Submission Filters and Search

Filtering Submissions

By Form:

1. Click form dropdown
2. Select specific form
3. View only submissions for that form

By Date Range (Coming Soon):

1. Click date range picker
2. Select start and end dates
3. View submissions in that range

By Landing Page (Coming Soon):

1. Click landing page dropdown
2. Select specific landing page
3. View submissions from that page only

By Status (Coming Soon):

1. Click status dropdown
2. Select: Success, Pending, Failed, or No Webhook
3. View filtered submissions

Searching Submissions (Coming Soon)

Search by:

• Email address
• Name
• Company
• Any form field value
• Submission ID

Example: Search "acme" to find all submissions with "Acme" in any field.

Submission Retention

Data Retention Policy

Submissions are retained according to your plan:

Current Retention:

• All Plans: Unlimited retention

Future Plans:

• Free: 90 days
• Pro: 1 year
• Enterprise: Unlimited or custom

Recommendation: Export important submissions for long-term storage.

Data Privacy

Compliance:

• GDPR compliant (data deletion on request)
• CCPA compliant (data access and deletion)
• SOC 2 compliant (security standards)

User Rights:

• Right to access data
• Right to deletion (contact support)
• Right to data portability (export feature)

Best Practices

Regular Review

1. Daily: Check for failed webhooks
2. Weekly: Review submission trends
3. Monthly: Analyze conversion rates
4. Quarterly: Export for long-term backup

Webhook Monitoring

1. Set up alerts for webhook failures (coming soon)
2. Check pending webhooks regularly
3. Fix issues quickly to avoid data loss
4. Test after changes to forms or webhooks

Data Management

1. Export regularly for backup
2. Clean test submissions (coming soon)
3. Archive old data if needed
4. Respect privacy - delete on request

Security

1. Limit access to submissions (team permissions coming soon)
2. Don't share screenshots with PII (personally identifiable information)
3. Use secure connections when exporting
4. Follow compliance requirements (GDPR, CCPA, etc.)

Troubleshooting

"No submissions showing"

Check:

1. ✅ Forms are published and embedded
2. ✅ Test submission to verify form works
3. ✅ Selected correct organization (if multi-org)
4. ✅ Filters not hiding submissions

"Submission data is incomplete"

Possible causes:

• User didn't fill all fields (only required fields captured)
• JavaScript error on form submission
• Bot protection blocked partial submission

Solution: Review form configuration, test thoroughly.

"Webhook shows failed but endpoint received data"

Possible cause:

• Endpoint didn't return 2xx status code
• Endpoint returned success after processing (too slow)

Solution: Return 2xx immediately, process asynchronously.

"Missing UTM parameters"

Cause: URL didn't include UTM parameters.

Solution: Ensure marketing links include UTM parameters:

https://yourdomain.com/landing?utm_source=facebook&utm_medium=cpc

What's Next?

• Creating Forms - Build new forms
• Webhooks - Set up integrations
• Field Types - Field reference

Quick Reference

Pro Tip: Set up a webhook to automatically send submissions to your CRM or database. Don't rely solely on viewing submissions in the dashboard - automate your workflow for scalability!