Closed decentralauren closed 1 week ago
@L03TJ3 if these are just boolean then it would be better to use .identify
and set them as a property instead of sending an event each time. we have limited events on posthog
@sirpy identify is something you do at the start of user-session (so that any events in the sessions can/will be linked to a user-profile)
Not sure I see how you suggest to use identify to track these events:
Interacted with wallet-connect Interacted with invite rewards used send-via-address used bridge
you should be able to call identify multiple times. or you can contact posthog to ask if there's a way to update a user property without triggering an event (ie so it isnt counted towards the limits) or if you can call identify multiple times
identify does nothing but to setup a person_profile.
doing any events involving a person profile is 4x as expensive according to their docs.
We decided after some suggestions that we won't track these events with posthog. We will create a cohort based location/app used.
It is undecided if we include wallet-address as identifiable ID.
Since that is all outside of scope of this ticket, it will be closed. The commits done around this will be reverted from this pr: https://github.com/GoodDollar/GoodDAPP/pull/4279
The events we want to track into posthog:
The only identifiable data we need is the wallet-address.
Technical implementation
To capture events in posthog:
A method should be added to the
AnalyticsClass
for handling the sending of events (similar to any other provider)