Do you use Yandex.Metrica? Then you know what I'm talking about.
One of the biggest frustrations for Yandex Metrica users is dealing with additional parameters. I've seen hints of upcoming updates that might add event parameters, but as of now, there are only two scopes of parameters you can use to enrich your data in Yandex Metrica: visitor and visit.
These are managed using the params and userParams methods, and it's incredibly inconvenient. Let me explain with an example of visit parameters.
Visit parameters are additional data you can send to Yandex Metrica with each site visit. These parameters can include any information useful for analysis, such as page categories, registration statuses, and other site-specific data.
To analyze this data, you need to add these parameters to your report with the necessary level of nesting (you can nest one parameter within another). Then, you can work with the required metrics like visits, users, goal achievements, and so on.
However, these parameters apply to the visit scope, which is quite coarse. For example, if you send a funnel step parameter along with a goal, the reports will aggregate visits under this parameter, not the actual progression through the funnel step.
In the Yandex Metrica interface, counting events with a specific parameter is very challenging and often feels like a ritual dance. You need to select the parameter and specify the exact goal, and so on. This seems to be the toughest limitation of session-based analytics, and it's quite frustrating.
Among the potential solutions are sending revenue per goal (which oddly enough is an event-scope metric) and using the Logs API, which includes page_view parameters.
In conclusion, we're still waiting for event parameters in Yandex Metrica. For instance, Matomo already has something called Action Custom Dimensions, showing that this problem isn't unsolvable.
If you work with GA4 to BigQuery exports, be sure to check out my SQL cheat sheet.
