AB Tasty

Name: AB Tasty
Brand: AB Tasty

Your customer experience optimization partner.

Est 2009|Valuation $150M|Raised $98.8M|52 Ref Customers

LinkedIn 30K|Web traffic 151K|FTEs 299|HQ Paris, Île-de-France, FR

MarketsConversion Rate Optimization (CRO) & A/B Testing A/B Testing & Experimentation

Published Oct 15, 2026

01Common complaints

1. Organizations that require a very high level of experimentation statistics governance and reporting transparency - If an organization needs highly opinionated statistical controls (sequential testing guardrails, false discovery rate controls, etc.), consider vendors that emphasize experimentation rigor. 2. Organizations with complex SPAs and insufficient QA resources - Reviews and competitor comparisons indicate SPA/mobile QA can be resource-intensive. If adequate QA resources are not available, evaluate alternatives with different delivery models. 3. Organizations requiring plug-and-play GA4 integration without development - Review feedback suggests GA4 integration may require development work; organizations needing zero-development GA4 connectivity should validate integration requirements. 4. Organizations with extremely high traffic that require flat, predictable pricing - Traffic-based pricing can be a constraint; organizations seeking predictable, traffic-independent spend should negotiate pricing terms or assess other pricing models. 5. Organizations requiring mature, publicly documented compliance artifacts immediately - AB Tasty documents ISO 27001 certification, but procuring teams that require immediately available SOC 2 Type II reports and detailed pen test summaries may need to engage the vendor for evidence.

Disqualifiers (poor fit)

No available engineering capacity for integration and SPA adjustments.
Ultra-performance-sensitive sites where client-side scripts are heavily scrutinized, unless performance is validated through a POC.
Organizations requiring fully transparent, publicly available security attestations and immediate self-serve procurement artifacts.

Known limitations highlighted in reviews

WYSIWYG/editor UX: described as dated or less intuitive than some competitors for some users.
Mobile QA: repeatedly noted as challenging.
Performance impact: heavy client-side changes can increase page load times.
Integration friction: GA/GA4 integration can require development and improvement.

Vendor-acknowledged compliance nuance

AB Tasty documentation explicitly warns that certain legacy cookie deposit methods do not comply with GDPR/ePrivacy and recommends avoiding them in production.

Roadmap / future considerations

Public documentation references ongoing AI-driven feature development (product labeling references such as "Evi"). The 2026 consolidation with Wingify/VWO could reshape roadmap priorities; procurement teams should request an updated roadmap under NDA and confirm product commitments.

Where it struggles (based on reviews)

Mobile QA and complex SPA behavior
Highly complex experiments requiring advanced governance and reporting
Analytics integrations that may require custom development effort

02Why they buy

Validated or partially validated by reviews and product materials: - Advanced targeting and segmentation (frequently noted by reviewers). - Ability for non-technical teams to launch tests with a visual editor and widgets in some scenarios. - Broad platform coverage: experimentation, personalization, and recommendations/merchandising (capabilities extended via the Epoq acquisition). Areas where competitors may offer advantages: - Experimentation governance and statistical rigor - Edge delivery and reduced client-side latency - Mobile and SPA workflow maturity

03Field reports

This section includes both positive and negative feedback, including direct quotes from review platforms.

Review platform signals (volume & rating)

G2: well rated on G2.
Capterra: very highly rated on Capterra (sample size on the platform is smaller).
TrustRadius: multiple vetted reviews; common pros/cons revolve around targeting, speed to launch, and QA/support communication.

Positive review themes (with quotes)

Common themes across review platforms: 1. Targeting / segmentation flexibility - Reviewer: “AB Tasty can be quite targeted… integrate with Mixpanel… set up an AB test only for B2B traffic.” 2. Usability for non-technical teams - Reviewer: “user friendly interface that allows non-technical teams to launch experiments with little training.” 3. Support (some customers) - Reviewer: “Support: the CSMs… are great… which is not always the case for other solutions.” 4. Widgets / speed to deploy - Reviewer highlights “Widgets… quickly validate best practices.”

