Event Name:
sign_in_details_update_attempt
- Use snake_case for consistency and robustness, as Mixpanel is case-sensitive and recommends this convention for event names and properties Best Practices.
Event Description:
Tracks when a user clicks any call-to-action (CTA) button or link within the settings menu related to updating sign-in details. This event helps analyze which CTAs are most interacted with during sign-in detail update attempts.
Trigger:
Fire this event whenever a user clicks any CTA (button or link) within the settings menu that is associated with updating sign-in details.
Event Properties:
- cta_text (string): The visible text on the CTA button or link that the user clicked.
- This property provides context for which specific action the user attempted, enabling deeper analysis without creating overly specific events Best Practices.
Example Implementation (JavaScript):
mixpanel.track('sign_in_details_update_attempt', {
cta_text: 'Change Password'
});
- Replace 'Change Password' with the actual text of the CTA clicked by the user.
Notes:
- Avoid creating separate events for each CTA; instead, use the cta_text property to distinguish between them. This keeps your event taxonomy clean and maintainable Best Practices.
- Document this event and its properties in your tracking plan or data dictionary (Lexicon) for clarity and team alignment Lexicon Overview.
This approach ensures your event tracking is consistent, scalable, and aligned with Mixpanel’s analytics requirements.
