The level_start event
level_start is part of GA4's recommended events for games. You fire it when a player begins a level or stage, passing a level_name parameter. Paired with level_end, it lets you measure how many players start versus finish each level — the core of game progression and difficulty analysis. Like all recommended events, its documented name plugs into GA4's gaming-oriented reporting.
What this means
level_start is a GA4 recommended event in the gaming set. You send it when a player enters a level, with level_name identifying which level began. Because the name is recognised by GA4, it feeds the platform's progression reporting alongside other gaming events.
The complementary level_end event records the end of the same level, so the two together form a per-level funnel.
Progression analysis
Counting level_start versus level_end per level_name shows where players stall. A level where many start but few reach level_end with success=true is a candidate for rebalancing. Adding level_up and post_score events around these builds a fuller picture of engagement and difficulty.
- level_name: identifies the level that started
- Pairs with level_end for completion rate
- Feeds GA4 gaming progression reports
How it appears in analytics and logs
A level_start event means a player began a level. A widening gap between level_start and level_end for a stage flags a difficulty or drop-off problem.
Diagnostic use case
Measure how many players start each level and build a progression funnel against level_end completions.
What WebmasterID can help detect
WebmasterID can record progression events first-party so game funnels work without third-party identifiers.
Common mistakes
- Sending inconsistent level_name values for the same level.
- Tracking starts but not ends, so completion can't be computed.
- Putting player IDs into level parameters.
Privacy and accuracy notes
level_name describes game content, not the player. Keep player identifiers and PII out of gaming event parameters. Educational, not legal advice.
Related pages
- The level_end event
level_end is the completion counterpart to level_start in GA4's recommended gaming events. You fire it when a player finishes a level, with level_name identifying the level and a success boolean indicating whether they completed it. Comparing level_end (success=true) against level_start per level gives a completion rate, the foundation of difficulty tuning and progression analysis.
- The level_up event
level_up is a GA4 recommended gaming event for character or account progression — distinct from completing a stage. You fire it when a player advances a level, passing a level number and optionally a character parameter. It measures long-run progression and retention depth, answering how far players advance rather than whether they finished a single stage.
- Recommended vs custom events
GA4 events come in three tiers: automatically collected, recommended, and custom. Automatic events fire without setup; recommended events have Google-defined names and parameters that unlock standard reports; custom events are ones you invent. The practical rule is to prefer a recommended name whenever one fits, because custom names miss out on prebuilt dimensions, reports, and predictive features.
- Event Explorer
Inspect level progression events.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.