Skip to content
Hosted in Europe. Your test data is stored in the European Union.Hosted and stored in EuropeLearn more
probant.
Log inCreate your workspace
From idea to rollout, in one tool.Product overview

Prepare

Decide

Roll out

Scale

Visual editorBuild the variant without a developer, with the assistant.Test plan and durationDuration calculated before the first visitor.IdeasEach idea estimated from your past tests.Metrics and marginNo-code goals, margin calculated from your orders.
ReportsA one-sentence verdict, with revenue and margin in euros.Session recordings and click mapsSee what visitors do with each variant.GuardrailsA test that breaks something stops on its own.
RolloutsStep by step, with automatic rollback.PersonalizationAn experience for one audience, measured against a holdout.Feature flagsTurn a feature on by rule, and off in one click.
Learnings libraryThe effects of your finished tests, on one scale.Installation and integrationsTwo lines of code, in the browser or on the server.Team and governanceRoles, launch approvals, and an audit log.
Explore the demo Pricing
The rules behind every verdict, set before launch.The full method

The method, step by step

How Probant decidesThe peeking trapThe winner’s curseThe statistics engineGlossaryVerify a report
MethodThe winner’s curseWhy the reported gain is too good, on average.See the correction
Revenue per visitor · Free shipping progress bar
Measured lift+6.0%
After correction+4.9%
+€125,700per month after correction, instead of +€153,300

Corrected using the demo store’s 48 finished tests.

Rerun the simulation with your own number of tests and duration.A/A simulator
By site area and by team.All use cases

You are…

Know what pays off, without a statistician.

The features that matter to you:

ReportsA one-sentence verdict, with revenue and margin in euros.Metrics and marginNo-code goals, margin calculated from your orders.Visual editorBuild the variant without a developer, with the assistant.See the use case
Cart · demo storeFree shipping progress barConclusive. Proven gain+€125,700 per month · revenue per visitor +6.0%, range +2.2% to +10.0%

Computed by the engine on a demo test.

By site areaCart and shippingProduct pageCheckoutMobile navigationCategory pages
Explore the demo
Blog, docs, and tools.All resources
A/A simulatorSee for yourself what peeking costs.Why checking a test every day produces false winners.Run the simulator
BlogMethod, measurement, and lessons learned.
Nov 12What is an A/B test? Definition, steps, and an exampleNov 7Measure margin, not just revenueNov 7The winner’s curse: why the announced gain falls short
All articles
Duration calculatorHow many days it takes to detect the effect you want.DocumentationInstall the script, handle consent, send events.Video tutorialsInstall, launch a test, and read a report, on video.ComparisonsProbant vs. other tools, with sources.AB TastyKameleoonVWOOptimizelyAdobe TargetDynamic Yield+11 more
ChangelogWhat changed in Probant, by date.Case study formatContext, test, result, and decision, on the demo store.Migrate to ProbantImport your AB Tasty, VWO, or Kameleoon history, recalculated by Probant.
Articles, docs, and calculators, free to use.
One fixed monthly price, no overage charges.See pricing

How many visitors do you test each month?

A tested visitor is each unique visitor who sees a test or a rollout during the month. It’s the only thing that sets the price.

Billing
Your planEssential€590/monthor €5,900 per yearFor a store that tests continuously, down to revenue per visitor.
  • Up to 250,000 tested visitors per month
  • All features, unlimited tests within your volume
  • No overage charges
Choose Essential
Your bill never goes over your plan. Once you reach the volume, running tests keep going.Billing questions

Probant vs. AB Tasty

Both tools compared point by point, based on AB Tasty’s and Wingify’s public documentation, accessed November 7, 2026. Every statement about AB Tasty links to its source.

AB Tasty is now part of Wingify.

AB Tasty and VWO merged under the Wingify brand (announced January 20, 2026); abtasty.com now redirects to wingify.com.12 Wingify states that it keeps running both platforms, VWO and AB Tasty, and that existing contracts and pricing are unchanged.34 The facts below come from AB Tasty’s documentation (docs.abtasty.com), still online, and from Wingify’s pages.

51 sources from 27 official pages, accessed November 7, 2026.

What AB Tasty offers.

