What's New - May 2026

PHP SDK Now Available for Fullstack Experimentation

We released the PHP SDK, making it easier for teams using PHP as their primary stack to adopt Convert for fullstack testing.

This gives PHP-based teams a more comfortable and native path to server-side experimentation and personalization with Convert. More info here.

Major MCP Update Expands Platform Capabilities

This month’s MCP update significantly expands platform capabilities.

The release includes regenerated specs and tools supporting 16 top-level MCP tools, 113 callable actions, new backend operations, and 19 MCP-native workflow prompts. It also improves search and retrieval with OpenAI-compatible search and fetch, a refreshed knowledge base, and a rebuilt semantic hybrid vector search. In addition, the update strengthens reliability through schema and data correctness fixes, stronger guardrails, resilient uploads and retries, expanded test coverage, drift detection, and improved MCP protocol compliance.

Overall, this release makes the platform more powerful, more reliable, and better equipped to support advanced workflows. More info here.

Heatmaps Released for Easier Visualization

We released Heatmaps, giving users an easier way to visualize areas of concentration and interaction.

This makes it simpler to understand where visitors focus their attention and helps teams uncover behavior patterns more quickly during analysis. More info here.

Signals Now Includes Sampling Rate Control

We added sampling rate exposure for Signals, giving users more control over the percentage of recordings they receive.

This improvement makes it easier to fine-tune session capture based on analysis needs, volume preferences, and project scope. More info here.

Revenue per Visitor Added to the Experience Overview Table

While Revenue per Visitor (RPV) is not a new metric, it is now available directly in the experience overview table.

Users can now toggle it in the same way as Conversions per Visitor, making it easier to review primary-goal revenue performance at a glance from the overview screen.

New Scheduled End Date Action for Experiences

We added a new option to the end date settings that lets users choose what should happen when an experience reaches its scheduled end date.

Previously, reaching the end date would complete the experience by default. Now, users can choose whether the experience should be completed or paused, offering more flexibility in how scheduled experiments are managed.

Ongoing Tracking Script Performance Improvements

We also continued improving the efficiency of our tracking script so it loads faster and has less impact on website performance.

While this may not always be directly visible, it reflects our continued investment in optimization and supports our broader Monthly Performance Improvements initiative in the in-app dashboard.