I apologize, but I don't have enough specific information in the provided knowledge sources to create a detailed Mixpanel event ticket or implementation instructions for the "Cancel Application" event you described. The knowledge sources don't contain information about this particular event or application flow.
However, I can provide some general guidance based on Mixpanel best practices for event tracking:
1. Event Name: "Cancel Application"
2. Properties to consider tracking:
- Cancellation Source (e.g. "landing_page", "cont_tracking_page")
- User ID (if available)
- Application Progress (how far along they were before cancelling)
- Timestamp
3. Implementation:
For client-side implementation, you would typically use the Mixpanel JavaScript SDK. Here's a general example of how you might track this event:
```
mixpanel.track("Cancel Application", {
"Cancellation Source": "landing_page",
"Application Progress": "25%"
});
LBKSYou would need to implement this tracking code on the client-side, triggered when the user clicks the "Yes, I want to cancel" button.
For more detailed implementation instructions, I recommend referring to the [Mixpanel JavaScript SDK documentation](https://docs.mixpanel.com/docs/tracking-methods/sdks/javascript).
Remember to follow Mixpanel's best practices for naming events and properties consistently, as outlined in their [best practices guide](https://docs.mixpanel.com/docs/data-structure/events-and-properties#best-practices).
For a more accurate and tailored implementation, you should consult with your development team and refer to Mixpanel's official documentation for the most up-to-date guidance.