Negative review themes (with quotes)

Common complaints across review platforms, notably around performance, editor maturity, QA burden, and integration/reporting gaps: 1. Performance / load time concerns - Reviewer: “when executing significant changes, the loading time becomes very long… affects the accuracy and quality of tests.” 2. WYSIWYG/editor limitations and dated feel - Reviewer: “WYSIWYG still looks a bit dated.” - Reviewer: “wysiwyg editor is not the most intuitive when compared to competitors… more convoluted QA process.” 3. Mobile QA and SPA complexity - Reviewer: “QA needs be easier… Improve QA on mobile.” 4. Analytics integration pain (notably GA/GA4) - Reviewer: “integration with GA4 needs to improve.” - Reviewer: “Google Analytics integration is fine but it requires code developing.” 5. Support/communication isn’t consistently strong - Reviewer feedback lists customer success / support team and communicating tool updates as areas for improvement.

Why customers choose AB Tasty over alternatives

Based on reviews and product positioning, buyers often select AB Tasty for:

Targeting/segmentation capabilities and integrations (GA, Mixpanel, CDPs).
Visual experimentation and widget-based changes that reduce the need for engineering in some scenarios.
A broader suite that combines experimentation, personalization, and recommendations.

Why some customers leave / consider alternatives

From competitor comparisons and review feedback, likely churn drivers include:

Need for more advanced statistics/reporting or experimentation governance at scale.
Desire for edge-based decisioning and lower client-side latency.
Better mobile/SPA workflows and reduced QA friction.
Preference for a platform with stronger publicly available security/compliance artifacts.

Vendor-published outcomes (examples)

Vendor case studies report outcomes such as a customer using AB Tasty to increase average order value.

Critical evaluation:

These are vendor-published outcomes; methodologies (baseline periods, attribution, sample size, novelty effects, seasonality controls) are typically not fully disclosed on summary pages.
Treat such outcomes as directional until a full case study with methodology is reviewed and results are validated for sustained impact.

Implementation and time-to-value

Aggregated reviewer feedback indicates a typical time-to-implement around two months for enterprise rollouts.

Interpretation:

This timeframe can be realistic for enterprise rollouts when tagging, governance, training, and analytics integration are included.
Teams expecting rapid time-to-value should scope initial pilots conservatively to reduce implementation overhead.

04Best fit

Best-fit company sizes

Based on review language and enterprise features (SSO, roles), AB Tasty generally aligns with mid-market to enterprise digital businesses, and smaller organizations with well-developed CRO programs.

Strongest verticals / use cases

Common fits include:

E-commerce and retail (recommendations, merchandising, on-site personalization)
Travel and hospitality
Media and subscription businesses
Large lead-gen sites (forms, funnels)

Roles/personas

Decision makers: VP Growth, VP Digital, Head of Product, Head of E-commerce, Head of Experimentation/CRO
End users: CRO managers, product managers, digital analysts, UX designers, marketing ops
Technical enablers: web engineers for SPA integration, performance tuning, and advanced experiments

Qualification criteria (great fit)

The organization can staff QA and experiment implementation adequately.
A requirement for robust segmentation/targeting and integrations exists.
A preference for a single vendor across experimentation, personalization, and recommendations is present.

05The pitch

What the product does (core value proposition)

AB Tasty is a digital experience optimization (DXO) platform focused on: - Experimentation (A/B/n, multivariate, split URL) to improve conversion and engagement. - Personalization via segmentation/targeting and on-site experience changes. - Recommendations & merchandising (capabilities extended through an acquisition of an AI-driven recommendations/search provider). - Feature experimentation / release management (feature flags, rollouts, server-side experiments via “Flagship” SDK tooling). In objective terms: AB Tasty is designed to help product, growth, and marketing teams test and deploy experience changes across web and (to some extent) app/server-side surfaces, with reporting to guide decisions.

Target market and positioning

