Funnel step order determines which behaviours count as a journey from its beginning to an outcome. The presence of three events in a report does not establish that a customer performed them in the intended sequence. Someone may enter at the second screen, return to the offer or display confirmation again. Before drawing conclusions from the customer journey on the website, write the counting rules and check example paths rather than fitting the definition to a favourable result.
Define a step as a state or an action
Each step needs one meaning: viewing an offer, starting configuration or receiving confirmation that a request was accepted. Do not use one label for both selecting Submit and successful completion, because a failure can occur between them. Record which observation establishes each step and where that information comes from. If you only have a screen address, do not assign the meaning of a confirmed saved operation without checking how the application behaves.
In our fictional example, A means the offer, B configuration and C confirmation that the task was accepted. These are exercise definitions, not a ready-made scheme for every shop or form. The individual actions may be microconversions, but a funnel also needs their relationship and counting unit. If step C lacks a reliable signal, resolve that first instead of building precise sequence rules around an outcome you cannot verify.
Decide where the journey may begin
The start rule determines whether you count only people entering at A or also visits to B without an earlier offer view. Customers may have a saved configuration link and no need to revisit A. For the complete route from the offer, however, B → C does not demonstrate entry at the beginning. Document this distinction so an absent first step is not automatically classified as a lost customer or capture failure.
Prepare separate comparisons for starts at A and B if the data and tool support identifying those journeys. Do not combine their denominators afterwards under “offer conversion”. Show who entered the counted set and during which period for every result. “Open” and “closed” have meanings in particular reporting implementations, so write your definition in a full sentence and verify the available setting in the documentation of the tool being used.
Distinguish the next step from a later step
A direct relationship requires B to follow A according to the report’s rule. A relationship allowing intervening events permits other actions before the customer proceeds. Someone opening help between the offer and configuration may still belong in your intended route, but that needs an explicit definition. Check what the report considers an intervening event: a page change, any event or only the next defined action in the measurement.
Do not assume “in order” means absolutely no activity between stages. Write A → help → B → C and its expected classification, then compare that with the actual counting behaviour. If the tool lacks the relationship you need, explain the limitation or choose another available analysis. Do not attribute a funnel setting to Meetlead merely because a source about Google Analytics describes it and its name resembles your analytical objective.
Test five paths before reading the report
Five short paths expose most uncertainty about starts, order and repetition. For each one, write whether it enters the counted set and reaches completion under your rule. The table is neither a customer measurement nor a ready-made product report. It illustrates decisions to make before interpreting abandonment counts, especially where several different routes can reach the same final action and the screen sequence is not mandatory.
Scroll the table sideways to see all columns.
| Journey | Rule to decide | Illustrative decision |
|---|---|---|
| A → B → C | Complete ordered route | Counts for a funnel beginning at A |
| B → C | Entry midway | Does not count as entry at A; examine starts at B separately |
| A → C | Skipping B | Does not meet a required B; may represent another route |
| A → B → A → B → C | Returning | Counting depends on whether intervening events are allowed |
| A → B → C → C | Repeated confirmation | One completed journey if counting once per session |
A → C is not necessarily a customer failure: B may be unnecessary for a known configuration or genuinely missing from capture. Establish whether the task requires the step and then whether it was observed correctly. Record both explanations as questions to verify rather than selecting the favourable one. During a website conversion audit, this distinction prevents confusion between the design of the task and the definition of the report.
Google Analytics documents funnel exploration, including open and closed funnels and relationships between steps. These are Google Analytics capabilities; the definitions below do not imply equivalent settings in Meetlead.
Define how returns and repetitions count
A → B → A → B → C may reflect checking the offer before completion rather than two separate orders. Decide whether you count first entry, the last attempt or one outcome per chosen unit. Do not remove returns from behaviour analysis just because the summary counts a conversion once. They may reveal uncertainty or missing information during configuration, even when the eventual outcome is successful and the headline funnel appears healthy.
C → C may come from redisplaying confirmation and does not necessarily mean two completed operations. Compare events with the application’s actual result using appropriate information and permissions. The distinction between an action signal and its outcome also appears in PDF downloads versus link clicks. If you count one outcome per session, say so explicitly; if you count operations, you need reliable evidence that separate saved records actually exist.
Keep sessions distinct from people
The funnel unit changes what “the customer did not finish” means. A person may view the offer in one session and return to configuration the next day. A session funnel does not automatically join these moments into one journey, and equating sessions with people changes the result’s meaning. State the unit, date range and available identification method before discussing customer counts or the time taken to pass through the process.
Do not manually join anonymous visits by similar behaviour to improve the result. An unconfirmed connection should remain an analytical limitation. If the data describes sessions, report sessions and do not promise a complete history across devices. Separately check visits that started outside the reporting period, as they may appear only at later stages and affect how the denominator should be interpreted within the selected time window.
Reproduce the rules using available analysis
A practical check compares your definition with data you actually possess without inventing unavailable settings. In Meetlead analytics, inspect available journeys and defined, integrated goals. Review visits matching the examples and note which stages and returns are visible. If a report cannot compute your rule, retain it as a question for further analysis and name the available result according to the definition it actually implements.
Prepare a short funnel record containing the meaning of A, B and C, permitted starts, relationships, return handling and counting unit. Add the expected classification of the five examples so another person can detect a changed interpretation. Update the record after process changes and before comparing periods. Otherwise an improved result may simply reflect removal of a required step or altered counting rather than an easier task for the customer.
Questions about funnel step order
Should an optional action be a required funnel step? No, if you want to measure completion of a route that also works without it.
Analyse its use separately or compare different routes where the data permits. Making an optional step mandatory excludes valid completed tasks. Describe the process rules first, then choose the reporting definition.
Does returning to a previous screen mean abandonment? Not on its own. Check the subsequent journey and counting rules rather than stopping at one movement.
A return may precede successful completion or allow the customer to read information. Keep its behavioural meaning even when the funnel classifies the overall journey as complete.
