

Sensor Tower vs SplitMetrics Optimize
Prices from each vendor’s own page, beside stores, free plan, agent access and delivery.
| Feature | ||
|---|---|---|
| Entry price | Not published custom quote per customer | Not published contact sales for a custom plan |
| Pricing model | Custom pricing, quoted per customer | Custom plan |
| Stores | App Store and Google Play | App Store and Google Play |
| Free option | Free planFree sign-up, limited data | NoneNo |
| API and agent access | MCPMCP server and API, enterprise API subscription through sales | NoneNot advertised |
| Delivery | Web app | Web app |
Entry price per year across all 19 tools, log scale, with these two named.
The short version
What the choice turns on.
Only the rows where these two differ.
- 01
Trying it
Sensor Tower: free plan. SplitMetrics Optimize: none.
- 02
Scripting and AI access
Sensor Tower: MCP. SplitMetrics Optimize: None.
- 03
Price
Neither publishes a price. Both quote on request.
In its favour
What Sensor Tower does well.
- The deepest market estimate set in the industry, going back years across both stores.
- Ad intelligence, audience data and cross-market analysis.
- The figures investors and large publishers cite when sizing a market.
- Account management, onboarding and custom reporting as part of the contract.
In its favour
What SplitMetrics Optimize does well.
- A/B testing of store listing creative, on lookalike pages kept out of the live store.
- The setup to run an experiment to statistical significance.
- A team platform with the support and onboarding an enterprise contract carries.
Keep comparing