GetMyBot नॉलेज बेस

Saved event funnels

See how many people moved from viewing a product to paying, and where they stopped. Set up steps and read the report.

इस पृष्ठ पर

A funnel shows a customer's progress through steps. For example, 100 people viewed a product, 30 started checkout, and 10 paid. The report helps you find where people most often stop.

A funnel uses events the platform already collects. You choose their order and how long a person has to complete the steps. It can include different events, not only the reactions shown in the Analytics overview.

Build a funnel

Open Analytics → Funnels and create a funnel with two to twenty steps. Give each step a clear name and choose one or more alternative events. A step is complete when at least one of its events occurs.

You can narrow a step, for example to events from a selected audience segment. Choose whether to include known customers, anonymous visitors, or both. Select events, properties, and conditions from the available lists; you cannot write an arbitrary expression or field path here.

Step order is strict: a person reaches step 2 only after step 1, and so on. If events have the same timestamp, their stable stored order decides which came first. An event before the previous step does not complete the funnel.

Time, identity, and audience

Set the start (from) and end (to) of the report period in UTC. The start is included and the end is excluded. The period can be no longer than 366 days. Also set a conversion window, the time allowed to reach the next step: from one minute to 366 days. A later step outside the window is not counted.

The report counts people by a single canonical customer profile. If profiles were merged and the event source supports that merge, their events count as one person's events. Anonymous events follow the selected identity filter; they are not automatically assigned to a known customer.

Segment membership comes from the currently published segment when the report is requested. It is not a historical snapshot: changing a segment today can change today's report audience even if the event period stays the same.

Choose the conversion mode carefully:

  • All currently shows the person's first valid completion, the same as First. It remains for compatibility; counting every completion separately is not yet available.
  • First shows the person's first valid completion.
  • Repeat records later valid completions but does not yet show them in the report. Counts, breakdowns, and lists of people use one best completion per customer in every mode. This mode is not suitable for reporting repeat purchases yet.

Read the report

Each step shows the number of people, the share that reached it from the first and previous steps, the share that stopped, and the median time since the previous step. Median time means half of the people moved faster and half moved slower. A breakdown by event property shows at most 25 separate values; the rest are grouped under Other.

The daily chart uses UTC and covers the full selected [from, to) period. The first day may be partial; later days start at UTC midnight. Days without events show zeroes.

Warnings describe data characteristics, not statistical significance. zero_denominator means nobody reached the first step, so a completion rate cannot be calculated. high_cardinality_truncated means some breakdown values were grouped under Other after the first 25. There is no partial_data warning. When there is no one to divide by, the UI shows zero instead of an invalid percentage.

Cohorts and segments

Click a step's number to see the people who reached it. This group is a cohort. A panel opens with brief customer profiles and a paginated list. Sensitive and internal fields from the source events are not shown. In the API, a cursor indicates where to continue the list.

You can save people who completed or stopped at a step as a dynamic segment. Each time the segment is recalculated, the list updates using the selected funnel revision, step, date range, and optional breakdown filter. The platform stores these settings rather than a one-time list of people.

Revisions and safe editing

Each save creates a new revision, a version of the funnel settings. Older reports and segments can keep using a previous revision. If another team member saved a change first, reload the funnel or make a copy instead of overwriting their work. You can copy, archive, and delete a funnel; deletion is unavailable while another supported object refers to it.

API example

Use a personal access token with analytics:read for a report. Values below are placeholders, not real customer data or credentials.

curl -X POST "$BASE_URL/api/bots/$BOT_ID/funnels/$FUNNEL_ID/query" \
  -H "Authorization: Bearer $PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "revision": 3,
    "from": "2026-07-01T00:00:00Z",
    "to": "2026-08-01T00:00:00Z"
  }'

A stale edit returns 409 with funnel revision conflict; an invalid or unbounded range returns 400 or 422 depending on where validation fails. For a cohort request, send the same bounded range plus step_position, completed, limit, and the returned cursor on the next page. Creating a cohort segment also needs segments:write.