AB Tasty positions itself as an enterprise/mid-market experimentation and personalization suite aimed at organizations that want: - A visual editor aimed at marketing teams and a widget library for experimentation - Advanced targeting/segmentation (often with analytics/CDP integrations) - Optional technical depth (code editor, SDKs, server-side) A meaningful portion of its market is e-commerce and consumer digital businesses where conversion optimization is a central KPI.

Get a comprehensive analysis of AB Tasty including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Organizations that require a very high level of experimentation statistics governance and reporting transparency
- If an organization needs highly opinionated statistical controls (sequential testing guardrails, false discovery rate controls, etc.), consider vendors that emphasize experimentation rigor.
Organizations with complex SPAs and insufficient QA resources
- Reviews and competitor comparisons indicate SPA/mobile QA can be resource-intensive. If adequate QA resources are not available, evaluate alternatives with different delivery models.
Organizations requiring plug-and-play GA4 integration without development
- Review feedback suggests GA4 integration may require development work; organizations needing zero-development GA4 connectivity should validate integration requirements.
Organizations with extremely high traffic that require flat, predictable pricing
- Traffic-based pricing can be a constraint; organizations seeking predictable, traffic-independent spend should negotiate pricing terms or assess other pricing models.
Organizations requiring mature, publicly documented compliance artifacts immediately
- AB Tasty documents ISO 27001 certification, but procuring teams that require immediately available SOC 2 Type II reports and detailed pen test summaries may need to engage the vendor for evidence.

Disqualifiers (poor fit)

No available engineering capacity for integration and SPA adjustments.
Ultra-performance-sensitive sites where client-side scripts are heavily scrutinized, unless performance is validated through a POC.
Organizations requiring fully transparent, publicly available security attestations and immediate self-serve procurement artifacts.

Known limitations highlighted in reviews

WYSIWYG/editor UX: described as dated or less intuitive than some competitors for some users.
Mobile QA: repeatedly noted as challenging.
Performance impact: heavy client-side changes can increase page load times.
Integration friction: GA/GA4 integration can require development and improvement.

Vendor-acknowledged compliance nuance

AB Tasty documentation explicitly warns that certain legacy cookie deposit methods do not comply with GDPR/ePrivacy and recommends avoiding them in production.

Roadmap / future considerations

Where it struggles (based on reviews)

Mobile QA and complex SPA behavior
Highly complex experiments requiring advanced governance and reporting
Analytics integrations that may require custom development effort

02Why they buy

Validated or partially validated by reviews and product materials:

Advanced targeting and segmentation (frequently noted by reviewers).
Ability for non-technical teams to launch tests with a visual editor and widgets in some scenarios.
Broad platform coverage: experimentation, personalization, and recommendations/merchandising (capabilities extended via the Epoq acquisition).

Areas where competitors may offer advantages:

Experimentation governance and statistical rigor
Edge delivery and reduced client-side latency
Mobile and SPA workflow maturity

03Field reports

This section includes both positive and negative feedback, including direct quotes from review platforms.

Review platform signals (volume & rating)

G2: well rated on G2.
Capterra: very highly rated on Capterra (sample size on the platform is smaller).
TrustRadius: multiple vetted reviews; common pros/cons revolve around targeting, speed to launch, and QA/support communication.

Positive review themes (with quotes)

Common themes across review platforms:

Targeting / segmentation flexibility
- Reviewer: “AB Tasty can be quite targeted… integrate with Mixpanel… set up an AB test only for B2B traffic.”
Usability for non-technical teams
- Reviewer: “user friendly interface that allows non-technical teams to launch experiments with little training.”
Support (some customers)
- Reviewer: “Support: the CSMs… are great… which is not always the case for other solutions.”
Widgets / speed to deploy
- Reviewer highlights “Widgets… quickly validate best practices.”

Negative review themes (with quotes)

Common complaints across review platforms, notably around performance, editor maturity, QA burden, and integration/reporting gaps:

