We’re continuously improving Feature Experimentation & Rollouts (FE&R) to make your experience smoother, faster, and more reliable. Here are the latest updates now available:

Data Explorer: Now available in FE&R

The Data Explorer, already available for Web Experimentation, is now accessible in Feature Experimentation & Rollouts. You can now explore and export your server-side data directly from the platform, without relying on external or technical tools like Postman.

With FE&R Data Explorer, you can:

• Query and export metrics (conversion rate, revenue, custom goals, NPS, action counts, etc.)
• Access and export raw hits (SDK events, API calls)
• Apply filters and dimensions (campaign, environment, feature, user properties, time range, etc.)
• Define custom date ranges and result limits
• Generate API payloads directly from the UI

This feature was one of the most requested improvements by our clients. It increases transparency, improves trust in data collection, and brings stronger consistency between client-side and server-side capabilities within One Platform.

👉 Access Data Explorer directly from your FE&R interface.

Live Hits: Real-Time QA for Server-Side

When implementing or debugging a campaign, waiting for aggregated reports can slow you down. With Live Hits, you can now visualize incoming SDK events in real time and instantly verify that your implementation is working as expected.

No more guesswork. No more waiting.

Live Hits significantly improves QA workflows and reduces implementation friction for technical teams.

You can quickly confirm:

• That events are properly triggered
• That traffic is correctly allocated
• That variations are being served as expected

👉 Access in Reporting → Button next to the filter.

Server-Side Reporting: Evolution

AND / OR filter operators

You can now switch between AND / OR operators for multiple values within the same filter type.

This gives you much more flexibility when segmenting your data and running deeper analysis directly inside your reports.

More precise segmentation means more accurate insights.

RevenueIQ*: now available for Server-Side 💰

*RevenueIQ is AB Tasty’s patented statistical engine that transforms experiment results into clear, reliable revenue projections — helping teams move from CRO to true Revenue Optimization by confidently quantifying uplift and ROI for every variation.

RevenueIQ, already available and widely adopted on client-side experimentation, is now live for server-side reports.

You can now project the financial impact of your experiments directly from your server-side reporting.

Available in any report with a transaction goal under the “Revenue stats” tab, RevenueIQ provides:

• Uplift per visitor: estimated revenue increase per visitor once deployed
• Uplift per month: projected monthly revenue impact
• Confidence intervals: lower, median, and upper revenue scenarios
• Revenue chances to win: probability that the variation will increase revenue

This means clearer decisions, fewer inconclusive experiments, and a direct view of real business impact.

You can confidently quantify and share the ROI of every server-side experiment.

Conclusion

These latest enhancements to Feature Experimentation & Rollouts are designed to empower your teams with greater transparency, flexibility, and actionable insights. With real-time data access, advanced reporting options, and robust revenue projections, you can confidently optimize your experiments and drive measurable business impact.

If you’ve ever opened your company’s experimentation dashboard and felt overwhelmed by the sheer number of campaigns, you’re not alone. As businesses grow, so do the number of teams, projects, and experiments running at any given time. Suddenly, what started as a handful of tests can turn into a maze of overlapping campaigns, making it tough to find what you need. 

That’s where Folders & Buckets come in. These two simple features can make a world of difference in how you manage, secure, and scale your experimentation efforts. Here’s how they work, why they matter, and some tips for getting the most out of them.

Too Many Experiments, Not Enough Organization

Picture this: your marketing, product, and development teams are all running their own experiments. Maybe you’ve got a few hundred campaigns live, or maybe it’s closer to a thousand. Either way, it’s easy for things to get messy. Important tests get buried, people accidentally edit the wrong campaign, and sometimes experiments even overlap – skewing your results or causing confusion.

This isn’t just a headache for your data team. It can slow down your whole organization and make it harder to get clear, actionable insights.

Folders: Your Experiment Filing Cabinet

Folders are exactly what they sound like: a way to group and organize your experiments in a way that makes sense for your business. But they’re much more than just a visual aid – they’re a powerful tool for access control and workflow management.

How Folders Work

• Custom Organization: Structure folders by team (e.g., Marketing, Product), by project or sprint, by product line, or even by page type (e.g., Homepage, Checkout). The choice is yours.
• Granular Permissions: Assign users to specific folders with different roles – viewer, editor, or admin. By default, new users see nothing until they’re granted access, minimizing risk and keeping sensitive experiments secure.
• Flexible Access: Users can be given access to multiple folders, with different roles in each. This is perfect for organizations where people wear multiple hats or collaborate across teams.

Why Folders Matter

• Clarity: Users see only the experiments relevant to them, reducing clutter and confusion.
• Security: Sensitive or high-impact experiments are visible only to authorized users.
• Agility: As teams grow or projects shift, folders and permissions can be reorganized on the fly – no need to start from scratch.

Pro Tip: Many organizations use folders to mirror their internal structure, but you can also get creative – organize by campaign type, business objective, or even experiment status.

Buckets: Keeping Experiments in Their Own Lanes

While folders help you organize and control access, Buckets (sometimes called “traffic repartition”) are all about managing how user traffic is allocated across experiments. Think of buckets as traffic lanes on a highway – each experiment gets its own lane, so there’s no risk of collisions.

How Buckets Work

• Traffic Allocation: By default, you can create up to 10 buckets, each representing 10% of your total user traffic. Assign experiments to specific buckets to ensure they don’t overlap.
• Mutual Exclusivity: Experiments in different buckets never see the same users, so results are clean and reliable.
• Planned Flexibility: While the default is 10 buckets, future updates will allow you to customize the number of buckets and the percentage of traffic allocated to each.

Why Buckets Matter

• No Overlap: Run multiple experiments at the same time – on the same page or feature – without worrying about interference.
• Reliable Results: By keeping experiments mutually exclusive, you avoid skewed data and can trust your insights.
• Enterprise-Ready: Especially valuable for organizations with multiple teams running simultaneous experiments.

Why This Matters for Your Team

Folders & Buckets aren’t just “nice-to-have” features – they’re essential for any organization looking to scale experimentation without losing control. They help you:

• Stay organized as your program grows.
• Keep sensitive experiments secure and compliant.
• Empower teams to work independently without stepping on each other’s toes.
• Deliver reliable, actionable insights by preventing experiment overlap.

As digital experimentation becomes a core business function, tools like Folders & Buckets are what separate the leaders from the laggards.

Ready to Get Organized?

If you’re struggling with a cluttered experimentation environment or worried about experiment overlap, it’s time to explore what Folders & Buckets can do for you. Customer Success Manager for more information, and see how easy it is to bring order – and results – to your experimentation program.

Experiment boldly. Organize smartly. Grow faster.

Want to learn more? Check out our documentation (folders/buckets) or contact us for a personalized demo.

FAQs about experimentation organization

How can I stay organized when running lots of experiments?

AB Tasty is built for big teams running many experiments. We offer our users a clear folder structure to group experiments by team, project, product line, or page type, and apply granular permissions so people only see the campaigns relevant to them. This reduces clutter, limits mistakes, and keeps your experimentation environment manageable as you scale.

What are folders in an A/B testing or experimentation platform?

Folders act like a filing cabinet for your tests: you can group experiments in ways that match your organization (e.g., by team, sprint, product, or page type) and assign viewer, editor, or admin roles per folder to control who can see and edit each campaign.

What are buckets in an experimentation platform?

Buckets (or “traffic repartition”) are a way to divide user traffic into separate lanes. Each bucket gets a portion of traffic (e.g., 10%) and experiments assigned to different buckets don’t share users, which keeps tests mutually exclusive.

Which A/B testing solutions help teams stay organized at scale?

The most effective solutions offer both structural tools (like folders with role‑based access) and traffic management features (like buckets for mutual exclusivity), like AB Tasty. Together, these help large organizations keep experiments secure, organized, and analytically sound as their programs grow.

Your search bar is the fastest path to conversion. Yet for too long, site search solutions have been frustrating: complex, rigid, and disconnected from what e-commerce and product teams actually need to do their jobs.

Even customers using the most expensive search solutions told us they were dissatisfied. The tools were too complex, built for developers instead of business teams, and required painful manual work to sync marketing campaigns across their site.

We heard you. Loud and clear.

So we rebuilt Site Search from the ground up. The revamped AB Tasty Site Search is now available—designed to drive revenue, empower your teams, and integrate seamlessly into your workflow.

