article thumbnail

Common technical hiccups in your product analytics that are easy to spot

Mixpanel

The good news is that many technical quirks tend to follow certain patterns that can be easily spotted—even by non-engineers. Here are four technical hiccups associated with corrupt event tracking data, how to spot them, and what to do about them. So why could that happen from a technical standpoint? Event stuttering.

article thumbnail

How to be the go-to engineer for product analytics

Mixpanel

The point is that some of these might be catchable by non-technical team members whose job it is to analyze the data, but a lot of cases could only ever be noticed by someone who understands how the implementation actually works on a technical level: an engineer like yourself. Keep the product folks technically up-to-date.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Always implement analytics as part of feature development. Here’s why.

Mixpanel

Analytics should be tested alongside features. In order to effectively test whether a feature has been implemented correctly, a QA engineer needs to understand the feature inside and out. You work like heck to get everything implemented and tested on time and get a brief moment of celebration…then surprise!

article thumbnail

How to add analytics event tracking in SwiftUI (the elegant way)

Mixpanel

We’ve heard reports of a variety of types of unexpected behavior that can sometimes occur in your lifecycle callbacks, so its important to test each view thoroughly to see where workarounds may be required, particularly as updates to SwiftUI are released.