Performance / load time concerns
- Reviewer: “when executing significant changes, the loading time becomes very long… affects the accuracy and quality of tests.”
WYSIWYG/editor limitations and dated feel
- Reviewer: “WYSIWYG still looks a bit dated.”
- Reviewer: “wysiwyg editor is not the most intuitive when compared to competitors… more convoluted QA process.”
Mobile QA and SPA complexity
- Reviewer: “QA needs be easier… Improve QA on mobile.”
Analytics integration pain (notably GA/GA4)
- Reviewer: “integration with GA4 needs to improve.”
- Reviewer: “Google Analytics integration is fine but it requires code developing.”
Support/communication isn’t consistently strong
- Reviewer feedback lists customer success / support team and communicating tool updates as areas for improvement.

Why customers choose AB Tasty over alternatives

Based on reviews and product positioning, buyers often select AB Tasty for:

Targeting/segmentation capabilities and integrations (GA, Mixpanel, CDPs).
Visual experimentation and widget-based changes that reduce the need for engineering in some scenarios.
A broader suite that combines experimentation, personalization, and recommendations.

Why some customers leave / consider alternatives

From competitor comparisons and review feedback, likely churn drivers include:

Need for more advanced statistics/reporting or experimentation governance at scale.
Desire for edge-based decisioning and lower client-side latency.
Better mobile/SPA workflows and reduced QA friction.
Preference for a platform with stronger publicly available security/compliance artifacts.

Vendor-published outcomes (examples)

Vendor case studies report outcomes such as a customer using AB Tasty to increase average order value.

Critical evaluation:

These are vendor-published outcomes; methodologies (baseline periods, attribution, sample size, novelty effects, seasonality controls) are typically not fully disclosed on summary pages.
Treat such outcomes as directional until a full case study with methodology is reviewed and results are validated for sustained impact.

Implementation and time-to-value

Aggregated reviewer feedback indicates a typical time-to-implement around two months for enterprise rollouts.

Interpretation:

This timeframe can be realistic for enterprise rollouts when tagging, governance, training, and analytics integration are included.
Teams expecting rapid time-to-value should scope initial pilots conservatively to reduce implementation overhead.

04Best fit

Best-fit company sizes

Based on review language and enterprise features (SSO, roles), AB Tasty generally aligns with mid-market to enterprise digital businesses, and smaller organizations with well-developed CRO programs.

Strongest verticals / use cases

Common fits include:

E-commerce and retail (recommendations, merchandising, on-site personalization)
Travel and hospitality
Media and subscription businesses
Large lead-gen sites (forms, funnels)

Roles/personas

Decision makers: VP Growth, VP Digital, Head of Product, Head of E-commerce, Head of Experimentation/CRO
End users: CRO managers, product managers, digital analysts, UX designers, marketing ops
Technical enablers: web engineers for SPA integration, performance tuning, and advanced experiments

Qualification criteria (great fit)

The organization can staff QA and experiment implementation adequately.
A requirement for robust segmentation/targeting and integrations exists.
A preference for a single vendor across experimentation, personalization, and recommendations is present.

05The pitch

What the product does (core value proposition)

AB Tasty is a digital experience optimization (DXO) platform focused on:

Experimentation (A/B/n, multivariate, split URL) to improve conversion and engagement.
Personalization via segmentation/targeting and on-site experience changes.
Recommendations & merchandising (capabilities extended through an acquisition of an AI-driven recommendations/search provider).
Feature experimentation / release management (feature flags, rollouts, server-side experiments via “Flagship” SDK tooling).

In objective terms: AB Tasty is designed to help product, growth, and marketing teams test and deploy experience changes across web and (to some extent) app/server-side surfaces, with reporting to guide decisions.

Target market and positioning

AB Tasty positions itself as an enterprise/mid-market experimentation and personalization suite aimed at organizations that want:

A visual editor aimed at marketing teams and a widget library for experimentation
Advanced targeting/segmentation (often with analytics/CDP integrations)
Optional technical depth (code editor, SDKs, server-side)

A meaningful portion of its market is e-commerce and consumer digital businesses where conversion optimization is a central KPI.

Get a comprehensive analysis of AB Tasty including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →