35.1 Lead Deletion and Export Overview

AIUNIFY Funnels provides two important record-management operations in the Leads area:

Delete	Removes an individual Lead/FormData record.
Export all	Downloads available Lead/FormData information as a CSV file, subject to the account's available features.

Because deletion removes stored information, consider export and retention requirements before deleting important Lead records.

35.2 Deleting a Lead

Each Lead record has a Delete action in the Action area.

The Leads interface defines the confirmation prompt:

Confirm Delete?

Confirm only after verifying that the correct Lead has been selected.

35.3 What the Delete Operation Does

The confirmed delete workflow validates that a Lead ID was supplied, finds the corresponding FormData record, and deletes that record.

After the delete request completes successfully, that FormData record is no longer available through the normal Leads listing.

35.4 Treat Delete as Destructive

The normal Lead delete controller performs a delete operation on the selected FormData record.

The confirmed user workflow does not provide a separate restore step as part of that deletion request.

Important: Export information that must be retained before deleting it.

35.5 Deleting One Lead Is Different from Deleting Its Landing Page

Deleting an individual Lead removes that selected Lead record.

Deleting an entire Landing Page has a broader consequence: the Landing Page model's deletion workflow also deletes the related Landing Page FormData records.

If a campaign is being retired, review and export the applicable Leads before deleting the Landing Page itself.

35.6 Export All

The Leads workspace provides the button:

Export all

The export operation creates a CSV file from Lead/FormData records belonging to the authenticated user.

35.7 Export Is User-Scoped

The confirmed CSV export query begins with FormData whose user_id matches the authenticated user's ID.

This is separate from the public form-submission process and requires authenticated access through the Leads workflow.

35.8 Landing Page-Specific Export Support

The export controller supports a landingpage_code parameter.

When a Landing Page code is supplied, AIUNIFY Funnels resolves that Landing Page and limits the export data to:

1. That Landing Page's source ID.
2. Records whose type is landingpage.

When no Landing Page code is supplied to the export request, the standard export begins from the authenticated user's available FormData records.

35.9 Do Not Assume the On-Screen Filter Automatically Changes Every Export

The Leads table uses a Landing Page ID filter for the on-screen DataTables query, while the export controller supports Landing Page scoping through a Landing Page code parameter.

For operational accuracy, confirm the scope of the downloaded CSV itself rather than assuming that every visible screen filter has automatically changed the export request.

35.10 CSV File Name

When data is available, the application creates a file name in this pattern:

formdata-[timestamp].csv

The timestamp portion is generated at export time.

35.11 CSV Columns Are Built from Actual Lead Field Names

AIUNIFY Funnels examines the field_values keys contained across the records being exported.

It combines those field names into the CSV column set and removes duplicate column names.

This design allows Leads captured from forms with different field structures to be represented in the same export.

35.12 Why Consistent Form Field Names Matter

If multiple Landing Pages use different names for conceptually identical information, the export can contain separate columns.

For example:

phone	One CSV column.
phone_number	A different CSV column.

Standardize important form field names across campaigns when you want cleaner consolidated exports.

35.13 Missing Values Become Blank CSV Cells

For each exported Lead, AIUNIFY Funnels iterates through the complete CSV column list.

If that Lead does not contain a value for a particular column, the application writes an empty value for that cell.

This keeps the CSV rows aligned even when different Landing Pages collect different information.

35.14 The First CSV Row Contains the Field Names

The export operation writes the collected field names as the CSV header row before writing the Lead values.

This makes the downloaded file suitable for opening in spreadsheet software or importing into another system that accepts CSV data.

35.15 Temporary Export File Cleanup

The application creates the CSV file for the download and configures the response to delete that temporary server-side file after it has been sent.

Your downloaded copy remains your responsibility after the browser receives it.

35.16 When No Export Data Exists

If the export query does not find any records, AIUNIFY Funnels returns to the previous screen with:

Not found any data for export

If you receive this message, confirm that Leads exist for the intended user and export scope.

35.17 Export Availability Can Be Feature-Gated

The current source includes optional SaaS billing behavior around Lead CSV export when the SaaS module is present.

The application's package feature definitions also identify:

Form data export csv

For that reason, CSV export may depend on the features available to the user's account or package in a deployment where those billing controls are active.

35.18 Protect Exported Lead Data

A CSV export can contain prospect or customer information collected through your Landing Pages.

After downloading it:

1. Store it only where authorized users can access it.
2. Avoid leaving unnecessary copies on shared devices.
3. Follow your organization's data-retention requirements.
4. Remove obsolete copies when they are no longer required.

35.19 Export Before Major Campaign Cleanup

Export Lead data before operations that may remove valuable campaign information, especially:

1. Deleting individual Leads in bulk over time.
2. Deleting a Landing Page whose Lead history must be preserved.
3. Retiring an important campaign.

35.20 Recommended Lead Deletion Workflow

1. Open Leads.
2. Search for or filter to the intended Lead.
3. Review its Lead Info and From source.
4. Determine whether the information must be retained.
5. Export the applicable data first when retention is required.
6. Select Delete.
7. Review Confirm Delete?.
8. Confirm only when the correct record is selected.
9. Verify that the intended Lead is no longer in the normal listing.

35.21 Recommended CSV Export Workflow

1. Open Leads.
2. Determine whether you need a general export or a Landing Page-specific export context.
3. Select Export all using the intended export scope.
4. Open the downloaded CSV.
5. Confirm the expected field-name columns.
6. Confirm the expected Lead records are present.
7. Confirm differently structured forms have aligned correctly with blank cells where appropriate.
8. Store the file securely.

Operating principle: Export before destructive cleanup, verify the scope and contents of every CSV, and treat downloaded Lead information as business data that must be protected appropriately.