When analytics are on (see Your consent choice, next), Meshk reports two kinds of signal to Google Analytics 4 (GA4). The generic kind: a page_view each time you load or navigate to a page, scroll_depth at roughly 25/50/75/90% of the way down a page, scroll_to_end once when you reach the bottom, and cta_click for the buttons and links you interact with.
The rest is purpose-built for this app, and named for exactly what it records rather than anything generic:
tuning_change— which tuning you pickmakam_change— which makam you pickneck_pluck— which pitch you tap on the neck, logged as its exact position in cents, not just a note namepattern_play— starting playback, tagged with where it came from: the active makam’s own seyir, a built-in pattern, or a pattern you createdsound_panel_change— adjusting sound design, reported once you release a slider or pick a preset, not on every point along the way
That’s more granular than a typical marketing site’s analytics, because it answers a narrower question than “how many visitors”: which tunings, makams, and features people actually use, so development effort goes where it’s useful. It is not designed to, and does not, identify you personally.
All of this travels through Meshk’s own domain rather than straight to Google — see Google’s role, below.