Skip to content

Missed Signups

Menu Location: Customers > Reports > Missed Signups

Overview

The Missed Signups report lists people who started your signup form, entering their name, email, and address on the first page, but never completed the process (or who completed it later under the same email address). The data comes from a background job that scans your server activity log for "signup completed page 1" events, so there is normally a short delay (up to a day) before a new missed signup appears here.

Primary Functions:

  • List everyone who submitted page 1 of signup without finishing
  • Show whether that person later became a customer under the same email
  • Export the list (current filter, or the entire table) as a CSV
  • Run a separate "Bot Report" view to spot likely bot/junk submissions

Page Layout

Header Section

  • Show only / Show all dropdown - "Show only missed signups" hides anyone whose email now matches an existing customer login; "Show ALL data" includes them too
  • Date Range - "From" / "To" date pickers filtering by when the signup attempt happened
  • Export ALL - downloads every matching row (ignores the date range, respects the Show only/Show all setting)
  • Export Page - downloads the rows for the current date range filter
  • Bot Report - switches the page to a separate view built for spotting bot traffic (see below)

Signup List Table

Displays each missed signup with:

  • Syslog ID - internal ID of the log entry the row was built from
  • Date / Time - when the signup attempt happened
  • Email - the email address entered
  • First Name / Last Name - as entered on the form
  • CustID - if this email now belongs to a customer account, shows a link to that customer; otherwise shows a dash

CSV Export Columns

Both export buttons produce: id, date, time, email, first name, last name, customer id.

The Bot Report View

Clicking Bot Report replaces the table above with a different, unfiltered view built from the 20 most recent signup-attempt log entries. It applies a simple heuristic to flag likely bot submissions: an entry is flagged when the street address entered is identical to the city entered, and the last name starts with the first name. For each entry it shows Syslog ID, Date, IP Address, first/last name, address, and city, with a "BOT" flag where the heuristic matched. Below that, three summary tables count how many flagged entries share the same IP address, first name, or city, which is useful for spotting a single source hammering the form with junk data.

This view does not use the date range filter or the Show only/Show all setting.

Automatic Recovery Email

Separately from this page, a background process periodically checks for new "signup completed page 1" events from the last 10-20 minutes. For each one that is not already a customer, it automatically sends the Missed Signup email template (editable on the Email Templates page) and enrolls the email in the "Missed Signups" drip campaign (managed under Drip Campaigns), if one is active for your tenant. This happens automatically in the background. There is no button on this page to manually select rows and send an email.

Common Use Cases

Use Case 1: Weekly Export for Outreach

Goal: Pull a fresh list of leads to follow up with manually

Steps:

  1. Set "Show only missed signups" so already-converted emails are excluded
  2. Set the date range to the period you want (e.g. the last 7 days)
  3. Click Export Page to download the CSV
  4. Load the CSV into your outreach tool of choice

Use Case 2: Check Whether Someone Already Converted

Goal: Confirm a specific missed signup went on to become a customer

Steps:

  1. Switch the dropdown to "Show ALL data" so converted rows are included
  2. Find the row by email
  3. If the CustID column shows a link instead of a dash, click it to open that customer's account

Use Case 3: Spot Bot or Junk Submissions

Goal: Rule out bot traffic before treating a spike in missed signups as real leads

Steps:

  1. Click Bot Report
  2. Review flagged ("BOT") rows and the repeat IP address / first name / city counts below the table
  3. A large count against one IP or one repeated name/city pattern indicates automated or junk submissions rather than real prospects

Troubleshooting

A lot of rows have obviously fake names or addresses

Use the Bot Report view (see above) to check whether these are being flagged by the built-in heuristic and whether they're clustering on a single IP address, first name, or city.

A new missed signup isn't showing up yet

The list is populated by a background job that processes the server log in batches, so a submission can take up to a day to appear. There is nothing to manually trigger from this page.

Someone says they never got a follow-up email

The automatic email only fires within a roughly 10-20 minute window after the signup attempt, and only if the address doesn't already belong to a customer. Check the Email Templates page for the "Missed Signup" template and, if your tenant uses one, the "Missed Signups" drip campaign under Drip Campaigns.

  • Missed Zip Codes - people who tried to sign up but their zip code isn't in your delivery area
  • New Signups - the latest customers who completed signup
  • Email Templates - edit the automatic "Missed Signup" email

Quick Reference Card

Task Action/Location
View missed signups Navigate to Customers > Reports > Missed Signups
Exclude already-converted emails Set dropdown to "Show only missed signups"
Include already-converted emails Set dropdown to "Show ALL data"
Filter by date Set the From/To date pickers, click Submit
Export current filter Click "Export Page"
Export everything Click "Export ALL"
Check for bot traffic Click "Bot Report"
See if a lead converted Look for a CustID link instead of a dash

FAQs

Does this report show me why someone abandoned signup?

No. It only records that the person submitted page 1 (name, email, address) and doesn't show which later step, if any, they reached.

Can I send a recovery email to selected rows from this page?

No, there's no send button here. An automatic email goes out on its own shortly after the signup attempt, as described above.

That email address now matches an existing login (users.username), meaning that person did eventually sign up, possibly after this record was captured.

End of Documentation

For additional help, contact your system administrator or Kiva Logic support.