Lead Capture Form

Overview

By default, a rotator link opens WhatsApp immediately.
When Lead Capture Form is enabled, visitors see a form first, then get redirected to WhatsApp after submit.

Latest version includes:

• Core fields: name, phone, email
• Dynamic custom fields (up to 10)
• Custom field types: text, textarea, select, checkbox
• WhatsApp message token support: [k:key]

When Should You Use It?

Use Lead Form when you want to:

• Capture richer lead data before chat starts
• Measure ad traffic quality beyond WhatsApp clicks
• Inject visitor context into the first WhatsApp message

Quick Enable Steps

1. Go to WhatsApp > Rotator.
2. Create a new rotator or edit an existing one.
3. Select Form Link mode.
4. Enable the Lead Capture Form toggle.
5. Configure:
   • Form title
   • Description
   • Logo URL (optional)
   • Submit button label
6. Save the rotator.

Configure Form Fields

Core fields

• name and phone are always enabled and required.
• email can be enabled/disabled, and optionally required.

Custom fields

• Maximum 10 fields per rotator.
• Each field has a Key (field ID) that must be:
  • unique
  • snake_case
  • not a system key

Use Tokens in WhatsApp Message

In your rotator message template, you can use:

• [uniquecode] for the visitor unique code
• [k:key] for custom field values

Example:

Hi team, I want to discuss.
Budget: [k:budget]
Need: [k:service_need]
Code: [uniquecode]

If a custom field value is missing/empty, token output becomes an empty string.

Rotator Custom URL Params with k_*

Besides form.custom_fields, you can also pass context from URL query params using the k_ prefix, for example:

• ?k_budget=50jt
• ?k_channel=meta
• ?k_product=premium_plan

k_* values will:

• Be stored in lead custom fields with stable keys (for example k_budget)
• Appear in CSV export as cf_k_budget
• Be usable in WhatsApp message templates in two token styles:
  • [k:k_budget] (full key)
  • [k:budget] (automatic alias from k_budget)

If a token has no value, output stays an empty string.

If you want k_* to be auto-forwarded when users click rotator/form links from pages that already contain query params (without manually appending query on every link), enable this tracker option:

konektor('init', 'WS-XXXX', {
  crossDomain: {
    autoLink: true,
    forwardKParams: true
  }
})

Link Format

• Direct WhatsApp link (no form): domain.com/wa/[slug] or domain.com/[slug] (depends on domain setup)
• Form link: domain.com/form/[slug]

Where Is Data Stored?

• Lead data is saved to Leads as usual.
• Custom fields are stored securely.
• Custom fields appear in Lead Detail.
• When exporting leads to CSV, custom fields are included as cf_<key> columns.
• In the lead list page, only core data is shown. Open Lead Detail or the export file to view custom fields.

Permission & Access

• Only workspace owners (owner) and admins can create, update, or delete rotators.
• Team members (staff) can only view lead details assigned to them.

Recommended Implementation Checklist

1. Enable Lead Form on one rotator first (pilot).
2. Add 2-3 high-value custom fields.
3. Add [k:key] tokens to message template.
4. Submit test from /form/[slug].
5. Verify:
   • WhatsApp redirect works
   • Custom fields appear in lead detail
   • Message tokens are replaced correctly

Troubleshooting

Do I need to update the tracking script?

• No, not required for Lead Capture Form + rotator custom fields.
• As long as your traffic uses /form/[slug], custom fields will work without tracking script changes.
• Tracker updates are still recommended for broader website tracking improvements (e.g., UTM/cross-domain), but they are not a strict requirement for this feature.

Form cannot be submitted

Common causes:

• Required field is empty
• Duplicate custom field key
• select value is not in the available options
• checkbox value is not Yes/No

[k:key] token not filled

Check:

• Token key exactly matches field key
• Field is active
• User actually submitted a value (empty maps to -)

Current Limits

• Custom fields are shown in Lead Detail and included in CSV export (cf_<key>)
• Max 10 custom fields
• Supported types only: text, textarea, select, checkbox