AB Tasty was founded in Paris in 2013.5 Wingify describes it as a comprehensive platform that combines A/B testing, feature flags, AI personalization, and product optimization for large enterprises.6 Its main statistical engine is Bayesian.7

Probant is for sites that want A/B test verdicts that hold up, with a plan set before launch and guardrails monitored through rollout. It measures what each conversion is worth: the margin on an order, a qualified or signed lead, a paid subscription.

The differences, point by point.

On the left, what AB Tasty’s public documentation says, each sentence with its source. On the right, what Probant does. “Not mentioned” means nothing was found in that documentation, which does not prove a feature is missing.

Probant and AB Tasty, point by point. Note numbers link to the sources at the bottom of the page.
CriterionAB TastyProbant
Statistical methodBayesian by default (beta-binomial model): “chance to win” and a 95% interval.78 Frequentist mode is available on request; the main framework remains Bayesian.9 Multi-armed bandit dynamic allocation available.10Frequentist, with a sequential plan set before launch: target effect, duration, and checkpoints. The verdict fits in one sentence, with a 95% range. Where to check
PeekingThe documentation recommends waiting until the campaign is ready, at least 14 days live, before analyzing.11 “Sequential Testing Alerts” are meant to spot losing variants early.12 A sequential correction for declaring a winner is not mentioned in their public documentation (as of November 7, 2026).Decisions are only made at planned checkpoints, with O’Brien-Fleming boundaries: very strict at first, close to the usual threshold at the end. During a rollout, ranges are always valid (mSPRT), so you can check them at any time. Where to check
Traffic split (SRM)Sequential detection (S-SRM) with real-time alerts, threshold of 0.01.1314 Limited to an early access program, on request.15 The documentation describes an alert; automatic blocking of the test is not mentioned there (as of November 7, 2026).14The traffic split is checked with a chi-square test every time the report is read. If the split is off, the test moves to “blocked” status and no winner is declared. Where to check
Guardrails“Sequential Testing Alerts” apply to the primary goal: they can automatically stop a server-side campaign in which a variant is losing conversions.1617 Automatic rollback on KPIs for progressive rollouts, documented in a section marked “Deprecated.”18Guardrail metrics are tracked with their range; a guardrail is only breached if the whole range crosses the limit. A breached guardrail blocks the test’s verdict, stops a running test on its own, and during a rollout moves visitors back to the original automatically. Where to check
Gradual rolloutsFeature flags and rollouts through the Feature Experimentation & Rollout module.19 Rollout in chosen steps, documented in the deprecated “Flagship” section.20Steps of 25% → 50% → 100% by default, 10% → 25% → 50% → 100% in cautious mode. Automatic rollback when a guardrail is breached; an exposed visitor stays exposed in the following steps. Where to check
Multi-armed banditMulti-armed bandit dynamic allocation available.10Optimization test: Thompson sampling, reallocated at most once a day, with a minimum share per variant. It maximizes a conversion rate, or an amount per visitor such as revenue: purchase probability and average order value drawn from their distributions, with values capped at a percentile as in an A/B test. Optionally, shares per device (mobile, tablet, desktop): one draw per device, each with its own learning and floor. A visitor always keeps their variant: a new split only applies to visitors who arrive after it. The screen says so: it maximizes conversions (or the amount per visitor) during the test, without proving that a variant is better. The difference is read period by period (and device by device), with no declared winner; the CSV export gives the same reading. Where to check
Revenue and margin per visitorStandard reporting does not show statistical indicators for revenue.21 For average order value, a Mann-Whitney test with no interval: the direction of the effect, not its size.22 RevenueIQ combines conversion and average order value into one core metric, revenue per visitor, and projects a gain per visitor.2324 Margin per visitor: not mentioned in their public documentation (as of November 7, 2026).Revenue and margin per visitor, each with its range; the gain is stated in euros. Margin is calculated on the server from reconciled orders, the cost of each product (Shopify or CSV), and store fees; no margin verdict below 90% of revenue covered by known costs. Where to check
Winner’s curseNot mentioned in their public documentation (as of November 7, 2026).The reported gain is corrected for the winner’s curse by Bayesian shrinkage toward the effects of the store’s past tests. Where to check
Bayesian modeBayesian by default for conversion rates (beta-binomial model), with a “chance to win.”7 With several variants, the Bonferroni correction applies to the “chance to win,” not to the intervals.25Optional, off by default: a Bayesian reading next to the verdict, with the probability that the variant does better, the credible interval, and the expected loss of each choice. The prior is centered on zero and as wide as the effects measured by the store’s completed tests; while there are too few of them to estimate it, the Bayesian reading is not shown. The decision always follows the sealed plan; when the two readings disagree, the report explains why. Where to check
Multiple comparisonsBonferroni correction applied to the “chance to win” when there are several variants, not to the intervals.25Segment comparisons are corrected with the Holm method. With several variants, the error risk is split across comparisons (Bonferroni). Where to check
Multivariate testingAll combinations of the sub-tests’ variations are created and shown at random.26 More sub-tests and variations require more traffic.27Full factorial design generated by Probant: two to four sections, each with two to four levels, up to sixteen combinations, each served as a variant. Main effects of each section across all traffic and interactions between two sections, corrected with the Holm method on the comparisons stated in the plan. Based on the workspace’s measured traffic, the plan says whether the test can reach a conclusion and suggests removing a level or a section; no best combination is declared without a check. Where to check
Variance reduction (CUPED)Not mentioned in their public documentation (as of November 7, 2026).CUPED applied to live test reports, using each visitor’s history before their first exposure; without history, the difference stays unadjusted and the report says so. Where to check
Visual editorThe editor embeds the site’s HTML in an iframe, as published when the editor opens.28 Without the tag on the page, a Chrome extension loads the site in the editor.29Two ways to edit, producing the same changes: a page preview loaded by Probant, without its scripts, or the live page on the site, scripts included. On the site, the editor is loaded by the script already installed, through a short-lived signed link for one draft and one variant, with no browser extension. It only sends the chosen changes to Probant. Where to check
WidgetsWidget library: a configuration can be saved as a preset for other campaigns.30 The countdown runs to an end date and can be placed in a pop-in, a banner, or anywhere on the page.3132Banner, countdown, pop-up, badge, reassurance, action bar, delivery date, social proof, promo code, free shipping, and survey, set up without code in the editor and saved in the workspace library for other tests. A widget is just a set of ordinary changes: escaped text, links over https or to the site, and styles applied without a style attribute, so a strict CSP does not need loosening. The countdown follows the site’s time zone and disappears at the deadline; the pop-in opens on arrival, on exit intent, or after scrolling, closes with the keyboard, and does not reappear during the visit if consent allows. Their small modules only load for visitors in the variant. The delivery date is calculated in the visitor’s browser (cutoff time, business days, public holidays); social proof shows the exact number of purchases received over a rolling week, and only above a threshold. The survey asks up to 8 questions (closed answers, recommendation scale, open question) with conditional logic, on the page or through a link outside the site (email, QR code), based on 70 templates (recommendation, satisfaction, effort, checkout blockers, cancellation, concept test, multi-question surveys…); open answers are redacted before sending (email addresses, phone numbers, cards, IBANs), kept for 180 days, and grouped by theme; each question is read by variant, with its range and response rate, and comparisons across all questions are corrected together; a response through a link is attached to the variant the visitor saw, recalculated by Probant, or stays outside the test. Where to check
Script and flickerThe synchronous tag is recommended against flicker; it then blocks page rendering.33 Blocking initial tag under 3 kB, 35 kB when empty, about 70 kB of shared functions; AB Tasty considers a tag over 125 kB too heavy.34353637 An “anti-flicker” code that hides the page is available on request, but not recommended.38 Server-side option through the SDK or the Decision API.39Script under 7 KB compressed, loaded asynchronously, that does not hide the page while it loads. Server-side assignment available, for a display with no flicker at all. Where to check
Granular permissionsFixed roles: the “Creator” role sets up a campaign without launching it, and a “User” or “Admin” approves it.40 In Feature Experimentation & Rollouts, folder-level permissions for a user or a team.41Four fixed roles, plus custom roles the owner builds from a catalog of named permissions: prepare, launch and stop, roll out, approve a launch, write variant JavaScript, manage flags, metrics, margin, members, and keys. No privilege escalation: billing, roles, transfer, and deletion of the workspace stay with the owner; no one can grant more than their own permissions, and an API key cannot exceed its author’s. Where to check
Data hostingWingify’s subprocessor list has a section for the AB Tasty application: Google Cloud (EU, United States, India), ClickHouse (EU and United States), AWS (“Global”).42434445 AB Tasty’s own documentation does not mention a hosting region (as of November 7, 2026).Database and compute in Amsterdam, with Scaleway, in the European Union. Scaleway, which hosts the database and compute, is a French company. Published subprocessor list: Scaleway (Amsterdam, Netherlands (nl-ams region), in the European Union), Brevo (European Union: servers in France and Germany, encrypted backups in Belgium (Google Cloud), according to Brevo), Mistral AI (European Union by default (European API endpoint), according to Mistral), ClickHouse (option not used), Stripe (Contract with Stripe Payments Europe, Ltd. (Ireland); data transferred to Stripe, LLC (United States), according to Stripe), Sentry (European Union: Frankfurt (Germany), including backups, according to Sentry). Depending on the feature used, Mistral may temporarily transfer data outside the European Union to the subprocessors it publishes; its data processing agreement limits these transfers to countries the EU recognizes as adequate, or covers them with standard contractual clauses. Stripe transfers payment data to Stripe, LLC, in the United States, under the Data Privacy Framework and, failing that, standard contractual clauses. Whatever region is chosen, Sentry may keep the data of Probant’s Sentry account (members, settings, audit log, project descriptions) in the United States; reported errors stay in Frankfurt. Where to check
Consent by defaultThree modes, including “do not restrict cookie deposit” with no consent requested, and delegation to a third-party tool or to the tag.4647 Two cookies can exist for a few microseconds without consent.48 First-party ABTasty cookie with a 13-month lifetime.49Consent required by default: no cookie, no assignment, and nothing sent before the visitor agrees. Consent given mid-page: the page does not change in front of the visitor; their variant starts on the next page. First-party cookie, lasting 390 days at most, never extended. Where to check
Pricing modelNo public pricing: a custom proposal based on monthly active users (MAU).5051 abtasty.com/pricing redirects to Wingify’s pricing page.2 Overage policy: not mentioned in their public documentation (as of November 7, 2026).Creating a Probant workspace is free; paid plans cost €590 to €1,990 per month depending on the number of tested visitors (2 months free with annual billing), with no overage charges. Agency plan: 1,000,000 tested visitors per month, shared across client workspaces, from 3 workspaces, for €1,490 per month or €14,900 per year. Where to check

