> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/form-guard/analytics.md). # Analytics Use **Form Guard Analytics to** **track form performance**, **review blocked leads, and recover missed** **opportunities** across every Form Guard in your account. Analytics is account-wide, so it aggregates activity from all guards into one shared view with trends, breakdowns, and lead-level detail your team can act on. ## Accessing Analytics Navigate to the [Form Guard list](https://app.clearout.io/form-guard/list) in your Clearout dashboard. At the top of the list page, find the row of summary metric cards and click **VIEW ANALYTICS** on the right.

{% hint style="info" %} **Live data for Today** When your date range is set to **Today**, a *Live Data* badge will appear. Use the **Refresh** button to pull the latest real-time numbers. Other date presets show compiled totals up to the last systematic refresh {% endhint %} ## Analytics Core Tabs Once inside the analytics dashboard page, use the side tab bar to jump between the three core areas: * [**Overview**](https://app.clearout.io/form-guard/analytics): Monitor macro trends, field-level frictions, overall traffic quality, and page-level performance. * [**Form Forensics**](https://app.clearout.io/form-guard/analytics/form-forensics): Look up individual leads to investigate exactly why a specific submission was allowed or blocked. * [**Lost Leads**](https://app.clearout.io/form-guard/analytics/lost-leads): Review, analyze, and export real **pre-verified leads** that were blocked or abandoned before reaching your CRM.

## Filters & Main Scorecard ### Global Filters The controls located above the **performance summary** manage your entire view across the active Analytics tab.

Control	What it does
Date range picker	Switch between presets like Today, Yesterday, This week, Last 7 days, Last week, This Month, Last Month, Last 30 Days, This Year, and Last Year, or choose a custom range. All Analytics sections refresh when this changes.
Refresh	Fetches the data again for the selected date range. The nearby timestamp shows the last fetch time.
Export CSV	Downloads the current Analytics view as a CSV file named for the active date range.

### Form Monitor The Form Monitor is the primary scorecard at the top of the Overview tab, providing five core metrics at a glance alongside period-over-period delta percentages.

Metric	What it means
Forms Submitted	Completed submissions processed by Form Guard. The sub-label reveals how many visitors started the form alongside your Abandonment Rate.
Validations	The total number of individual form fields checked (across email, phone, and name) during the selected period.
Blocked	Submissions flagged as risky, fake, or invalid and stopped before they could reach your CRM. The sub-label displays your overall Block Rate.
Allowed	Clean, high-quality submissions that successfully passed every enabled validation check.
Avg Fill Time	The average duration visitors spent filling out the form. Use this to quickly spot robotic behavior (instant fills) or confusing form layouts (abnormally long fill times).

Each card also shows a period-over-period delta. Use it to spot changes quickly.

{% hint style="info" %} **What counts as a visitor?** A unique visitor is any browser session that loaded a page with your Form Guard script and performed some action on the form. **Forms Submitted** and **Validations** metrics only count visitors who engaged with the form {% endhint %} ## Traffic & Lead Quality Insights ### Lead Quality Breakdown This section helps you break down exactly why submissions were allowed or blocked by merging two critical visual widgets: #### Block Composition The donut chart splits total blocked submissions across three validator categories: * **Email**: Failures due to invalid formatting, disposable domains, free/role-based addresses, gibberish strings, or catch-all setups. * **Phone**: Failures caused by invalid numbers, blocked line types (e.g., premium/voip restrictions), or restricted countries. * **Name**: Failures triggered by invalid characters, obvious gibberish, or profanity filter hits. The donut center shows the total blocked count. The legend shows each category's share. A badge in the card header shows the overall block rate.

#### Top Reasons Ranks the top five reasons behind blocked or allowed submissions. Use the toggle to switch between **Blocked** and **Allowed**. Use the filter pills for **All**, **Email**, **Phone**, or **Name**. Click **View More** to expand the full list. Click any row to open **Form Forensics** with that reason pre-filtered.

### Visitor & Traffic Insights This section helps you separate traffic quality from traffic volume. It combines **Unique Visitors** and **Countries**. #### Unique Visitors The chart shows unique visitors across the selected date range. The time scale adjusts automatically for the selected period. Look for these patterns: * **Sudden spikes** - often due to a new campaign or a bot wave. * **Flat or zero traffic** - often a sign that the Form Guard script is not loading.\

