You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project that uses the DSL configuration for tracking screen views. It’s the standard setup for naive screen tracking via an ARAnalyticsTrackedScreens config. It works well, but I’m up against a problem: out-of-the-box screen tracking does not allow you to tack on additional event properties.
Looks good to me, especially if you're OK with the current naive implementation. We're still using the RAC branch. So please ensure backwards compatibility.
Custom properties is working currently but I need custom event name for tracked screens in Mixpanel. I can see that ARAnalyticalProvider is very coupled to Google Analytics.
I'm seeing the best way is override didShowNewPageView: implementation in MixpanelProvider:
First of all, nice work on ARAnalytics!
I have a project that uses the DSL configuration for tracking screen views. It’s the standard setup for naive screen tracking via an
ARAnalyticsTrackedScreens
config. It works well, but I’m up against a problem: out-of-the-box screen tracking does not allow you to tack on additional event properties.When adding a screen monitor hook, additional configuration values like
ARAnalyticsEventProperties
are ignored, and thedidShowNewPageView:
implementation just hardcodes an event and properties.I’m okay with hardcoding the event name – I like the opinionated screen tracking event – but it’d be nice if I could tack on additinoal properties:
The sent
Screen view
propeties would then be a union of the default@{ @"screen": pageTitle}
dictionary and the value ofARAnalyticsEventProperties
.I’m filing this as an issue to see if it gets a basic 👍 or 👎. If the former, I’ll take a stab at a PR.
Thanks!
The text was updated successfully, but these errors were encountered: