6.1 Dashboard Overview

The Dashboard provides the first operational summary of activity within AIUNIFY Funnels.

It combines Landing Page counts, captured Lead information, Order information, revenue information, visitor-environment breakdowns, and recent form-collection activity into one workspace.

The Dashboard is most useful for answering questions such as:

  1. How many Landing Pages are currently associated with my account?
  2. How many form submissions have been captured?
  3. How many Orders are associated with my account?
  4. What browsers, operating systems, and device types are represented in my captured Lead activity?
  5. Has form-collection activity occurred during the recent seven-day period?

6.2 LandingPages Counter

The Dashboard calculates the Landing Page count from Landing Pages belonging to the authenticated user.

This makes the Landing Page counter an account-specific overview of the Landing Pages currently associated with your user account.

Use Landing Pages → My Landing Pages when you need to inspect the individual Landing Page records behind the total.

6.3 Leads Counter

The Lead total is based on captured form-data records belonging to the authenticated user.

A Lead record is created through the supported Landing Page form-submission workflow. The Dashboard count therefore provides a quick indication of how much form-collection activity has accumulated for your account.

For individual Lead records, submitted fields, source Landing Pages, visitor details, filtering, editing, deletion, and CSV export, use the dedicated Leads workspace described later in this manual.

6.4 Total Orders

The Dashboard calculates Total orders from Landing Page Orders associated with the authenticated user.

This number is an overview count. Use Ecommerce → Orders for individual Order records and for the supported Order-status and payment-status operations.

6.5 Revenu Metric

The current Dashboard interface includes a metric labeled Revenu.

The deployed controller calculates this value by summing the total of Landing Page Orders whose status is not CANCELED.

Important implementation note: unlike the Landing Page, Lead, and Total Order counters, the current Revenue calculation does not apply an explicit authenticated-user filter in the controller source. If the Revenue figure appears broader than the Orders you expect for your account, use the individual records in Ecommerce → Orders as the record-level reference and report an unexpected Dashboard total for review.

This distinction is important because the Dashboard should be used as an operational summary rather than as the sole accounting record for a transaction.

6.6 Browser Leads

The Dashboard groups captured form-data records belonging to the current user by Browser.

This can help you understand the browser environments represented among visitors who completed supported Landing Page forms.

Browser information is associated with captured form activity; it should not be interpreted as a complete count of every person who merely viewed a Landing Page.

6.7 OS Leads

The OS Leads reporting area groups the authenticated user's captured form data by operating system.

Use this information as a directional indicator of the environments used by visitors who reached the point of form submission.

6.8 Device Leads

The Device Leads reporting area groups the authenticated user's captured form data by device.

This information can help you determine whether your converted visitors are commonly arriving from different device categories and can inform the responsive testing you perform before publishing future Landing Pages.

6.9 Data Collectors in the Recent Seven-Day Period

The Dashboard constructs a recent seven-day collection series from captured form-data records belonging to the current user.

The application establishes a date range beginning seven days before the current date and counts collected form-data records by date within that range.

The chart is displayed when recent collection data exists. A lack of chart activity can therefore mean that there were no qualifying form-data records during the period.

6.10 What Dashboard Analytics Represent

Dashboard Area Confirmed Source
LandingPages Landing Pages belonging to the authenticated user.
Leads Captured form-data records belonging to the authenticated user.
Total orders Landing Page Orders belonging to the authenticated user.
Revenu Sum of non-canceled Landing Page Order totals under the current controller implementation.
Browser Leads User form-data records grouped by browser.
OS Leads User form-data records grouped by operating system.
Device Leads User form-data records grouped by device.
Recent collector activity User form-data records grouped by date across the recent seven-day range.

6.11 Analytics Are Not the Same as Raw Records

A Dashboard metric summarizes underlying data. When a number needs to be investigated, move from the summary to the applicable detailed workspace.

  1. Use My Landing Pages for individual Landing Pages.
  2. Use Leads for individual form submissions.
  3. Use Orders for individual Ecommerce Orders.

6.12 Recommended Dashboard Review Routine

  1. Open the Dashboard after signing in.
  2. Review your Landing Page and Lead totals.
  3. Review Total orders if your Landing Pages support Ecommerce.
  4. Review Browser, OS, and Device information for useful audience patterns.
  5. Review the recent collection trend for new Lead activity.
  6. Open the detailed Landing Pages, Leads, or Orders workspace whenever a summary requires investigation.

Operating principle: Use the Dashboard to identify activity and trends, then use the underlying records to confirm the details behind the numbers.

Write Your Comment