Live snapshot · Latest To Release
Events / 🎮 Engagement Analytics
level_complete_x
deprecatedSheet text: level_complete_X (27, 100 etc) - check and remove if we still send event with such name
Spec
Doc fields save here and survive re-import. Name, status, parameters, and pipeline flags change through a ticket.
Status is deprecated, introduced after 1.9.39. Firebase on, Adjust on (adj_level_complete_x).
Open change ticketSheet 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
- remove from normal analytics
- (27, 100 etc) - check and remove if we still send event with such name
- or maybe it's adjust event?
- level_id · remove from normal analytics
- end_boosters_used · not attampt but app session count
- started_from · Need to add
Parameters
13 on this event
| Parameter | Type | Examples | Description | Flags |
|---|---|---|---|---|
Top values | unknown | — | — | FirebaseNo Adjust |
Top values | number | — | how many seconds did it take to complete the level on this particular attempt where user won | FirebaseNo Adjust |
Top values | string | — | fails+1 should be put in the value. Attempts taken to complete the level | FirebaseNo Adjust |
Top values | number | 1 | 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 value | FirebaseNo Adjust |
Top values | enum | 0/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" level | FirebaseNo Adjust |
Top values | enum | [1,0,2,1] - ([vacuum,spring,fan,ice]) allowed: 1 · 0 · 2 · 1 - vacuum · spring · fan · ice | numbers should be for each booster in this order | FirebaseNo Adjust |
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 tools | FirebaseNo Adjust |
Top values | enum | [vacuum,spring,fan,ice,hammer,sandglass,clear_bar,extra_time] allowed: vacuum · spring · fan · ice · hammer · sandglass · clear_bar · extra_time | total number of boosters spent on the level (including failed attampts), in this order | FirebaseNo Adjust |
Top values | enum | - 1/2/3 allowed: - 1 · 2 · 3 | how many stars gained | FirebaseNo Adjust |
Top values | boolean | 0/1 allowed: 0 · 1 | if user purchased something for real money on this particular attampt | FirebaseNo Adjust |
Top values | enum | 0/1/2/.. allowed: 0 · 1 · 2 · .. | total real money spent (in dollars) from all the attempts for this level (all spending since the previous level_complete) | FirebaseNo Adjust |
Top values | integer | integer | what percentage of total items in the level was matched and taken out of board/stack | FirebaseNo Adjust |
Top values | enum | lobby / retry / ..auto_start allowed: lobby · retry · ..auto_start | — | FirebaseNo 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
Validation
- warningDeprecated event “level_complete_x” is still routed to Firebase and Adjust.
- warningDescription contains a likely typo. “total number of boosters spent on the level (including failed attampts), in this order” → “total number of boosters spent on the level (including failed attempts), in this order”.
- warningParameter “shop_purhcase” looks like a typo. Did you mean “shop_purchase”?
- warningDescription contains a likely typo. “if user purchased something for real money on this particular attampt” → “if user purchased something for real money on this particular attempt”.
- warningParameter “items_clreaded_perc” looks like a typo. Did you mean “items_cleared_perc”?
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.
Not seen in the BigQuery 14-day extract.
| Version | Change | Details |
|---|---|---|
| 1.6.36 → 1.9.23 | Deleted | First seen already deprecatedsheet note |
| 1.6.36 → 1.9.23 | Parameter added | level_id |
| 1.6.36 → 1.9.23 | Parameter added | completion_time |
| 1.6.36 → 1.9.23 | Parameter added | attempt_number |
| 1.6.36 → 1.9.23 | Parameter added | end_boosters_used · Sheet example: 1 |
| 1.6.36 → 1.9.23 | Parameter added | pre_boosters_chief_level · Sheet example: 0/1/2/3/4/5 |
| 1.6.36 → 1.9.23 | Parameter added | boosters_used · Sheet example: [1,0,2,1] - ([vacuum,spring,fan,ice]) |
| 1.6.36 → 1.9.23 | Parameter added | pre_boosters_manual_used · Sheet example: [0/1,0/1] - [hammer, sandglass] |
| 1.6.36 → 1.9.23 | Parameter added | boosters_used_total · Sheet example: [vacuum,spring,fan,ice,hammer,sandglass,clear_bar,extra_time] |
| 1.6.36 → 1.9.23 | Parameter added | stars_gained · Sheet example: - 1/2/3 |
| 1.6.36 → 1.9.23 | Parameter added | shop_purhcase · Sheet example: 0/1 |
| 1.6.36 → 1.9.23 | Parameter added | total_shop_purchases · Sheet example: 0/1/2/.. |
| 1.6.36 → 1.9.23 | Parameter added | items_clreaded_perc · Sheet example: integer |
| 1.6.36 → 1.9.23 | Parameter added | started_from · Sheet example: lobby / retry / ..auto_start |