ABsmartly
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by ABsmartly B.V. · absmartly.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
ABsmartly at a glance
- Vendor
- ABsmartly B.V.
- Headquarters
- Incorporated in the Netherlands source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates ABsmartly 2.5/5, the mean of 6 judges. ABsmartly is a developer-centric A/B testing and feature flagging platform from ABsmartly B.V. how scores are made
- As of
- Vendor pages captured 19 Oct 2026 to 16 Nov 2026; evaluated by the panel 16 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
ABsmartly is a developer-centric A/B testing and feature flagging platform from ABsmartly B.V. of Amsterdam, built by the folks who architected the A/B testing tool at Booking.com. Statistical rigour is the strongest criterion, scoring a flat 7, on Group Sequential Testing documented with efficacy and futility boundaries, a named author and a downloadable whitepaper; we found no public information on sample ratio mismatch checks or multiple-metric corrections. Experimentation scope and data and integrations score 6-7 on twenty-one documented SDKs, a REST API described as giving complete control, and raw data exports. The weakest ground in the verdicts is consent and tracking at 0-2, where we found no public information on the test script's behaviour relative to visitor consent, and sovereignty at 2-4, where the privacy policy states data may be stored on servers in the USA and cloud hosting is listed with Amazon Web Services in the USA. Performance impact is the genuine split at 2-5: the product engineer's 5 and the growth lead's 4 credit the server-side architecture, the remaining scores sit at 2 for want of measurements. Pricing is demo-only.
Speaks for it
- Statistical rigour scores a flat 7, on Group Sequential Testing documented by name with efficacy and futility boundaries, a named author and a downloadable whitepaper
- Experimentation scope scores 6-7 on documented SDKs for twenty-one languages, feature flags, multivariate tests, custom-attribute targeting and the LaunchPad visual editor
- Data and integrations scores 6-7 for a REST API described as giving complete control, CI/CD webhooks, raw data exports and a Segment integration
- The SDKs are published under Apache-2.0 and MIT licences, so a team can inspect what runs
- Real-time results display confidence intervals, and Bayesian statistics are named as available
Held against it
- Consent and tracking scores run 0-2, and we found no public information on when the test script runs relative to consent, what it stores on the device, or any cookieless mode
- Sovereignty scores run 2-4, and the privacy policy states data may be stored on servers in the USA while the subprocessor list names Amazon Web Services in the USA for cloud hosting
- Performance impact splits 2-5, and we found no published figures for script weight, loading behaviour, flicker handling or Core Web Vitals impact behind the claim to keep your vitals performant
- We found no public information on sample ratio mismatch detection, variance reduction or corrections for multiple metrics — the gap that holds statistical rigour below its top band
- Purchase routes through a demo form, and we found no public prices, tiers or traffic metric behind the advertised all-in pricing with unlimited experiments and unlimited user seats
Best for
- You are an engineering team shipping experiments server-side behind feature flags, across many languages, in your own stack
- You need a sequential-testing method you can show finance or a client's stakeholders, with a whitepaper and a named author behind it
- You want to pull raw experiment data out through an API and check the results against your own numbers
- Your team mixes no-code marketers with developers and needs a visual editor alongside server-side SDKs
Avoid if
- You run a consent-gated or German-market site and must document the test script's consent behaviour before rollout; consent and tracking scores run 0-2 and the captured pages document only marketing consent and de-identification
- Your data-protection review requires confirmed EU residency for visitor data; the privacy policy states data may be stored on servers in the USA, with standard contractual clauses as the stated safeguard
- You need published measurements of the snippet's page cost before signing; the pages carry the claim to keep your vitals performant and performance impact scores split 2-5
- You must build a budget before a sales conversation; every captured purchase route ends at a demo form
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 3.5 of 5 |
| Statistical method & guardrails | 3.5 of 5 |
| Consent & visitor tracking | 1 of 5 |
| Snippet performance & flicker | 1 of 5 |
| Analytics, data export & integrations | 3 of 5 |
| European sovereignty | 1.5 of 5 |
Experiment types & delivery
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
Twenty-one documented SDKs across Java, Python, Go and more put server-side and feature-flag experiments firmly in reach, and LaunchPad is a real visual editor so my team can build tests without engineering, with targeting on custom attributes rather than URLs alone. Apps, websites and email are all named as surfaces. We found no public information on multi-page tests, mutually exclusive groups, holdouts or a personalisation engine, so I stop below the top of the scale. 1 5 8
The E-Commerce Manager
The captured pages show a genuinely developer-led platform: SDKs for twenty-one languages including server-side ones, a LaunchPad visual editor, multivariate tests, feature flags with attribute targeting, and experimentation across apps, websites, email and CRM. But we found no public information on personalisation that can be tested against a control, on holdouts, or on mutually exclusive experiment groups — the exact things I'd want for merchandising tests. 1 5 8
The Product Engineer
Server-side is the whole product: twenty-one documented SDKs from Java, Go and Python to Rust, Scala and C++ plus browser and Node, with feature flags, multivariate tests, custom-attribute targeting and a searchable experiment hub for past decisions on one platform. The captured pages do not document mutually exclusive groups, holdouts or personalisation tested against a control, so it falls short of the top band despite the SDK breadth. This is exactly the surface I want for shipping experiments behind flags in my own stack. 1 8 8 5
The CRO Consultant
Twenty-one SDKs across server languages, a visual editor called LaunchPad, feature flags, multivariate tests and surfaces from native apps to emails clear the mid anchor decisively — this is the server-side muscle I want across different client stacks. What the captured pages do not show is multi-page tests, mutually exclusive experiment groups, holdouts, or personalisation tested against a control, which is the gap I would probe before standardising several clients on it. 8 8 5 1
The Data Protection Officer
Documented SDKs for twenty-one languages from Java and Go to React and Swift cover server-side and client-side work, alongside a visual editor, feature flags, multivariate tests, targeting on custom attributes and a searchable experiment hub. We found no public information on multi-page tests, mutually exclusive experiment groups, holdouts, or personalisation that can itself be tested against a control. 1 8 5 8
The Skeptic
Server-side and client-side experiments run through SDKs documented for twenty-one languages, with feature flags and multivariate tests in one platform, a visual editor for no-code creation, and targeting on custom attributes — a genuine programme, not a visual editor bolt-on. We found no public information on multi-page tests, mutually exclusive experiment groups, holdouts, or personalisation tested against a control, which is what separates the top band here. 1 8 5 8
Statistical method & guardrails
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead
Group Sequential Testing is documented in unusual depth — efficacy and futility boundaries, explicit false-positive control when checking results repeatedly, a downloadable whitepaper and a named author — which is exactly the paper trail I need when finance asks where the promised revenue went. Bayesian statistics and real-time results with confidence intervals are also named. We found no public information on sample ratio mismatch detection, CUPED variance reduction or multiple-comparison correction. 6 8
The E-Commerce Manager
Group Sequential Testing is documented by name with efficacy and futility boundaries, a stated protection against early peeking inflating the false positive rate, a downloadable whitepaper, and confidence intervals in the real-time analytics. We found no public information on sample ratio mismatch detection, variance reduction, or corrections for multiple metrics, which is what separates a strong engine from a full guardrail set. 6 8
The Product Engineer
Group Sequential Testing is named, explained with efficacy and futility boundaries and pre-set checkpoints, credited to a named statistician, and backed by a downloadable whitepaper — a genuine, documented answer to peeking, and the futility boundary lets you stop a test that does nothing or hurts. I found no public information on sample ratio mismatch detection, variance reduction, or correction for multiple metrics or variants, and Bayesian statistics appear only as a listed feature. Raw data exports at least leave room for re-analysis. 6 8 8
The CRO Consultant
Group Sequential Testing is documented unusually well — efficacy and futility boundaries, batch analysis with pre-set checkpoints, the false-positive claim, a downloadable whitepaper and a named author behind the method — which is a peeking protection I can actually show a client's stakeholders. The pages name the methods (sequential and Bayesian) and show confidence intervals in the results view. We found no public information on corrections for multiple metrics or variants, sample ratio mismatch detection, CUPED-style variance reduction, or guardrail metrics that stop a harmful test. 6 8 5
The Data Protection Officer
Group Sequential Testing is documented by name with efficacy and futility boundaries, a stated protection against inflating the false-positive rate when checking data mid-test, a downloadable whitepaper, Bayesian statistics and real-time analytics with confidence intervals. We found no public information on sample ratio mismatch detection, correction for multiple metrics or variants, or variance reduction. 6 8
The Skeptic
Group Sequential Testing is named and genuinely documented: efficacy and futility boundaries, pre-set checkpoints, an explicit claim that more frequent checks do not inflate the false positive rate, a named author for the method, and a downloadable whitepaper — the best answer to peeking on these pages. Real-time analytics show confidence intervals, and a Bayesian option is claimed but documented far less. I read for sample ratio mismatch checks and corrections for multiple metrics or variants and found no public information on either, nor on variance reduction, so it stops below the top band. 6 5 8
Consent & visitor tracking
n/r
n/r
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
There is a published GDPR and HIPAA compliance policy with a DPIA, de-identification of personal data, a named DPO and free subject-request handling within a month, and consent withdrawal through a contact form. We found no public information on when the test script runs relative to consent, which cookies or storage keys it sets, whether a cookieless mode exists, or how testing maps to §25 TDDDG — before a German rollout I would demand that in writing. 7 2
The E-Commerce Manager
The compliance policy states that processed personal data is de-identified, names a Data Protection Officer, and offers free one-month data requests and consent withdrawal. We found no public information on when the test script runs relative to consent, what it stores on a visitor's device, or a cookieless mode — the question that decides whether I can run this on a German shop is unanswered. 7 2
The Product Engineer not rated — no public information
We found no public information on how the test script behaves relative to visitor consent, what it stores on the device, whether a cookieless or consent-pending mode exists, or how visitor identifiers are handled; the pages we read — the privacy policy, the GDPR and HIPAA compliance policy, the terms and the SDK documentation — describe the company's data-protection programme, not the snippet's runtime behaviour. Nothing on §25 TDDDG or ePrivacy handling of the script appears on the captured pages. 2 7 3 8
The CRO Consultant
Nothing on the captured pages says when the test script runs relative to consent, which cookies or storage keys it sets, or whether a consent-pending or cookieless mode exists — exactly what a DPO asks me to produce, and it is not here. What is published is general GDPR policy: prior consent for marketing, a withdrawal right through the contact form, a named DPO, free data-subject requests handled within a month, and de-identification of personal data. 7 2 3
The Data Protection Officer
We found no public information on whether the test script may run before the consent banner is answered, on a consent-pending mode, or on the cookies and storage keys the script sets on the device. A Managed Component for WebCM is named among integrations without any documented consent behaviour, and the terms place the duty to secure consents on the customer while the compliance policy speaks only of marketing consent and de-identified personal data. 3 7 8
The Skeptic not rated — no public information
We found no public information on when the test script runs relative to a visitor's consent, what it stores on the device, or any consent-pending or cookieless mode. The captured privacy and compliance pages address the vendor's own marketing consent, de-identification of processed data and transfer safeguards, but we found no public information on the script's behaviour under §25 TDDDG or the ePrivacy rules. 2 7 8
Snippet performance & flicker
panel disagrees
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead
The documented architecture is server-side SDKs with a self-hosted instance endpoint and a "build on your own stack" pitch, which addresses page cost at the design level. We found no published performance measurements, Core Web Vitals impact, script size or flicker-handling documentation — "keep your vitals performant" is a claim, not a figure. 8 1 6
The E-Commerce Manager
The vendor tells engineers to keep their vitals performant and build on their own stack, with open-source SDKs under permissive licences as the implied path. We found no public information on script weight, loading behaviour, Core Web Vitals impact, or flicker handling — on a product page where a tenth of a second shows in conversion, that silence is the whole story. 1 6 8
The Product Engineer
The architecture is server-side first — SDKs for every major server language and an endpoint on your own instance under the absmartly.io domain — so flicker-sensitive tests can run without a client script, and the SDKs are open source under Apache-2.0 and MIT, which lets a team inspect what runs. But no performance figures, snippet size, loading behaviour or flicker-handling trade-offs are published; "keep your vitals performant" is a claim, not a measurement I can check. 8 8 1 3
The CRO Consultant
The captured pages claim you can build on your own stack and keep your vitals performant, which points the right way, but we found no published measurements, snippet weight, loading behaviour, or any flicker-handling documentation. As written it is marketing language I cannot take to a client's web performance team. 6 1 3
The Data Protection Officer
The pages we read carry the claims "Keep your vitals performant" and "Build on your own stack", but we found no public information on script weight, asynchronous loading, anti-flicker handling, impact on Core Web Vitals, or from where the snippet is delivered. Without measured figures or an installation description, the cost the snippet imposes on the page stays undocumented. 1 3 6
The Skeptic
The performance evidence consists of the claim to keep your vitals performant while building on your own stack, and a platform said to handle billions of events monthly — neither is a measurement of what the snippet costs a page. We found no public information on snippet weight, loading behaviour, flicker handling, or any impact on Core Web Vitals. A claim without a published figure is marketing. 1 3 6
Analytics, data export & integrations
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API for managing experiments and reading results with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
Raw data exports, an API-first platform with a REST API and CI/CD webhooks, plus a Segment integration mean I can pull results into our own stack and re-check the numbers, and the open-source SDKs make the collection layer inspectable. We found no public information on warehouse-native analysis, streaming export or stated API limits. 8 8 5
The E-Commerce Manager
A REST API described as giving complete control, webhooks for CI/CD pipelines, raw data exports for advanced analysis, and a named Segment integration give me a way to check results in my own data. The named integrations on the captured pages are Segment and a managed web component, and we found no public information on a Google Analytics or tag manager integration, or on visitor-level and warehouse export limits. 5 8 8
The Product Engineer
A REST API billed as complete control with published guides and API references, webhooks wired for CI/CD pipelines, raw data exports, a Segment integration and custom metrics — that is enough surface to build internal tooling, which is my bar. I found no public information on warehouse-native computation of metrics, streaming export, or stated API limits, so the export story reads as files rather than a warehouse pipeline, and I would want to verify granularity before trusting results against our own data. 8 5 8 3
The CRO Consultant
A documented REST API, webhooks for CI/CD pipelines, raw data exports for advanced analysis and a Segment integration — enough for me to pull results out and check them against the client's own numbers, which is my baseline. We found no public information on visitor-level streaming to a data warehouse, warehouse-native metrics, or stated API limits, so I would not call it warehouse-native. 8 8 5
The Data Protection Officer
A REST API described as giving complete control, webhooks for CI/CD pipelines, raw data exports for advanced analysis and a Segment integration are documented, with SDKs published under Apache-2.0 and MIT licences. We found no public information on warehouse-native analysis, streaming export of visitor-level data, or stated API limits. 5 8 8
The Skeptic
Raw data exports for advanced analysis, a REST API pitched as complete control, webhooks for CI/CD, an API-first stance, and a Segment integration, with SDKs published under permissive open-source licences — enough to pull results out and re-analyse in principle. We found no public information on export formats, warehouse-native analysis, or stated API limits, so the depth of the raw export remains unverifiable from the captured pages. 5 8 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
The contracting entity is ABsmartly B.V. in Amsterdam and a dated subprocessor list with countries is published, but cloud hosting is listed with Amazon Web Services in the USA and the privacy policy states data may be stored "on our servers in the USA", with standard contractual clauses named as the safeguard. We found no public information stating EU hosting for visitor data. 2 4 7
The E-Commerce Manager
The contracting entity is ABsmartly B.V. at an Amsterdam address, with a published subprocessor list naming each country. The privacy policy states data may be stored on servers in the USA, the cloud hosting subprocessor listed is Amazon Web Services in the USA, and we found no public information on EU hosting of visitor data as standard or on a data processing agreement. 2 4 7
The Product Engineer
The contracting entity is ABsmartly B.V. on the Keizersgracht in Amsterdam and the subprocessor list is published with locations and a recent update date, but that list names Amazon Web Services in the USA for cloud hosting, and the privacy policy states that data collected may be stored on servers in the USA. Transfer safeguards such as standard contractual clauses and binding corporate rules are stated, yet nothing on the captured pages documents EU hosting of experimentation data or of the snippet delivery — for a script that runs on every visitor, that gap matters to me. 2 4 7 3
The CRO Consultant
The contracting entity is ABsmartly B.V. on the Keizersgracht in Amsterdam and a subprocessor list is published with countries, which is a solid start. But the privacy policy states collected data may be stored on servers in the USA with standard contractual clauses as the safeguard, and EU residency for visitor data is not stated as standard — for a script on every visitor, that is a conversation I would hold with the DPO before contracting. 3 4 2 7
The Data Protection Officer
The contracting entity is ABsmartly B.V. of Amsterdam and a subprocessor list is published with locations, which is what I look for — but the privacy policy states data "may be stored, with appropriate technical and organizational security measures applied to it, on our servers in the USA", and the cloud hosting subprocessor is Amazon Web Services in the USA, so EU processing of visitor data is not evidenced. Transfer safeguards are listed, and we found no public information on a customer data processing agreement, on EU hosting as standard, or on a CDN named in the subprocessor list. 2 4 7
The Skeptic
A Dutch contracting entity, a published privacy policy and a subprocessor list with countries are on the ledger, but the privacy policy states data may be stored on servers in the USA and the subprocessor list names Amazon Web Services in the USA for cloud hosting, alongside several other US processors. Standard contractual clauses are the stated transfer safeguard, and we found no public information on EU hosting of visitor data or where the snippet is delivered from. 1 2 4 7
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
Pricing is described qualitatively — "all-in pricing" with unlimited experiments and unlimited user seats — but we found no public price figures, and the only purchase path shown is a demo request form, so I cannot build a budget line without a sales conversation. The terms document a 14-working-day cooling-off period and non-refundable conditions thereafter. 5 6 3
The E-Commerce Manager
Every captured page routes buying through a demo form, and we found no public prices at all — no 'from' figure, no tier, no traffic metric. The only pricing facts are an all-in model with unlimited experiments and unlimited user seats, prices changeable at any time, and a 14-working-day cooling-off period, so what a December traffic peak costs me is a negotiation. 3 5 6
The Product Engineer
No prices are public: the pages describe an all-in model with unlimited experiments and unlimited user seats, but every purchase routes through a demo form, and the terms discuss cooling-off periods and refunds without a single figure, tier, traffic metric or limit. A buyer cannot estimate even a rough annual cost from what is published. 5 6 3
The CRO Consultant
There is a documented model — all-in pricing with full access to all features, unlimited experiments and unlimited user seats — alongside contract terms like a 14-working-day cooling-off period, refunds within 30 days, and the right to change prices at any time. But no price figures, no traffic metric and no tiers appear on any captured page and the product is sold through a demo form, so I cannot estimate any client's annual cost before the sales call. 5 3 6
The Data Protection Officer
We found no public price anywhere: the product is sold through a demo form, and beyond a described all-in pricing model with unlimited experiments and unlimited user seats, the terms state only commercial conditions — a fourteen-working-day cooling-off period, refunds within thirty days, card fees borne by the buyer and prices changeable at any time. No tier, traffic metric or figure is published, so a buyer cannot estimate the annual cost from public pages. 3 5 6
The Skeptic
The captured pages advertise "all-in pricing" with "Unlimited Experiments, Unlimited User Seats", and terms covering a fourteen-working-day cooling-off period, refunds within thirty days, and a right to change prices at any time — but we found no public prices, tier boundaries, or the traffic metric a buyer would be billed on. With every number behind the demo form, no annual cost can be computed from public pages. 3 5
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in NL | 2/2 pts | 1 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about ABsmartly
Is ABsmartly European?
Yes. whats-best.ai classifies ABsmartly as EU-Made. Its vendor, ABsmartly B.V., is incorporated in the Netherlands, per the vendor’s page captured 16 Nov 2026.
Where does ABsmartly store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does ABsmartly have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to ABsmartly?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Webtrends Optimize (3/5) highest among the other 45 Conversion Optimization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Varify.io (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: ABsmartly alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 19 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 6 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage absmartly.com Checked 16 Nov 2026 Details →
- 2 Privacy policy absmartly.com Checked 16 Nov 2026 Details →
- 3 Terms of service absmartly.com Checked 16 Nov 2026 Details →
- 4 Subprocessor list absmartly.com Checked 16 Nov 2026 Details →
- 5 Experiment types & delivery — found from sitemap absmartly.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 6 Statistical method & guardrails — found from sitemap absmartly.com Checked 16 Nov 2026 Details →
- 7 Consent & visitor tracking — found from sitemap absmartly.com Checked 16 Nov 2026 Details →
- 8 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →