A landing page should help a visitor make one decision. Its form should be just as specific: collect the information needed for the next step and avoid questions nobody will use. ZoraForms stores submissions and UTM source data, while its dashboard helps you organize follow-up before a campaign produces more contacts.
Define what a lead means first
A demo request does not need the same data as a newsletter subscription. For a newsletter, email and consent may be enough; for a consultation, a name, company, and short need description can help. Every extra field adds effort. Start with the minimum that lets you reply usefully, rather than a form trying to replace a sales conversation.
Give fields clear labels and technical names such as email, name, company, and message. You will see these names later in submission details and exports. Do not add an upload field: ZoraForms does not support file uploads.
- One primary call to action on the page.
- Email as the required reply channel.
- Only questions needed for qualification.
- A clear statement of what happens after sending.
Store UTM data with the submission
A campaign URL can include utm_source, utm_medium, utm_campaign, utm_term, utm_content, and utm_id. To keep them, enable UTM inclusion in Integration and paste the updated form or fetch code. The code reads allowed parameters from the current page URL at submission time and adds them as hidden fields.
The mechanism does not store the full URL or use cookies to carry a first source between pages. Parameters must be present on the form page. Treat UTM values as campaign descriptions: never put email addresses, names, or other personal data in them.
https://example.com/demo?utm_source=linkedin&utm_medium=paid&utm_campaign=fallGive submissions a follow-up rhythm
After a test, open Submissions and inspect the fields and source section. Establish a simple queue: new, contacted, conversation in progress, closed. A status is not a CRM, but it keeps you from reviewing the same messages repeatedly. CSV or JSON export can pass data on, and a webhook can send an accepted submission to a system you already use.
Separate stored submissions from email notification. The dashboard remains the source of truth if a notification is delayed or filtered. ZoraForms does not provide a shared inbox or team conversation assignment; for several people, name a campaign owner and agree how a contact moves on.
- Send a test from a URL containing UTM values.
- Inspect the dashboard record before starting ads.
- Set a status after each next step.
- Export or use a webhook only where it is useful.
Set up email delivery, then assess the campaign
You can configure custom SMTP for sending customer conversations. Its connection test checks login, but does not prove inbox delivery. Customer replies return through an IMAP mailbox configured by the operator and the Reply-To header; you do not connect your own receiving mailbox to ZoraForms.
Compare campaigns by accepted submissions and the quality of the subsequent conversation, not clicks alone. Before more traffic arrives, check the plan limit and form protection. Free includes up to 100 monthly submissions, so the limit is part of campaign planning rather than an error to discover after launch.