#### Countries The countries card ranks the countries that drive the most submissions. Toggle between **Blocked** and **Allowed** to compare suspicious traffic with genuine demand. Each row shows the country flag, country name, validation count, and share of the total.

{% hint style="success" %} **Act on country trends** If a country shows a high number of blocked submissions, it helps you identify where most low-quality or unwanted leads are coming from. You can use these insights to optimize your GTM strategy, targeting, and campaign efforts accordingly. {% endhint %} ### Page Insights **Page Insights** breaks activity down by page URL.

Column	What it shows
Page URL	The full page URL where Form Guard was triggered.
Validations	Total validations on that page.
Allowed	Validations that passed on that page.
Blocked	Validations blocked on that page.
Block Rate	Number of Blocked divided by Number of validations for that page.

Every column is sortable. Use the URL filter when a guard runs across many pages. {% hint style="info" %} **How to read block rate** A high block rate usually points to one of three things: bot traffic, a strict rule, or a broken form flow. Check **Form Forensics** before changing your guard settings. {% endhint %} ## Form Forensics (Lead Lookup) [**Form Forensics**](https://app.clearout.io/form-guard/analytics/form-forensics) is your granular lookup tool to answer a single question: *What exactly happened to this specific lead?*

### Searching for a lead Search by **email address**, **phone number**, or **name**. Form Forensics detects the input type and returns matching validation history for the selected date range.

Column	Description
Lead	The input value.
Verdict	Whether the input value was allowed or blocked.
Reason	The specific reason behind the verdict.
Page URL	The page where the validation happened.
Country	The visitor's country.
Time	Relative time and exact timestamp.

{% hint style="info" %} The search box performs a case-insensitive partial match across all lead data, including email, phone, and name. Enter any fragment to find matching records without needing a full email, name or phone number. {% endhint %} ### Drilling in from Lead Quality Click any reason in **Top Reasons** to open **Form Forensics** with that reason already applied. Clear the reason chip to return to the free-text search.

### Exporting Use **"Export Leads"** to download the current result set as CSV. ## Lost Leads (Recovery Workflow) A **lost lead** is a high-intent visitor who entered a fully valid email or phone number but never made it to your CRM because they abandoned the form midway or were blocked due to a secondary field failure Use [Lost Leads](https://app.clearout.io/form-guard/analytics/lost-leads) to recover real pre-verified leads that were blocked or abandoned before they reached your CRM. {% hint style="warning" %} **Data Retention Policy**: Lost leads are retained on a rolling **30-day window**. Because older lead data goes cold quickly, expired records are permanently purged. We highly recommend mapping out a frequent export schedule.at the table shows {% endhint %}

Column	Description
Name / Email / Phone	The values the visitor entered before leaving or being blocked.
Intent	Blocked (Form Guard rejected the final submission) or Abandoned (the visitor dropped off mid-funnel).
Attempts	How many submission attempts the visitor made.
Page URL	The page where the activity happened.
Time	Relative time and exact timestamp.

### Recovering a lead Common recovery workflows include: * **Email follow-up**: Contact leads who entered a usable address. * **Phone follow-up**: Prioritize leads with reachable numbers. * **Fix the block** - review the case in [**Form Forensics**](https://app.clearout.io/form-guard/analytics/form-forensics), then update [**Advanced Settings**](/form-guard/advanced-settings.md) if a real lead was blocked by mistake. ### Date range and export The **Lost Leads** uses its date range picker. Each query is limited to a maximum 30-day span for optimal performance. Use **Export CSV** to download your current view and archive your leads before they age out of the system {% hint style="success" %} **Make Lost Leads a daily workflow** Many teams review yesterday’s blocked and abandoned leads each day, recover the real ones, and use the patterns to refine their GTM strategy. {% endhint %} ## Related * [Form Guard Overview](https://docs.clearout.io/form-guard/overview): Learn what Form Guard does and how to install it on your site. * [Advanced Settings](https://docs.clearout.io/form-guard/advanced-settings): Configure the rules and filters that shape the verdicts shown in Analytics. * [Email](https://docs.clearout.io/form-guard/email-field-validation), [Phone](https://docs.clearout.io/form-guard/phone-field-validation), and [Name Field Validation](https://docs.clearout.io/form-guard/name-field-validation): Dive deeper into the specific validator rules behind each allowed or blocked response. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.clearout.io/form-guard/analytics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.