April 2026 — Audience engagement, smoother editing, and steadier sync

You can now compare how much different audience segments browse your site, not just how many people belong to them. April also brings fixes for interrupted typing, outdated survey answers, and delays getting data into your email platform.

See which segments explore more of your site

New Engagement lift indicators show whether people in a segment view more or fewer pages than the rest of your audience. Hover over a lift indicator on a question or segment-group card to see the comparison, including a sampling notice when applicable. Righty and connected AI assistants can also compare segments by engagement, goal conversions, or offer conversions. Learn more about understanding your audience.

Enlarge

Team question card showing answer counts, percentage shares, lift and response rateOriginalOriginal

Keep your edits while saves happen in the background

Typing in questions, flow steps, conditions, and offer URLs is smoother, with fixes for lost keystrokes, jumping cursors, and refreshes overwriting in-progress edits—even just after publishing. Inline AI helpers, including phrase personalization, now stay draft-only until you choose Publish. If you’d rather control refreshes yourself, Settings → Advanced includes Auto refresh project configuration data from server. Here’s how to manage automatic refresh.

Enlarge

Advanced settings for configuration synchronization and project behaviorOriginalOriginal

Keep contact data aligned with the latest answer

When an identified visitor answers a survey again, their new selection replaces the old one before syncing, including choices they’ve deselected from a multiple-answer question. In Sync, customized field values now survive reloads, removing a mapped field asks for confirmation, and changing sync settings preserves your manually written rules. Tag-based sync also correctly recognizes returning contacts from Kit tags and Customer.io segments. See how to map answers to contact fields and tags.

Get answers into Bento with less waiting

Bento field and tag updates now use its subscriber import queue to reduce delays, and syncing can recover when a subscriber was deleted and recreated in Bento. Automatic widget, answer, form, and offer tracking events are no longer sent to Bento by default, keeping that traffic from competing with contact updates. Your mapped answers still sync; see the Bento integration guide.

Send flow webhooks before leaving the page

A flow’s redirect now waits for pending webhook requests, within the existing timeout, instead of immediately navigating away and interrupting them. Webhook data and its preview also use readable question and answer names rather than including formatting markup. Failed requests that previously disappeared now show in delivery history; see the Webhook node reference.

Reuse campaign details after the landing page

Liquid can now use the most recently remembered query-parameter value when that parameter isn’t on the current page. That lets you carry a referral or ad-click value into a later flow step without requiring it on every URL—see capturing query parameters.

Let your AI assistant configure answer choices

Through MCP, your assistant can now set visibility conditions and scores when creating or updating a question’s answer options. Flow engagement responses are smaller, too, so inspecting recorded visits is less likely to overwhelm your assistant’s conversation. The question tools reference covers the new option settings.

Smaller improvements and fixes

• Klaviyo email clicks recognize contacts more reliably, including when RightMessage loads before Klaviyo’s script finishes.
• Form submissions can continue through the flow when an email-platform sync fails, rather than leaving visitors stuck on the form.
• Reconnecting an integration uses the current connection instead of an older saved connection.
• Routine integration credential refreshes no longer create a false prompt to publish changes.
• Flow split tests count offer conversions correctly instead of showing zero.
• Weekly report summaries use readable segment names instead of internal identifiers.
• UTM, referrer, and page-based rules include the visitor’s current page on their first page view.
• Embedded widgets no longer appear twice when a page builder has saved an old copy of their rendered content.
• Widget page-visibility switches correctly reveal their page fields, and clicking inside an expanded form field no longer collapses it.
• Rules that reference a disconnected email platform now show an explanation instead of appearing blank.