Funnels

A funnel counts how many visitors go through a series of steps, in order, within a time window, and where they drop off.

Three kinds of steps

Step	Example
Page	Path /checkout/shipping, or a pattern like /p/*
Event	add_to_cart, purchase, form_submit, with optional property filters
Element	A click on a button, chosen by its data-ah-name (add-to-cart) or its CSS selector (div.slot-picker)

Element steps are what make Eureka funnels "real": you measure the actual click on Add to cart or Pick a delivery slot, not just the page that follows.

Build a funnel

1. Open Explore → Funnel exploration.
2. Add steps. For an element step, the element picker lists every element clicked on your site, with its clicks by agents and humans; search by text or name.
3. Choose the window (for example 1 hour) and whether steps must follow each other directly (closed funnel) or not (open funnel).
4. Choose a breakdown: by actor family (agents vs humans vs bots) or by navigation mode (agent / human / mixed sessions).
5. Save it to reuse it in reports, dashboards, the API and the MCP server.

Read it

For each step: visitors who reached it, conversion from the previous step and from the first one, and the median time between steps. With the actor breakdown, the friction points that hurt agents stand out. In the demo, for example, about 90% of humans who reach the delivery-slot step pick a slot, against about 25% of agents, who click the slot picker several times before giving up.

Name your key buttons

Ask your developers to add data-ah-name="…" to the buttons in your funnels. The name stays the same through redesigns, so your funnels keep working. See Autocapture and element naming.