What AB Tasty also does.

Probant shares these points with AB Tasty.

  • An interval next to the lift

    AB Tasty shows a 95% interval in addition to the raw lift.8

  • A traffic split check

    Sequential SRM detection with real-time alerts, in early access.1315

  • Automatic stop of a losing campaign

    “Sequential Testing Alerts” can stop a server-side campaign on their own and send an email.16

  • Flags, rollouts, and server side

    Feature flags and rollouts through SDKs or the Decision API.1939

  • Revenue per visitor

    RevenueIQ estimates revenue per visitor and the gain a winning variant could bring.2324

  • Consent delegation

    Consent can be handled by a third-party tool (TMS or CMP) or by the AB Tasty tag.47

When to choose AB Tasty over Probant.

Based on AB Tasty’s public documentation.

  • You want tests, flags, and personalization in one tool

    AB Tasty combines A/B testing, feature flags, AI personalization, and product optimization.6

  • You prefer a Bayesian reading or dynamic allocation

    The main engine gives a “chance to win.”7 Multi-armed bandit allocation is available.10

  • You want a custom-built offer

    Wingify offers custom proposals rather than fixed plans, and targets large organizations.650

What sets Probant apart.

These points are not in AB Tasty’s public documentation, accessed November 7, 2026. A missing mention does not prove a feature is missing; if these points matter to you, ask AB Tasty.

  • Margin per visitor

    Probant measures revenue and margin per visitor, each with its range.

    AB TastyMargin per visitor is not mentioned in their public documentation (as of November 7, 2026).

    Learn more

  • Winner’s curse correction

    The reported gain is corrected by Bayesian shrinkage toward the effects of the store’s past tests.

    AB TastyA winner’s curse correction is not mentioned in their public documentation (as of November 7, 2026).

    Learn more

  • Checkpoints for declaring a winner

    O’Brien-Fleming boundaries, set at launch, determine when a winner can be declared.

    AB Tasty“Sequential Testing Alerts” target losing variants.12 A peeking correction for declaring a winner is not mentioned in their public documentation (as of November 7, 2026).

    Learn more

  • SRM that blocks the verdict

    A traffic split imbalance moves the test to “blocked” status, and no winner is declared.

    AB TastyAB Tasty’s documentation describes an SRM alert.14 Automatic blocking of the test is not mentioned there (as of November 7, 2026).

  • A stated hosting region

    Database and compute in Amsterdam, with Scaleway, in the European Union.

    AB TastyAB Tasty’s own documentation does not mention a region (as of November 7, 2026); only Wingify’s subprocessor list gives one.42