Semantic Search That Understands Intent

The biggest transformation? We’ve eliminated the endless synonym nightmare.

Traditional search engines rely on keyword matches. If a customer searches for “running shoes” but your product catalog says “athletic footwear,” you lose the sale. Fixing this meant maintaining massive synonym lists that were tedious to build and impossible to keep current.

AB Tasty Search uses a hybrid engine that blends keyword matching with semantic AI. The system understands the meaning behind queries, not just the exact words typed.

The impact:

• Zero “No Results” dead ends: Semantic AI delivers relevant results even when users misspell, use natural language, or describe products contextually
• No manual synonym maintenance: The system handles variations automatically
• Real revenue gains: Early clients report a +11.6% increase in transactions and a +6.9% lift in add-to-cart rates
• Understanding of user needs: We leverage AI to understand user queries without requiring a complex setup.

Built for Business Teams, Not Just Developers

We know the pain of being bottlenecked by engineering resources. Need to spotlight a product for a campaign? Waiting days (or weeks) for dev time kills momentum.

The new AB Tasty Search puts control where it belongs: in the hands of merchandisers and marketing teams.

We provide intuitive low-code/no-code tools that enable rapid iteration without developer dependency. This agility is delivered through two key mechanisms:

1. Widget-based deployment: You can deploy the search functionality quickly using a simple widget that adds an overlay when a user clicks the search bar. This widget-based deployment allows you to challenge your existing solution in days, not months, enabling faster time to value.
2. Intuitive merchandising controls: Merchandisers can optimize ranking, spotlight key products, and tailor results to user behavior. You can easily boost or bury products based on any catalog attribute, set query-specific redirections, and make real-time product ranking adjustments.

The result? True autonomy and agility for non-technical teams.

The Strategic Advantage: A Unified Platform for Discovery

Here’s where it gets really powerful: the revamped Search isn’t a standalone tool. It’s part of your complete optimization platform.

Search, Recommendations, and Merchandising now share the same rules, the same interface, and the same data. That marketing campaign you’re launching? Apply your merchandising logic once, and it works consistently across product discovery, search results, and recommendation widgets.

Why buy Search alongside Recommendations & Merchandising?

• Consistency across channels: Same rules across Search, Merchandising, and Recommendations – no more manual syncing.
• Personalization: Leverage your unified customer data to tailor search results by user type and behavior.
• Simplified implementation, stack, and cost: One vendor, one dashboard, one connection to your catalog, and one source of truth for all your optimization activities.

This unified approach allows you to deploy product discovery as a global strategy, challenge it with unified KPIs and a dashboard, and optimize holistically.

What’s Next? Conversational Discovery

The search bar is evolving, and so is AB Tasty. We are already looking beyond traditional search to deliver a truly multi-modal experience that blends conversational, discovery, and keyword search into one seamless journey.

And with our approach to personalization, every search result can be personalized in real time based on user behavior, preferences, and context—delivering the right products to the right people at exactly the right moment. Read more about AdaptiveCX here.

Our upcoming Shopping Assistant will bring an AI-powered chat interface to your site through the same easy widget deployment. Natural language conversations will guide shoppers to the right products, increasing conversion while reducing returns.

Get Started with AB Tasty Site Search

The revamped AB Tasty Search module is generally available, ready to replace basic native search solutions (like Shopify or Salesforce) or replace your complex, developer-dependent tools.

If you are looking to eliminate “no results” experiences, empower your merchandising teams, and unify your product discovery strategy under one intelligent platform, the time to explore the new AB Tasty Search is now.

Talk to your AB Tasty representative to start testing the new Search module today. The best way to know if it works for you? Test it.

Website performance has never mattered more. Google Core Web Vitals now directly influence organic rankings, mobile conversions continue to dominate, and users expect instant experiences.

In this context, many digital teams ask the same question:

“Will an experimentation or personalization tool slow down my site?”

It’s a valid concern. After all, any third-party script has the potential to impact performance if it’s not engineered carefully.

In this article, we’ll break down what actually affects performance in an experimentation platform — and how AB Tasty has built a performance-first architecture that avoids common pitfalls.

1. The Real Reasons Experimentation Tools Can Slow Down a Website

Not all experimentation platforms behave the same. When performance issues appear, they usually come from a few well-identified causes.

1.1 Heavy, all-in-one tags

Some tools load everything upfront — all features, all experiments, for every visitor — even when most of that code is never used.

This leads to:

• Slower execution in the browser
• More JavaScript to download and process
• Increased pressure on the main thread
• Wasted network bandwidth on unused code

The result: a slower page and unnecessary work for the browser.

1.2 “Anti-flicker” scripts that block the page

To prevent visual flicker, many vendors solve flicker by hiding the page (e.g., opacity: 0) until the experiment loads.

While this may avoid a brief visual change, it comes at a cost:

• The page cannot render immediately
• First visual elements appear later (LCP, FCP)
• It hurts SEO rankings
• Users may face a noticeable “white screen,” especially on slower connections

The page looks stable — but it loads later than it should.

1.3 Limited optimization for modern websites

Modern websites are no longer simple static pages. Single-page applications, server-side rendering, and hydration flows all require precise timing.

When experimentation scripts are not adapted to these architectures:

• They may re-run unnecessarily
• They can interfere with rendering
• They introduce delays that affect performance

2. AB Tasty’s Philosophy: Performance by Design, Not by Patch

At AB Tasty, we believe an experimentation platform should contribute to user experience — not compromise it. That’s why performance is woven directly into our architecture.

2.1 A lightweight, modular tag

AB Tasty uses a dynamic import system:

• Visitors only load the code that applies to them
• Unused features are never downloaded
• The tag remains lightweight and efficient

This means:

• Faster execution
• Less JavaScript to process
• Reduced impact on the browser

 The result: faster page rendering and minimal impact on Core Web Vitals. 

 3. No Anti-Flicker Masking — A Choice That Matters

Instead of masking slow performance with a CSS workaround, AB Tasty focuses on solving the root cause: delivering variations fast.

Why we don’t rely on anti-flicker masking:

• It hides the website and delays the first visible content
• It sends negative signals to Google
• It degrades UX on slower devices
• It increases the risk of bounce

How AB Tasty avoids flicker instead

AB Tasty applies variations:

• In real time, as the page updates
• In sync with the browser’s rendering cycle
• Before the human eye can perceive any visual change

 Visitors always see a stable page — without flashes, jumps, or white screens.

 4. Designed for Modern Architectures

AB Tasty is built to work smoothly with today’s most common tech stacks:

• Single-page applications (React, Vue, Angular…)
• Server-side rendering frameworks (Next.js, Nuxt.js…)
• Hybrid architectures

Our tag intelligently adapts to:

• Route changes
• Delayed or lazy-loaded components
• Hydration phases
• Dynamic content updates

 Experiments run reliably — without reloading pages or slowing down the app.

5. Measure the Performance Impact — Transparently

With the Performance Center, teams can:

• Monitor tag size
• Track the impact of each campaign
• Follow performance guidelines and recommendations

This gives CRO and technical teams full visibility and control over experimentation performance.

Conclusion: You Can Experiment Without Sacrificing Speed

A fast digital experience and an experimentation program are not mutually exclusive.

With its modular architecture, modern rendering logic, and performance-first philosophy, AB Tasty enables brands to run impactful campaigns without jeopardizing SEO or UX.

If performance is a concern for your engineering or CRO teams, we’d be happy to share:

• Performance benchmarks
• Technical documentation
• Best practices for Core Web Vitals
• Case studies from top global brands

Experiment boldly — with a platform engineered for speed.

FAQs

Does A/B testing slow down your website?

Yes, but AB Tasty minimizes it. Our tag delivers < 100ms load time, < 500ms execution, and < 10ms from cache—making us 2x faster than Kameleoon. Plus, we block releases if Core Web Vitals degrade by > 2%.

Does A/B testing affect Core Web Vitals?

It can — but AB Tasty minimizes this impact through dynamic imports, optimized rendering logic, and non-blocking execution.

Do I need anti-flicker for A/B testing?

Most of the time, no. Anti-flicker masking can degrade SEO and create a poor user experience.

Is AB Tasty fast?

Yes — benchmarks from independent sources consistently show AB Tasty among the fastest experimentation tags on the market.