md2link

Analytics Events — by Screen

DraftMay 14, 2026

Analytics Events — by Screen

Snapshot of all analytics events the app currently sends. Updated: 2026-05-14

Total: 20 events across 10 screens


1. Main screen (bottom navigation)

Event Parameters When it fires
view_home User selects the Home tab
view_discovery User selects the Explore tab
view_architects User selects the Architects tab

2. Home screen

Event Parameters When it fires
click_home_story User taps a story group at the top of Home
click_home_feed style User taps a style in the "new feed" section
click_home_banner style User taps a style on the hero banner
click_template display_type, style User selects a style from a category grid

3. Story Viewer

Event Parameters When it fires
click_story_template style User selects a style while viewing a story

4. Explore — Style Detail

Event Parameters When it fires
view_explore_style Style detail screen opens

5. Select Photo

Event Parameters When it fires
view_add_photo Photo-selection screen opens

6. Crop

Event Parameters When it fires
view_crop Crop screen opens

7. Palette

Event Parameters When it fires
view_palette Color-palette screen opens

8. Generating

Event Parameters When it fires
view_generating Generating screen opens (generation starts)

9. Result

Event Parameters When it fires
view_result Result screen opens
click_save User taps Save / Download on the result

10. Subscription / Paywall

Event Parameters When it fires
iap_view convert_number, source Subscription screen opens
iap_btn_click convert_number, package_id, source User taps the Buy / Continue button
iap_successfull ⚠️ convert_number, purchase_package_id, purchase_order_id, purchase_token_part_1, purchase_token_part_2, source Purchase completes successfully

source values: generate_photo, home_button_pro

⚠️ iap_successfull is spelled with double "L" in the app. Please confirm whether spec expects iap_successful (one L) or keep as-is.


Open questions for spec alignment

  1. Spelling of iap_successfull (double-L) — keep or fix to iap_successful?
  2. Is the convert_number parameter expected in the spec for all IAP events?
  3. Screens / events possibly missing vs spec:
    • Onboarding / Intro / Splash / Language-select
    • Settings screen and its interactions
    • Pro CTAs from non-paywall entry points
    • Generation lifecycle: success / fail / re-generate
    • Share action on Result
    • Rating dialog
    • Per-screen Back-button events
  4. Do click_home_feed / click_home_banner / click_template need extra params (e.g. position index, category name)?