#Golang maps godocs update

The cohort in the feature flag is in the same group as another condition.There's more than one cohort in the feature flag definition.However, there are a few constraints here and we don't support doing this for arbitrary cohorts. To support feature flags that depend on cohorts locally as well, we translate the cohort definition into person properties, so that the person properties you set can be used to evaluate cohorts as well. If it fails to compute a flag, it returns None, instead of going to PostHog's servers to get the value. In this case, you can set the OnlyEvaluateLocally parameter to true, which tries to compute flags only with the properties it has. Sometimes, performance might matter to you so much that you never want an HTTP request roundtrip delay when computing flags. Alias – the other distinct ID of the user, which will be aliased to the current one.DistinctId – the current unique id (logged in user id).If you're using PostHog in the front-end and back-end, doing the identify call in the frontend will be enough. The same concept applies for when a user logs in. Then, when that users signs up, you want to do an alias call with the session ID and the newly created user ID. In a purely back-end implementation, this means whenever an anonymous user does something, you'll want to send a session ID with the capture call.

This will allow you to answer questions like 'Which marketing channels lead to users churning after a month?' or 'What do users do on our website before signing up?' To connect whatever a user does before they sign up or login with what they do after, you need to make an alias call.

#Golang maps godocs update

The most obvious place to make this call is whenever a user signs up, or when they update their information.