Forms & Lead Capture

Insights → Analytics → Form Analytics shows how your forms capture leads.

• Leads, New Leads, Converted and the Conversion Rate.
• Lead Sources: where people came from, from the UTM parameters and referrers on the links they used.
• Device Breakdown: phones, desktops and tablets.
• Lead Capture Trend: leads and conversions by day.
• Leads by Funnel and Recent Leads.
• Locations, where the data exists.

Add UTM parameters to the links you share and Gadura records them on the lead.

Example

your-site.gadura.site/webinar?utm_source=instagram&utm_medium=bio&utm_campaign=launch

The parameters

• utm_source: where (instagram, google, newsletter).
• utm_medium: how (bio, ad, email).
• utm_campaign: why (launch, sale).
• utm_term and utm_content for paid search and link variants.

Where it shows

Insights → Analytics → Form Analytics, under Lead Sources. Keep names lowercase and consistent; "Instagram" and "instagram" count separately.

The Device Breakdown in Form Analytics shows the share of leads from phones, desktops and tablets.

If most leads are on phones, keep forms to three or four fields, use large buttons, and test on your own phone. If desktop leads dominate, longer forms are fine. When mobile traffic is high but mobile conversion is low, the form is the problem.

Conditional logic shows or hides a field based on the answer to another.

Examples

• "Business or individual?" Business shows a Company Name field.
• "How did you hear about us?" Other shows a "Please specify" field.
• "Do you have a website?" Yes shows a Website field.

Why

Shorter-looking forms, only relevant questions, and better completion.

Where

In the website, landing page or funnel builder, select the form block, expand a field, and open Conditional Logic.

1. Edit the page and select the form block.
2. Expand the field to show or hide and open Conditional Logic.
3. Choose Show this field or Hide this field, and whether all rules or any rule must match.
4. Add a rule: the field to check, the operator, and the value.

Operators

Equals, does not equal, contains, does not contain, is empty, is not empty.

Example

On Company Name: show this field if all match; rule: type equals Business.

Tip

The field you check must come before the field it controls, and rules use the field's Name (ID), not its label.

• Keep the base form short and reveal the rest conditionally.
• Always show email and name; make company, phone and detail questions conditional.
• Test every combination yourself before publishing, and check a hidden required field cannot block submission.
• Two levels of conditions at most.
• Give fields clear Name (ID) values so rules are easy to read.
• The editor shows every field; use Preview to see the logic work.

1. Name (ID): rules use the field's Name (ID), not its label, and it is case-sensitive.
2. Order: the field you check must come before the conditional field, and must not itself be hidden.
3. Operator: equals needs an exact match; contains is not case-sensitive; is empty means no value at all.
4. All or any: with all, every rule must be true.
5. Preview: the editor shows all fields; test on the published page or in Preview.
6. Conflicts: show and hide rules on the same field fight each other. Keep one.

If it still misbehaves, remove the logic, save, and add it back.

• Ask only for what you need. Every extra field costs completions.
• Use conditional logic for the optional questions.
• Plain labels: "Email", "Phone (optional)".
• Put proof near the form: a subscriber count, a short testimonial.
• Do not require a phone number unless you will call.
• On phones: one column, large buttons, the email keyboard for the email field.
• A button that says what they get: "Send me the guide", not "Submit".
• A line of reassurance: "Unsubscribe any time."
• Read Form Analytics: which sources convert, and which devices struggle.