Frequently asked questions.

Does AB Tasty still exist after the merger with VWO?

Yes. Wingify states that it keeps running both platforms, VWO and AB Tasty.3 Existing contracts, pricing, service levels, and support are announced as unchanged.4

Does AB Tasty correct for peeking?

Its main engine is Bayesian, and its documentation recommends waiting at least 14 days before analyzing.711 “Sequential Testing Alerts” are meant to spot losing variants early.12 A sequential correction for declaring a winner is not mentioned in their public documentation (as of November 7, 2026). Probant sets checkpoints before launch and only concludes at those points.

How much does AB Tasty cost?

Wingify does not publish pricing: each proposal is custom, based on monthly active users.5051 Creating a Probant workspace is free; paid plans cost €590 to €1,990 per month depending on the number of tested visitors (2 months free with annual billing), with no overage charges.

Sources.

Official pages from AB Tasty and Wingify, accessed November 7, 2026. Quotes are reproduced in their original language.

  1. Source 1: wingify.com/blog/vwo-and-ab-tasty-join-forces
    I am incredibly excited to announce that VWO and AB Tasty are joining forces, subject to customary closing conditions.
  2. Source 2: www.abtasty.com/pricing

    This address redirects to wingify.com/pricing.

  3. Source 3: wingify.com/llm-info
    The merger expanded Wingify’s product capabilities, global reach, and expertise while continuing to support the trusted VWO and AB Tasty platforms.
  4. Source 4: wingify.com/blog/vwo-and-ab-tasty-join-forces
    All existing client relationships, contracts, pricing, service levels, and support remain unchanged.
  5. Source 5: wingify.com/llm-info
    Founded: VWO founded in 2010; AB Tasty founded in 2013 (Paris); merged under Wingify in 2026
  6. Source 6: wingify.com/llm-info
    Over time, it expanded globally and evolved into a comprehensive platform that combines A/B testing, feature flags, AI-powered personalization, and product optimization for enterprise organizations.
  7. Source 7: docs.abtasty.com/reporting-and-performances/reporting/understand-the-statistics-behind-your-reports/statistics-for-the-reporting
    For conversion data, corresponding to the notion of success and failure rate we use a Bayesian framework.
  9. Source 9: docs.abtasty.com/reporting-and-performances/reporting/frequentist-analysis-mode
    While our primary framework is Bayesian, some users prefer Frequentist analysis.
  10. Source 10: docs.abtasty.com/web-experimentation-and-personalization/traffic-allocation/dynamic-allocation
    Dynamic traffic allocation is based on a statistical research topic called “multi-armed bandit”.
  12. Source 12: docs.abtasty.com/web-experimentation-and-personalization/campaign-flow-advanced-options/sequential-testing-alerts
    Sequential Testing Alerts offers a sensitivity threshold to detect underperforming variations early and trigger alerts or pause experiments.
  13. Source 13: docs.abtasty.com/reporting-and-performances/reporting/sample-ratio-mismatch
    To enhance efficiency, a Sequential algorithm layer has been integrated into the SRM, resulting in the S-SRM. This addition enables real-time alert detection, allowing you to take immediate action.
  14. Source 14: docs.abtasty.com/reporting-and-performances/reporting/sample-ratio-mismatch
    The Sequential approach follows a frequentist methodology, relying on p-value principles for detection. The chosen significance threshold is 0.01.
  15. Source 15: docs.abtasty.com/reporting-and-performances/reporting/sample-ratio-mismatch
    This feature is currently part of an Early Adopters program. Please contact your CSM to benefit from it.
  17. Source 17: docs.abtasty.com/web-experimentation-and-personalization/campaign-flow-advanced-options/sequential-testing-alerts
    This alerting system is based on the percentage of conversions lost per variations.
  18. Source 18: docs.abtasty.com/flagship-deprecated/steps-configuration/using-the-automatic-rollback-option
    When the conditions are met, the progressive rollout feature will be rolled back, which means that no more of the targeted visitors will see the feature.
  19. Source 19: docs.abtasty.com/feature-experimentation-and-rollout/campaign-creation/how-to-create-feature-toggles-and-manage-rollouts
    This how-to provides a comprehensive guide to setting up a feature toggling and managing rollouts on the AB Tasty FE&R platform, detailing each step from feature flag creation to campaign activation.
  20. Source 20: docs.abtasty.com/flagship-deprecated/use-cases/configuring-a-progressive-rollout
    A Progressive rollout (or Progressive deployment) enables you to progressively release a feature to your users by choosing each deployment step and the proportion of traffic allocated to your users.
  21. Source 21: docs.abtasty.com/reporting-and-performances/reporting/understand-the-statistics-behind-your-reports/statistics-for-the-reporting
    Statistical indicators are not displayed with the following metrics: Transaction growth metrics for average product quantity, price, and revenue
  22. Source 22: docs.abtasty.com/reporting-and-performances/reporting/understand-the-statistics-behind-your-reports/statistics-for-the-reporting
    This test does not provide a confidence interval, so it only tells if the average cart value goes up or down, but no information is given about the estimated gain.
  23. Source 23: docs.abtasty.com/reporting-and-performances/reporting/campaign-reporting/reporting-insights-with-evi-explore-powered-by-revenueiq/understand-the-practical-use-of-revenueiq
    Under the hood, RevenueIQ combines conversion and AOV results into a central metric: visitor value (RPV).
  24. Source 24: docs.abtasty.com/reporting-and-performances/reporting/campaign-reporting/reporting-insights-with-evi-explore-powered-by-revenueiq
    This metric shows the most probable incremental revenue that a winning variation could generate per visitor.
  25. Source 25: docs.abtasty.com/reporting-and-performances/reporting/understand-the-statistics-behind-your-reports/statistics-for-the-reporting
    When the Bonferroni correction is applied, there may be inconsistencies between the chance to win and the confidence interval displayed in the confidence interval tab. This is because the Bonferroni correction does not apply to confidence interval.
  27. Source 27: docs.abtasty.com/web-experimentation-and-personalization/campaign-creation-and-dashboard/how-to-create-a-campaign/experimentations/how-to-create-a-multivariate-test
    The more subtests with variations you configure, the more traffic you need to allocate the different combinations.
  28. Source 28: docs.abtasty.com/web-experimentation-and-personalization/editors-and-widget/visual-editor/discovering-the-visual-editor
    The editor embeds the website HTML in an iframe, so what loads at the moment you open the editor is the code currently published on the website.
  29. Source 29: docs.abtasty.com/web-experimentation-and-personalization/editors-and-widget/visual-editor/discovering-the-visual-editor
    If you can’t install the AB Tasty tag but you absolutely need to load your website in the editor, we provide a Chrome extension
  30. Source 30: docs.abtasty.com/assets-library/widget-library
    Save widget configurations as reusable presets for future campaigns.
  31. Source 31: docs.abtasty.com/web-experimentation-and-personalization/editors-and-widget/list-of-widgets/ab-tasty-prebuilt-widgets/countdown-widget
    As this widget is a countdown, the first thing you will be asked to do is define an end date and time.
  32. Source 32: docs.abtasty.com/web-experimentation-and-personalization/editors-and-widget/list-of-widgets/ab-tasty-prebuilt-widgets/countdown-widget
    free placement (which allows you to place the widget wherever you want in the page flow)
  33. Source 33: docs.abtasty.com/help-center/troubleshooting/troubleshooting-i-see-the-original-version-very-briefly-before-i-see-the-variation-flickering
    Synchronous loading will block the rendering of the page until the tag is fully loaded, reducing the chance of flickering.
  34. Source 34: docs.abtasty.com/client-side/tag/readme-1/tag-size
    the initial render blocking tag: less than 3 kB
  35. Source 35: docs.abtasty.com/client-side/tag/troubleshootings/tag-troubleshooting-performance
    Our tag is 35 kB weight when empty, additionnal needed modules may be downloaded asynchronously.
  36. Source 36: docs.abtasty.com/client-side/tag/readme-1/tag-size
    AB Tasty's shared features: about 70 kB
  37. Source 37: docs.abtasty.com/client-side/tag/troubleshootings/tag-troubleshooting-performance
    We usually consider an AB Tasty tag going over 125 kB is too heavy to comply with good performances.
  38. Source 38: docs.abtasty.com/help-center/troubleshooting/troubleshooting-i-see-the-original-version-very-briefly-before-i-see-the-variation-flickering
    For some customers, we can provide an ‘anti-flicker’ code that hides the original version of the site as long as the AB Tasty tag (and therefore the campaigns and their modifications) is not loaded on the page.
  40. Source 40: docs.abtasty.com/account/account-management/how-to-manage-users
    The Creator role can configure a campaign but cannot launch it. A user with User or Admin rights must validate the campaign.
  41. Source 41: docs.abtasty.com/feature-experimentation-and-rollout/user-and-access-management/folder-permissions
    To avoid configuration mistakes and maintain governance, you can assign specific permissions to specific users or teams per folder.
  42. Source 42: wingify.com/compliance/subprocessors
    Section B – AB Tasty (app2.abtasty.com) and Additional Sub-Processors for the Combined Wingify and AB Tasty Portfolio
  43. Source 43: wingify.com/compliance/subprocessors
    Google Cloud Platform (Google LLC) Cloud Hosting Services 1600 Amphitheatre Parkway, Mountain View, California, U.S.A EU, USA, India
  44. Source 44: wingify.com/compliance/subprocessors
    Clickhouse Cloud Hosting Services 650 Castro St., Suite 120 #92426 Mountain View, CA 94041, U.S.A EU and USA
  45. Source 45: wingify.com/compliance/subprocessors
    Amazon Web Services (Amazon.com, Inc.) Cloud Hosting Services – Storage for personalization and targeting. 410 Terry Avenue North Seattle, WA 98109-5210, U.S.A Global
  46. Source 46: docs.abtasty.com/account/performance-and-security/consent-policy---cookies-storage-and-privacy
    Not restricting cookie deposits. This means no consent is requested from the visitors and the campaign is automatically displayed and data tracked.
  47. Source 47: docs.abtasty.com/account/performance-and-security/consent-policy---cookies-storage-and-privacy
    Delegating the consent to the AB Tasty. In this case, the tag will try to determine whether the visitor gave their consent on the website before tracking them and collecting their data.
  48. Source 48: docs.abtasty.com/account/performance-and-security/consent-policy---cookies-storage-and-privacy
    This results in both cookies being declared even without consent and for a very short period of time (in microseconds).
  49. Source 49: docs.abtasty.com/account/performance-and-security/consent-policy---cookies-storage-and-privacy
    This is a first-party cookie that has a lifetime of 13 months.
  50. Source 50: wingify.com/pricing
    Your business doesn’t fit a template, neither does our pricing. No fixed plans. Just a custom proposal built around your goals and scope.
  51. Source 51: wingify.com/pricing
    Yes. Pricing is based on your Monthly Active Users (MAUs), depending on the product.

Migrate from AB Tasty

Your AB Tasty history can be imported and is reread by Probant’s engine: every verdict is recalculated from visitors and conversions.

Migrate from AB TastyExplore the demo
  • Open demo, no sign-up
  • Free to start, no overage charges
  • Database and compute in Amsterdam, with Scaleway