Remove Engineering Remove Events Remove Technical Cofounder Remove Technical Review
article thumbnail

How to be the go-to engineer for product analytics

Mixpanel

Engineers are always looking for ways to differentiate themselves. Here are four ways you can position yourself as the go-to engineer for everything product analytics—and simultaneously make yourself invaluable to both the product and engineering teams. Spearhead a slick analytics implementation. You’d be celebrated.

article thumbnail

Why it’s never too early to add product analytics to your app

Mixpanel

So it’s tempting to think the additional add-on of measuring user events in your code (i.e., This is a very compelling story (especially if you’ve got only one or two engineers or developers on your team who may or may not include yourself). Remember, product analytics involves tracking events in your app. Sure you would.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

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

Mixpanel

As new features are added to your products, so should new analytics events be added to your codebases. When engineers implement features, they write code. When engineers add analytics events to new features, they add additional analytics code to their new feature code. Product analytics is an ongoing effort.

article thumbnail

Data thinking vs. product thinking

Mixpanel

However, if we built an event funnel in our product analytics, one that examines what users are doing several steps before potentially reaching the chat feature, we might find that the engagement drop-off was actually happening a screen or two earlier, maybe due to a poorly designed series of buttons or UI flow. Create counter metrics.

article thumbnail

User friction can sink your app. Here’s what it is and how to avoid it.

Mixpanel

That’s because you can track all events that a user takes in your product (in order) and then measure what you expect to see against what actually happens. App performance needs to be top priority for your engineering teams, especially for commercial apps. Detecting user friction with product analytics. Unexpected drop-off.