You have designed, tested and released your form, and now it has begun collecting responses. This section explains how you can manage submitted form data .
Form data collection is always associated with a campaign: a distinct data set into which submitted form data is recorded.
Access, reporting and exporting of forms data is performed by campaign. Learn about how data is collected.
Each form has a Record Retention Policy that defines long form data will be kept.
For submitted records the default setting is 12 months. It means that the user data will be kept for 12 months from the moment the user clicks "Submit" button, after that the record with user data will be automatically deleted.
Make sure you adjust the Record Retention Policy to suit your business needs. It can be managed from the Form-level Properties interface in the Visual Designer.
Campaign data is read only: once a form is submitted it is locked and cannot be modified.
The only attribute that can be changed is the runtime state of a record, a special field that can store a custom state (see Assign Form State Workflows to learn how you can use this field).
Submitted data can be accessed in a variety of ways.
An Email Notification Workflow can be added to deliver form data to a specified email address.
You can configure the workflow to include the form data as formatted text in the body of the message or in an auto-generated PDF document attachment.
via the Form Data List
by Exporting Campaign Data
You can export all or parts of forms data, for any date range in XML and CSV formats. See How to Export Campaign Data.
The POST Webhook Workflow can send an HTTP POST notification to a specified URL address along with form data.
via the REST API
The REST API allows you to query metadata about your form definitions and campaigns and get access to all campaign data, including file attachments.