Framer ships custom A/B test distribution and analytics search

Here at industry sources, we tracked Framer's latest release closely because it addresses a critical gap in their experimentation workflow. Framer has added Custom Distribution for A/B tests, meaning builders can now control traffic allocation beyond simple 50/50 splits. This is table-stakes functionality for real conversion optimization work - you need to test new variants with controlled exposure before ramping to production.

The platform also shipped four complementary improvements: folder organization in the sidebar reduces friction for larger projects, A/B testing support for CMS pages extends experiments beyond static content, and a search function in the analytics dashboard lets you actually find what you're looking for instead of scrolling through noise.

These aren't flashy features. They're operational necessities. Anyone running serious traffic through Framer expects to allocate 10% to a variant, measure carefully, then decide. Custom distribution makes that workflow native instead of requiring external tools or workarounds.

• Custom distribution lets you set non-standard traffic splits (e.g., 85/15 instead of 50/50)
• CMS page testing expands experiments beyond static layouts to dynamic content variants
• Sidebar folders scale project organization without requiring external naming conventions
• Analytics search cuts time spent hunting specific metrics or page variants

Custom distribution solves a real problem: gradual rollout. You can now run a variant at 5% traffic, validate it doesn't break conversion funnels, then increment to 25%, then 50%. This is how production-grade testing works. Before this, Framer was locking you into binary splits or forcing you to use external analytics platforms to manage allocation.

The CMS testing addition matters more than it appears. If your content strategy involves testing headline variations, product descriptions, or metadata at scale, you now do that in Framer instead of coordinating between your design tool and a separate experimentation platform. That's consolidation that reduces toolchain complexity.

The analytics search function is a productivity multiplier. On a site with 20+ variants running, finding which version of the homepage performed best without search is genuinely painful. This forces you to actually use Framer's built-in analytics instead of exporting to Sheets or jumping to GA4.

• Validate variants at low traffic before full rollout - reduces risk of breaking revenue flows
• Keep CMS testing inside Framer instead of fragmenting between design and experiment platforms
• Make data-driven decisions faster by actually navigating your analytics instead of memorizing variant names
• Folder organization means new team members spend less time hunting for the right project state

Framer shipping custom distribution signals that no-code platforms are graduating from prototype tools to conversion optimization infrastructure. This isn't new for Webflow or Wix, but Framer's design-first positioning meant experimentation was historically secondary. Priorities are shifting.

The fact that they're bundling folder organization, CMS support, and analytics search together shows they're optimizing for real workflows instead of edge cases. They're saying: this is how builders actually work, and we're building the entire experience around that, not bolting features on top.

The momentum in this space continues to accelerate.

• No-code platforms are competing on experimentation rigor, not just template breadth
• Analytics tooling quality is now a retention factor - builders will leave if data discovery is painful
• CMS integration with testing is becoming baseline, not premium