33.1 Leads Workspace Overview

The authenticated Leads workspace is where AIUNIFY Funnels presents information collected through supported Landing Page forms.

Use this workspace to review submitted Lead information, identify its source, search records, filter Landing Page results, edit Lead fields, delete records, and access CSV export when available.

33.2 Opening Leads

Select Leads from the authenticated AIUNIFY Funnels navigation.

The Leads routes require an authenticated user session.

33.3 User-Specific Lead Listing

The confirmed Leads data query begins with Lead/FormData records whose user_id matches the currently authenticated user.

The Landing Pages offered in the Landing Page filter are also loaded from Landing Pages belonging to the authenticated user.

33.4 Main Leads Table Columns

The confirmed Leads screen displays these table headings:

Lead Info Displays the submitted form field names and their corresponding values.
From Identifies the source Landing Page and provides a link to its Landing Page Settings when the relationship is available.
Browser Displays the browser family recorded with the Lead.
OS Displays the recorded operating-system/platform family.
Device Displays the recorded device classification.
Dates Displays Created and Modified dates.
Action Provides the Lead-management operations available for the record.

33.5 Understanding Lead Info

The Lead Info column is generated from the Lead record's stored field_values.

Each stored field key and value is displayed as part of the Lead information.

Because Landing Pages can contain different form structures, Lead Info does not have to contain the exact same fields for every Landing Page.

33.6 Understanding From

For a Lead whose type is landingpage, the From column uses the associated Landing Page information.

When the Landing Page relationship is available, the source name links to the Landing Page's Settings screen.

This provides a useful way to move from a captured Lead back to the campaign that generated it.

33.7 Browser Information

The Browser column displays the browser family stored during form submission.

This information can help you understand the types of browsing environments producing conversions.

33.8 Operating-System Information

The OS column displays the operating-system or platform family stored with the Lead.

Reviewing OS information alongside Device information can help identify how visitors are interacting with the campaign.

33.9 Device Information

The Device column displays the device classification produced by the application's tracking workflow.

If a campaign produces substantial activity from a particular device type, use that information as one input when reviewing responsive Landing Page design.

33.10 Created and Modified Dates

The Dates column displays both:

  1. Created — when the Lead record was created.
  2. Modified — when the Lead record was last updated.

If you edit a Lead, the Modified date may therefore differ from the original Created date.

33.11 Newest Records Are Requested First

The confirmed Lead data query orders records by created_at in descending order.

This places the newest captured records first in the normal data request before DataTables presentation behavior is applied.

33.12 Searching Lead Information

The Leads interface provides a search control identified by the placeholder:

Search lead info

The server-side Lead search applies the entered search value against the stored field_values content.

Useful searches can therefore include recognizable information submitted by the visitor, such as a name, email address, phone value, company name, or another stored form value.

33.13 Landing Page Filter

The Leads interface contains a Landing Page filter whose default option is:

All landing pages

The remaining options are built from the authenticated user's Landing Pages.

Selecting a Landing Page filters the Lead query by:

  1. The selected Landing Page's internal source ID.
  2. The source type landingpage.

33.14 When to Use All Landing Pages

Use All landing pages when you want to review Lead activity across the available Landing Page campaigns together.

This is useful for general monitoring or when searching for a Lead and you do not yet know which Landing Page captured it.

33.15 When to Filter to One Landing Page

Filter to a specific Landing Page when you want to:

  1. Review one campaign's Leads.
  2. Compare captured information with that page's current form.
  3. Clean up campaign-specific test Leads.
  4. Investigate a campaign-specific conversion issue.

33.16 Optional Popup Filtering

The source also contains optional Popup integration support. When the Popup module is installed, the Leads interface can add an All popups filter and include Popup-generated records.

This manual remains focused on AIUNIFY Funnels Landing Pages. If that optional module is not part of your deployed user experience, the Popup filter will not be relevant to normal Funnels operations.

33.17 Action Operations

Each Lead's Action area provides:

Edit Opens the Lead record for field editing.
Delete Starts deletion of the selected Lead record.

Editing is covered in Chapter 34. Deletion and CSV export are covered in Chapter 35.

33.18 Delete Confirmation

The Leads interface defines the deletion confirmation message:

Confirm Delete?

Verify the selected record carefully before confirming deletion.

33.19 Export All

The top of the Leads screen contains an Export all action.

CSV export behavior and its available page-scoping behavior are covered in Chapter 35.

33.20 Leads and Dashboard Analytics Serve Different Purposes

The Dashboard summarizes Lead activity through counts and charts, while the Leads workspace exposes the individual captured records.

Use the Dashboard for high-level activity review and use Leads when you need to inspect or manage the actual submitted information.

33.21 Recommended Daily Lead Review

  1. Open Leads.
  2. Review the newest records.
  3. Use All landing pages for an overall review.
  4. Filter to a specific Landing Page when investigating one campaign.
  5. Use Search lead info to locate a particular submitted value.
  6. Review the source Landing Page through the From link when necessary.
  7. Edit a Lead only when stored information genuinely needs correction or augmentation.
  8. Export data that must be retained before destructive cleanup operations.

Operating principle: Use the Leads workspace as the record-level view of Landing Page conversions: search the submitted data, filter by campaign, review source and device information, and preserve important records before deleting anything.

Write Your Comment