As they say - if you’re not measuring it, you’re not managing it.
But just what should you be measuring when it comes to your brand’s mobile app?
Downloads, for one thing. But downloads alone are very much surface-level. They tell you that a device acquired the app. They don’t tell you whether the customer signed in, found a product, enabled notifications, placed an order, returned next month, or removed the app the following day.
An ecommerce app measurement plan needs to connect acquisition to customer behavior, commercial performance, retention, and technical health. It also needs to separate total app revenue from the value the app genuinely added.
This guide breaks down the metrics that matter, how they fit together, and how you can use analytics to better understand and grow your ecommerce brand’s mobile app.
The Ecommerce App KPI Framework
Before you start putting together a haphazard list of KPIs, you should understand why you’re tracking what you’re tracking, and what these metrics are actually telling you about your app.
Do they indicate that you’re struggling to get users? Struggling to hold onto users? Doing a good job of getting people to come back and use the app regularly?
Here are six broad areas you should categorize your KPIs into:
| Area | Question |
|---|---|
| Acquisition | Are the right people installing the app? |
| Activation | Do new users reach initial value? |
| Engagement | Do customers use the app in useful ways? |
| Commerce | Does the app support profitable orders? |
| Retention | Does it earn continued use? |
| Quality | Can customers rely on it? |
A giant list of events and numbers is going to be confusing. A categorized dashboard of events, organized into logical areas, is comparably much easier to understand.
Now let’s get into which metrics you should track for each category.
Acquisition Metrics
Acquisition is one of the most straightforward success indicators. Though, realistically, it’s probably more of a failure indicator.
Strong acquisition doesn’t necessarily mean your app is successful. You could get a lot of downloads, but no one using the app or buying through it.
But poor acquisition metrics tell you a lot. If you’re not getting anyone to download your app, that’s an obvious area to focus on.
Here are some of the metrics that tell you which messages and placements persuade customers to visit the store page, install, and continue into the app.
Promotion Impressions and Clicks
Track how often customers see an app promotion and how often they act on it. Useful sources include website banners, product page placements, email, SMS, post-purchase messages, QR codes, stores, social posts, and paid campaigns.
Click-through rate = promotion clicks ÷ promotion impressions
A low rate may mean the message is weak, the audience is wrong, or the placement is easy to ignore. It doesn’t tell you whether the resulting installs are valuable.
Listing Views and Conversion
Your app store listing is another step in the funnel.
Track product page views, downloads, and conversion rate by source, campaign, country, device, and listing variant. Apple defines App Store conversion rate using downloads and pre-orders divided by unique device impressions. Google Play updated its store-listing reporting in July 2026 to focus more heavily on user-intent clicks, so make sure everyone working with the dashboard understands the current metric definitions.
Use store-page data to test the icon, screenshots, preview, description, rating, and message match between the campaign and listing.
Installs, First-Time Downloads, and Reinstalls
Keep these concepts separate.
A first-time download is different from a redownload or reinstall. An install event may also be counted at the device level rather than the customer level. Platform dashboards, attribution tools, and product analytics can therefore show different totals without any of them being broken.
Document which source owns each number and use the same definition when comparing periods.
Cost per Install and Cost per Activated User
For paid acquisition:
Cost per install = campaign spend ÷ attributed installs
Then calculate the more useful version:
Cost per activated user = campaign spend ÷ users who completed the activation event
A campaign with cheap installs can be expensive if very few users reach value.
Activation Metrics
Activation is the transition from “downloaded the app” to “used it in a meaningful way.”
Choose an event that reflects your app’s purpose. It could be:
- Signing in and loading the customer’s account
- Adding a loyalty membership
- Enabling a useful alert
- Saving a product or preferred store
- Scheduling a repeat order
- Completing a first purchase
Whichever you go with, the idea is to understand how many people are getting past a certain threshold where they’re likely to continue using the app.
Here are a few specifics to track in this bucket.
Activation Rate
Activation rate = new users completing the activation event ÷ new users who first opened the app
Measure it within a defined window, such as the first day or first seven days. Break it down by acquisition source, customer status, operating system, app version, and country.
Time to Value
Measure how long and how many steps it takes a new user to reach activation.
Long setup, forced account creation, early permission prompts, unclear benefits, and login failures can all delay or prevent it.
Onboarding Completion and Drop-Off
If the app has onboarding, track each step. Don’t measure only the percentage that reaches the final slide. Connect onboarding to the first useful action.
A user who skips onboarding and purchases may be more successfully activated than one who completes five educational screens and leaves.
Engagement Metrics
Engagement metrics track your customers’ activity in the app. Downloads and activation are great - but what you really want is engaged users who open and shop in your app regularly.
Here are the best individual metrics to monitor.
Daily, Weekly, and Monthly Active Users
DAU, WAU, and MAU show how many users were active in each period. Define “active” based on a meaningful in-app event rather than background activity or a notification receipt.
The right window depends on purchase frequency. Daily activity may matter for a marketplace with frequent releases. Monthly activity may be more informative for luggage, furniture, or other low-frequency categories.
Stickiness
Teams sometimes calculate:
DAU/MAU = daily active users ÷ monthly active users
This indicates how often monthly users return on a typical day. It isn’t a universal quality score. A healthy value depends heavily on the natural rhythm of the category.
Sessions per User and Session Frequency
Track how often active users return and the gap between sessions.
More sessions can signal stronger product discovery, useful launch behavior, or repeat shopping. They can also signal that a task takes several attempts. Pair session data with outcomes.
Product Discovery and Intent Events
Useful events include search, filter use, product view, variant selection, wishlist addition, back-in-stock signup, add to cart, and checkout start.
Track the progression between them. Search volume alone doesn’t tell you whether customers find anything. Search-to-product-view rate and zero-result rate are more diagnostic.
Commerce & Revenue Metrics
This category measure the return you’re getting from your app - whether people are actually buying things in the app and spending money.
Conversion Rate
Define the denominator before reporting it.
Session conversion rate = orders ÷ shopping sessions
User conversion rate = purchasing users ÷ active users
Both are valid, but they answer different questions. Use a consistent definition when comparing app, mobile web, campaigns, or periods.
Add-to-Cart and Checkout Completion
Build the core funnel:
- Product view
- Add to cart
- Checkout start
- Payment attempt
- Purchase
Track errors and exits at each stage. A strong add-to-cart rate with weak checkout completion may indicate payment, promotion, shipping, login, or integration problems rather than poor product demand.
Average Order Value
Average order value = app revenue ÷ app orders
Segment AOV by new versus existing customer, category, campaign, incentive use, and order type. A higher app AOV can be encouraging, but app users may already be more loyal and valuable before installation.
Revenue per Active User
Revenue per active user = app revenue ÷ active app users
This combines purchasing rate and order value into one useful metric. Contribution per active user is even better when product margin, discounts, returns, and variable costs differ between channels.
App Share of Revenue
App share of revenue = app revenue ÷ total ecommerce revenue
Track app share alongside total revenue and customer behavior. A rising share may reflect incremental growth, or it may mean existing customers moved orders from mobile web into the app.
The distinction matters when evaluating ecommerce mobile app ROI.
Incremental Revenue and Contribution
The most important commercial question is what changed because of the app.
Compare app adopters with their own behavior before installation and with suitable non-adopter cohorts. Use holdouts for promotions or push campaigns where practical. Track contribution rather than revenue when discounts, returns, and fulfillment costs matter.
No method removes all selection bias. Customers who install are often more engaged already. State that limitation rather than assigning the full difference to the app.
Retention Metrics
Retention shows whether the app continues to earn its place after acquisition. This is another crucial area to track - as stronger retention means each download you’re able to acquire goes further.
Day 1, Day 7, Day 28, and Longer-Term Retention
Cohort retention measures the percentage of a group that returns in a later period.
Apple’s App Store Connect Analytics reports average retention at Day 1, 7, 14, and 28. Product analytics tools can define additional windows and qualifying events.
Choose an event that represents genuine use. Opening the app because a notification was tapped is weaker than browsing, using an account feature, or purchasing.
For low-frequency categories, also track 60-day, 90-day, seasonal, or event-based return behavior. A customer doesn’t need to open a furniture app every week for the app to be useful.
Churn and Lapsed Users
Define what “lapsed” means for your category. It might be no meaningful activity for 30, 60, or 90 days.
Track the size of the lapsed audience, the actions that preceded inactivity, and whether reactivation campaigns produce lasting return or one brief session.
Uninstalls and Active Install Base
Google Play provides install and uninstall statistics. iOS data is more constrained, so teams often combine platform analytics, notification-token changes, and product data to understand the active base.
Don’t treat every missing push token as a confirmed uninstall. Permissions, device changes, token rotation, and inactivity can produce similar signals.
Repeat Purchase Rate and Purchase Frequency
Retention should connect to the business model.
Track how many app customers purchase again, the time between orders, and the number of orders per customer. Compare equivalent cohorts and account for their prior purchase history.
Push Notification Metrics
Push is a category in and of itself. You could have strong acquisition, strong retention, decent engagement; but if your push campaigns are poor, there’s a clear area in which you could improve.
Here’s what to track for push.
Permission and Reach
Track:
- Eligible users
- Permission prompt views
- Opt-in rate
- Reachable devices
- Delivery rate
- Opt-out rate
Permission should be measured by acquisition source, prompt context, and operating system. A well-timed request after the user selects a useful alert may outperform a generic first-open prompt.
Opens, Sessions, and Conversion
Direct-open rate measures taps on the notification. Influenced opens or sessions include users who return later after receiving it.
Track deep-link success, product engagement, purchase, revenue, and opt-outs by message type. A campaign with high opens but frequent opt-outs may be borrowing from future value.
Use control groups where possible to estimate lift. Attributed revenue isn’t the same as incremental revenue, especially when a customer was likely to purchase anyway.
Our guide to push notifications for ecommerce covers permission, campaign design, and measurement in more detail.
Technical Quality Metrics
These metrics give you an idea of how well your app is performing from a technical perspective - and can be an indicator of why other areas, such as retention and engagement, may be underperforming.
Crash and ANR Rates
Track crashes by active user, session, app version, device, and operating-system version. For Android, monitor application-not-responding events as well as crashes.
Android vitals identifies user-perceived crash rate and user-perceived ANR rate as core quality metrics that can affect app visibility on Google Play. App Store Connect also reports crashes by app version.
Review quality immediately after each release and connect incidents to changes in conversion, retention, reviews, and support contacts.
Startup and Screen Performance
Measure cold and warm startup, search response, product page load, cart updates, checkout transitions, and time to interactive.
Use percentiles, not only averages. A reasonable median can hide a poor experience for customers on older devices or weak networks.
API, Integration, and Checkout Errors
Track failures in authentication, product loading, inventory, pricing, promotions, loyalty, subscriptions, cart, payment, order creation, and deep links.
These events need enough context to diagnose the problem without exposing sensitive customer information.
App Version Adoption
Know which versions are in use and how quickly customers update. This affects bug fixes, feature support, and the number of old code paths the team must maintain.
Customer Experience Metrics
Behavior data tells you what happened. Reviews, support contacts, surveys, and usability research help explain why.
Track App Store and Google Play rating, rating volume, review themes, support contact rate, issue category, and resolution time. Ask short in-app questions after appropriate moments rather than interrupting a customer who is trying to buy.
Group feedback with observed data. A rise in login complaints is more actionable when you can also see the affected app version, device group, and authentication error rate.
Building a Clean Event Taxonomy
Tracking everything is one thing. But if all your events and metrics are gibberish strings, it’s going to be hard to analyze the data properly.
Google Analytics for Firebase provides recommended events for retail and ecommerce, but your implementation still needs consistent names, parameters, and business definitions.
Create an event dictionary that records:
- Event name and plain-language meaning
- Exact trigger
- Required parameters
- Customer and session identifiers
- Owning team
- Downstream reports that use it
- Data and consent requirements
Use the same product, order, campaign, market, and customer identifiers across the app and backend where privacy rules allow. Prevent duplicate purchase events and server-to-client double counting.
Test analytics as part of every release. A checkout can work for the customer while silently breaking the event that finance and marketing depend on.
Common Ecommerce App Analytics Mistakes
The most common mistake is reporting installs and revenue without the journey between them.
Others include mixing users and devices, comparing app users with all web traffic, treating attributed sales as incremental, changing event definitions without documenting it, ignoring consent gaps, and reporting averages that hide a broken device or market.
Another mistake is separating product and technical data. A conversion drop after a release may be a merchandising problem, a payment failure, a slow screen, or a crash. Teams need a shared view of the timeline.
Final Thoughts
Ecommerce app analytics should help you answer three questions:
Are the right customers adopting the app? Are they getting enough value to return? Is the channel adding profitable behavior after accounting for what those customers would have done anyway?
Downloads matter, but only as the top of the funnel. Connect them to activation, useful engagement, commerce, retention, push, quality, and customer feedback.
When definitions are clear and events are reliable, the dashboard becomes a way to improve the app rather than a collection of numbers used to defend it.
Ecommerce App Analytics FAQs
These definitions will keep the most common app-performance discussions grounded.
What Is the Most Important Metric for an Ecommerce App?
There isn’t one universal metric. A useful north-star metric combines active customers with value, such as monthly purchasing users or contribution from retained app customers. Keep acquisition, activation, retention, and technical quality as guardrails.
How Do You Measure Ecommerce App Conversion Rate?
Choose a denominator and state it clearly. Session conversion rate is orders divided by shopping sessions. User conversion rate is purchasing users divided by active users. Don’t compare rates that use different definitions.
How Do You Measure App Retention?
Group users into cohorts based on install or first use, then calculate the percentage that completes a meaningful event in later periods. Choose windows that match the category’s natural purchase and usage frequency.
How Do You Know Whether App Revenue Is Incremental?
Compare app adopters with their own prior behavior and with suitable non-adopter or holdout cohorts. Control for customer quality, promotions, seasonality, and channel shift. No observational comparison removes all selection bias, so state the remaining uncertainty.
