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
In the web quickstart for tracking your first event we tell people to init, identify, then track. Including identify isn't necessary to track an event and doesn't make sense in the case of anon activity and could cause confusion on id mgmt - I think it should be removed or clarified it's not req'd unless the user is identified. Other guides for mobile just have init + track.
The text was updated successfully, but these errors were encountered:
totally fair. as i'm thinking more about it this might be a broader thing to consider. we're using signup in most of the quickstart guides except http (but in mobile we don't include identify) for consistency i'm assuming. but then in the ref docs we're all over the place with event naming and the JS ref example isn't an authentication event. maybe in quickstart guides we can show sending both an anon event and auth event. I'd challenge using signup across the board in these - ofc you can track business critical events like signup, purchase, etc client side but it's a bit at odds with our usual recommendation to track these server-side for safety.
In the web quickstart for tracking your first event we tell people to init, identify, then track. Including identify isn't necessary to track an event and doesn't make sense in the case of anon activity and could cause confusion on id mgmt - I think it should be removed or clarified it's not req'd unless the user is identified. Other guides for mobile just have init + track.
The text was updated successfully, but these errors were encountered: