

Gummicube vs SplitMetrics Optimize
Prices from each vendor’s own page, beside stores, free plan, agent access and delivery.
| Feature | ||
|---|---|---|
| Entry price | Not published agency engagement, quoted per client | Not published contact sales for a custom plan |
| Pricing model | Managed service with a data platform | Custom plan |
| Stores | App Store and Google Play | App Store and Google Play |
| Free option | NoneNo | NoneNo |
| API and agent access | NoneNot advertised | NoneNot advertised |
| Delivery | Agency plus 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
Where it runs
Gummicube: agency. SplitMetrics Optimize: web.
- 02
Price
Neither publishes a price. Both quote on request.
In its favour
What Gummicube does well.
- They do the work, which is the whole point for a team with budget and no time.
- Years of category experience across many clients.
- Google Play alongside the App Store, handled by the same team.
- Creative and listing production as part of the engagement.
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