The post_score event
post_score is a GA4 recommended gaming event for recording a player's score. You fire it when a score is achieved or submitted, passing a score value and optionally level and character. It supports analysis of skill distribution, leaderboard behavior, and how scoring correlates with progression and monetisation events across your player base.
What this means
post_score is a GA4 recommended gaming event. You fire it when a player posts or achieves a score, with the required score parameter and optional level and character to give the score context.
It is useful both for leaderboard-style games and for understanding how scoring relates to other events like level_up or spend_virtual_currency.
Score analysis
Examining the distribution of score values shows whether a game is well calibrated — heavy clustering at the low end may indicate excessive difficulty. Cross-referencing scores with level and monetisation events reveals whether high-skill players are also high-value players.
- score: the recorded score value
- level / character: optional context
- Pairs with progression and monetisation events
How it appears in analytics and logs
A post_score event means a player recorded a score. The score distribution reveals difficulty calibration and how players cluster by skill.
Diagnostic use case
Record player scores to analyze skill distribution and how scoring relates to progression and retention.
What WebmasterID can help detect
WebmasterID can capture scoring events first-party so skill and engagement analysis needs no third-party identifiers.
Common mistakes
- Omitting the score parameter that defines the event.
- Sending scores without level context for comparison.
- Attaching personal identifiers to score events.
Privacy and accuracy notes
score, level, and character describe gameplay, not the individual. Keep player PII out of these 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 unlock_achievement event
unlock_achievement is a GA4 recommended gaming event you fire when a player earns an achievement, identified by an achievement_id. Achievements are engagement and goal-completion signals: which ones unlock often, which are rarely reached, and how unlocking relates to retention. It complements progression events by capturing discrete milestones rather than continuous leveling.
- 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.
- Event Explorer
Analyze score distributions.
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.