ABsmartly vs. Akamai mPulse
| Product | Rating | Most Used By | Product Summary | Starting Price |
|---|---|---|---|---|
 ABsmartly | Score9.7 out of 10 | N/A | ABsmartly is an A/B testing and experimentation tool for use across web, email, and apps, both server-side and client-side. The ABSmartly platform is designed for product teams and PLG-driven organisations who want to make data-driven decisions. The ABsmartly platform caters to various testing scenarios, including feature flags, split testing, multi-variant, multi-page, multi-platform, SEO tests, cross-device testing, among others. ABsmartly was founded by experimentation… | $60,000 per year (starting at 50 Million events per month) |
 Akamai mPulse | Score7.8 out of 10 | N/A | mPulse, from Akamai, is a real-time end-user digital experience monitoring solution (or RUM, for real user monitoring) that enables the user to capture user experience data, optimize website performance, and measure ROI. | N/A |
| ABsmartly | Akamai mPulse | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Editions & Modules | No answers on this topic | No answers on this topic | ||||||||||||||
| Offerings |
| |||||||||||||||
| Entry-level Setup Fee | No setup fee | No setup fee | ||||||||||||||
| Additional Details | ABsmartly has an events-based pricing model, clients have unlimited experiments, metrics and platform users, and they pay per event. ABsmartly has no pricing tiers or packages, so all customers get all features, including the advanced Group Sequential Testing engine, real time data processing, and collaborative tools. ABsmartly handles the infrastructure costs and provides the platform, however if clients wish, they can handle the infrastructure on their side. ABsmartly's event-based plans start at €60,000/year for 50 Million events per month. ABsmartly includes onboarding, standard training and support at no extra cost. ABsmartly has 2 categories of billable events: Exposure events An exposure event happens every time a call is made to check which variant (of an experiment or a feature flag) to show a visitor. The number of exposure is dependent on the number of unique visitors, the number of experiments and the number of exposure per experiment. Exposure Events = {# unique visitors} x {# experiments} x {# experiment exposures} Goal events A goal event happens every time a goal is triggered by a visitor of an application. A goal is what is used to create an experimentation metrics and they usually represent an action taken by visitors, a click on a button, a conversion, a cancellation, etc. The number of goals events is dependent on the number of unique visitors, the number of goals and the number of goals exposures. Goal Events: = {# unique visitors} x {# goals} x {# goal triggers} | — | ||||||||||||||
| More Pricing Information | ||||||||||||||||
| ABsmartly | Akamai mPulse | |
|---|---|---|
| Small Businesses |  Google Optimize Score6.7 out of 10 | No answers on this topic |
| Medium-sized Companies |  AB Tasty Score8.6 out of 10 |  Catchpoint Score8.5 out of 10 |
| Enterprises |  Google Content Experiments (discontinued) Score7.3 out of 10 |  Nexthink Score7.3 out of 10 |
| All Alternatives | View all alternatives | View all alternatives |
| ABsmartly | Akamai mPulse | |
|---|---|---|
| Likelihood to Recommend | - | 7.0 |
| ABsmartly | Akamai mPulse | |
|---|---|---|
| Likelihood to Recommend | No answers on this topic |
|
| Pros | No answers on this topic |
|
| Cons | No answers on this topic |
|
| Alternatives Considered | No answers on this topic |
|
| Return on Investment | No answers on this topic |
|
| ScreenShots | ABsmartly Screenshots      |