Reviewing leads

In the admin: Leads — the screen this page documents (opens in the running app).

What/why: The lead lifecycle — what this screen manages and why it exists.

Purpose: give sales the full picture of every converted session — the needs-profile, the recommendation, the systems viewed, and (when scoring is on) the hot-lead flag. This screen is read-only: leads are captured by the public flow and synced to Eloqua; nothing is edited here.

When to use

• Following up on a lead: what did this buyer actually need and see?
• Segmenting recent conversions by date range, track, or hot-lead status.
• Checking how many current leads are flagged hot.

Prerequisites

• Admin access with the view_audit capability — the read-only tier that also covers Analytics and Audit; see admin access.

Steps

1. Open Admin → Leads (/admin/leads).
2. Each row is a converted session: its key guided-flow answers (the needs-profile), the recommended system, the systems the visitor viewed, and the hot-lead flag when hot-lead scoring is enabled.
3. Filter with the controls at the top — from/to date, track, and hot only. Filters are plain GET query params, so a segmented view is linkable and bookmarkable (same convention as Analytics and Audit).

Behavior guarantees

• Read-only by construction: the route exposes no mutating actions.
• What appears here is consent-gated at capture time — see privacy, consent & retention. To erase a lead's data on request, use Erasing visitor data.

Hot-lead scoring is configured on the Eloqua screen; the metrics behind conversion are in the behavioral metrics reference.