Live snapshot · Latest To Release

Events / 🎮 Engagement Analytics

level_start

ready

Spec

Doc fields save here and survive re-import. Name, status, parameters, and pipeline flags change through a ticket.

Add visual aid to description

png, jpeg, webp, or gif. 5 MB max. Alt text is required. This is not a QA screenshot.

Status is ready, introduced after 1.9.39. Firebase on, Adjust off (adj_level_start).

Open change ticket

Sheet statuses: draft, ready, implemented, verified, deprecated.

Edits

Nickname recorded with each doc save or comment. It is not a verified identity.

No edits recorded yet.

    Sheet notes

    • level_id, user_id, attempt_number (__ do we need this in level_start?__), timestamp
    • crnt_active_screen is reported as loading, should have been home
    • started_from · Need to add
    • session_quit_count · not attampt but app session count

    Parameters

    6 on this event

    ParameterTypeExamplesDescriptionFlags

    level_id

    Top values

    		unknown——FirebaseNo Adjust

    started_from

    Top values

    		enumlobby / retry / ..auto_start

    allowed: lobby · retry · ..auto_start

    		—FirebaseNo Adjust

    attempt_number

    Top values

    		number—fails+1 should be put in the value. Total attempts count for this level in all sessionsFirebaseNo Adjust

    session_quit_count

    Top values

    		string—for how many session was user failing the level before completing it. If the first level_start for this lvl was in this session, then 0 should be the parameter valueFirebaseNo Adjust

    pre_boosters_chief_level

    Top values

    		enum0/1/2/3/4/5

    allowed: 0 · 1 · 2 · 3 · 4 · 5

    		Pre level boosters from chief tools are used automatically, so we track them separately, sending the current "chief tools" levelFirebaseNo Adjust

    pre_boosters_manual_used

    Top values

    		enum[0/1,0/1] - [hammer, sandglass]

    allowed: 0 · 1,0 · 1 - hammer, sandglass

    		[hammer, sandglass] - it can be only 0 or 1, should not include auto used boosters from chief toolsFirebaseNo Adjust

    Add, remove, or rename parameters from a change ticket.

    Also on every event

    14 global parameters are sent with ALL EVENTS, including this one.

    • custom_user_id
    • user_id_acct
    • user_id_guest
    • online_status
    • custom_time_stamp
    • current_level
    • custom_app_version
    • custom_session_number
    • purchaser_user
    • lives_remaining
    • ab_test_assigned
    • config_version
    • custom_session_id
    • crnt_active_screen

    Version history

    Consecutive backup snapshots, plus rename and delete notes on the sheet. BigQuery 14-day counts annotate a row when the name matches. They do not create renames.

    Seen in BigQuery: 1.9.23 × 10,1031.9.39 × 101,2351.9.41 × 791.9.42 × 36

    VersionChangeDetails
    0.91 → release test 1Added1 parameters on introduction
    0.91 → release test 1Parameter addedlevel_id · BQ sample: 100 | 306 | 5 | 4 | 26 | 219 | 386 | 50
    2026.03.31 → 1.6.36Parameter addedstarted_from · Sheet example: lobby / retry BQ sample: lobby | retry | auto_start
    1.6.36 → 1.9.23Parameter addedattempt_number · BQ sample: 1 | 20 | 2 | 3 | 4 | 5 | 6 | 7
    1.6.36 → 1.9.23Parameter addedsession_quit_count · BQ sample: 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7
    1.6.36 → 1.9.23Parameter addedpre_boosters_chief_level · Sheet example: 0/1/2/3/4/5 BQ sample: 0 | 5 | 1 | 2 | 3 | 4
    1.6.36 → 1.9.23Parameter addedpre_boosters_manual_used · Sheet example: [0/1,0/1] - [hammer, sandglass] BQ sample: [0, 0]