Changelog

v0.80.1 — 2026-10-29

⚡ Improvements

• Tags now call RPC 1.7.0 to receive theme colours and style settings under clearer names: answer colours, highlight colour, button colours, focus ring colour, and button radius, border and shadow. Existing looks are unchanged.

v0.80.0 — 2026-10-29

🚀 New features

• Secondary actions (Skip, Previous and Close) now have their own theme colours for fill, text and border, so you can style them independently from the main button. By default they look the same as before.
• Conversations have separate colours for the user's replies, so replies and the bot's bubbles can be themed independently.
• Text fields have editable colours for background, text, border, placeholder and icons.
• Answers have their own shadow colour, so they keep a visible edge even when the card shadow is turned off.
• Headers have their own colour settings, separate from the answer colours.
• The conditional step bubble in conversations now follows a theme colour for its warning border.

🐛 Bug fixes

• Keyboard focus rings now use the button focus colour everywhere, and links, text fields, field icons, the video play button and the Likert radio show a single ring instead of two.
• The multiple-choice check mark now appears on the selected answer in cards and conversations.
• Single-choice answers, NPS scores and stars are outlined on hover and focus, like multiple-choice answers.
• The launcher label now follows its font settings, and keeps its previous 20px default size.
• The "Other" field no longer turns red when focused, and it shows the theme editor's focus preview.
• A missing border radius setting now falls back to Screeb's default instead of drawing square corners.
• The range slider track is visible again on older WebViews, and the slider handle and legends now use consistent colours across cards, conversations and emails.
• The fallback image shown when the animated Screeby fails to load now uses the right ink for light and dark backgrounds.
• Checklist ticks in message text now use the text colour instead of drawing black.
• Link buttons in messages are styled as call-to-action buttons, with a focus ring that follows their corner radius.
• Upload progress, loading spinners, scroll indicators and message footers now follow theme colours instead of fixed ones.
• The max-selections hint is drawn as part of the conversation.
• Conversations no longer pick a selection colour that blends into the answers, including on free plans.
• Email cards use the same theme colours as the widget for headers, answers and fields.

⚡ Improvements

• Unselected checkboxes, radios and Likert rings, and text field borders, are darker so they meet the 3:1 contrast guideline.
• Text fields in cards and conversations have consistent rounded corners.
• Rating buttons, text fields and small link buttons follow the configured corner radius.
• Likert radios and NPS or star answers use the selection colour for hover, selection and focus.

v0.79.0 — 2026-10-29

🐛 Bug fixes

• Likert questions can now be completed even when the survey scenario still references statements that have since been removed. The Next button now appears once every displayed statement is answered, in both card and conversational formats.

v0.78.0 — 2026-10-23

⚡ Improvements

• Theme editor preview: the widget can now be previewed inside the Screeb theme editor, with forced visual states (hover, selected, focus, error) and a click-to-locate inspect mode that identifies which theme settings style each element (#3416).
• Theme tokens: added brand-level tokens and editor metadata for the theme editor. Corner-radius settings for avatars now offer three presets instead of a free range (#3410, #3411).

🐛 Bug fixes

• The tag no longer logs an error when targeting is intentionally off (for example with the disable-targeting init option, in preview mode, in hosted pages, or in the external editor). It now logs a quiet debug message instead (#3423).

v0.77.0 — 2026-10-22

⚡ Improvements

• The tag now talks to the Screeb backend using RPC version 1.4.0. For workspaces with the corresponding feature enabled, in-app messages are drawn from the workspace theme (#3391).

v0.76.1 — 2026-10-22

🐛 Bug fixes

• Fixed the emoji picker in the survey editor appearing behind the dialog it was opened from. It now reliably stacks above the dialog each time it opens, including when the dialog is shown again while the picker is opening (#3402).

v0.76.0 — 2026-10-22

🚀 New features

• Closing rules can now apply to the whole response, not just before the visitor starts answering. When a distribution sets the closing rules lifecycle to "whole response", its closing rules also cover started responses, so a No Follow or Custom survey no longer follows a visitor around once they have begun answering (#3368).
  • With the Close action, a started response ends like a displayed one.
  • With the Hide action, the widget is removed but the response stays started, and it resumes at the same step when targeting matches again.
  • The default, "before start", keeps today's behavior.
• The widget and the survey builder can now draw their appearance from a theme document sent by the API, falling back to the existing settings when none is sent (#3385).
  • Uploaded theme fonts are loaded by URL.
  • Page-level JS customizations keep taking precedence, so existing customizations keep working.
  • Make sure your Content Security Policy's font-src allows the static assets origin used for uploaded fonts.

🐛 Bug fixes

• A hidden response is no longer re-shown about a second later while its Custom closing rules still match.
• A malformed theme document now falls back to the settings instead of throwing.
• Malformed uploaded fonts are skipped, and a font that failed to load is retried.

⚡ Improvements

• The inspector and debug output now show the closing rules lifecycle of each distribution.
• Capping no longer blocks a started response that closing rules hid mid-answer from resuming.

v0.75.0 — 2026-10-21

🚀 New features

• Theme documents are now resolved layer by layer (base, group, then format), so a widget can read its look from a stored theme as well as from workspace settings (#3383, #3384).

🐛 Bug fixes

• onSurveyShowed now fires once per response. Feedback button surveys previously triggered it twice, and again whenever the button remounted (#3374).
• A broken theme token (an unknown reference, a type mismatch or a loop) no longer breaks the whole theme. Only that token falls back to the layer below or to Screeb's default, and each issue is reported once.
• A theme layer that is null is now skipped instead of causing an error.

⚡ Improvements

• The survey editor's step sidebar, "Add a block" and "Add a step" dialogs, sticker picker and variable pickers now use the shared UI components, for a more consistent look and better keyboard and screen reader behavior (#3359).
• Pickers opened during a dialog's opening animation now stay anchored to their trigger.
• The editor's image and video upload buttons are now named in every state (idle, uploading, error, replacing), and their accessible name includes the words they show.
• The inspector's long lists no longer flood screen reader landmarks, since rows only become regions on request.
• Style picker pieces (option tiles and picker triggers) can now show a preview of the style, and long tile labels are clamped to two lines with the full text on hover.

v0.74.1 — 2026-10-20

🐛 Bug fixes

• Leave-intent detection on touch devices no longer fires on scrolls that the page animates on its own (for example smooth scrolling or scripted scroll animations). It now only triggers on a real finger gesture, including the inertia scroll that continues right after the finger lifts (#3375).

⚡ Improvements

• The in-page inspector now uses the shared UI components, giving its tabs, rows, forms, empty and error states, and copy buttons a more consistent look and better keyboard focus behavior. Copy buttons appear on hover or focus.
• The survey editor's dialogs and step sidebar now use the shared UI components, giving them consistent titles, button layout, form fields, and panel sizing (#3358).

v0.74.0 — 2026-10-20

⚡ Improvements

• Mobile apps with session replay enabled now start the native view mirror only when something actually needs it: a recording starts, the editor or a preview is open, a targeting rule looks for an element, or an anchored message (popover, beacon) is displayed. This avoids walking the app's view tree after every change, scrolling included, for users who would never be recorded.

v0.73.0 — 2026-10-14

⚡ Improvements

• Surveys and messages appear faster: about 35% faster on a first visit and 40% faster for returning visitors in our measurements.
• The next question shows up sooner after an answer. Responses are now sent as plain HTTP requests, batched and without a CORS preflight, instead of over a WebSocket connection.
• Initialization no longer waits on session recording or identity capture.
• Tabs opened at the same time now share a single response, through a cross-tab lock instead of a random delay.
• The tag no longer opens a WebSocket connection, so a Content Security Policy no longer needs a wss entry for Screeb.

🐛 Bug fixes

• The tag keeps working on pages that add enumerable properties to Object.prototype.
• Commands are no longer corrupted on pages that define Array.prototype.toJSON, such as pages using Prototype.js (Magento 1).
• The tag keeps booting when sessionStorage is full or blocked.
• After a survey or message is disabled, an open page no longer keeps requesting it every second until its configuration refreshes.

v0.72.0 — 2026-10-14

🚀 New features

• Session replay has a new inputs-only privacy mode. It masks every form input while leaving page text visible, apart from any text you've chosen to mask with your own selectors. The tag now reads a three-level privacy setting (none, inputs, all) from the channel configuration.

v0.71.0 — 2026-10-13

🚀 New features

• Pass and fail states in the inspector are now announced by name, not only shown by color. (#3295)

🐛 Bug fixes

• Cancelling an image or video upload in the editor now really cancels it. Nothing is committed afterwards, and the original file is restored without an error message.
• Closing a popover or moving to another question mid-upload now aborts the upload instead of letting it finish in the background.
• An unreadable image no longer leaves the upload tile stuck on "uploading". It now shows an error.
• Hosted survey links now open correctly when a response was left running in another interaction. The old response is closed and a new one starts instead of failing.
• A searchable select no longer shows its keyboard focus ring after a mouse click, and its highlighted row only shows the ring when you navigate by keyboard.
• Fixed keyboard navigation in tab rows: the row keeps its Tab stop when the selected tab is disabled, and each tab points only at its own panel.
• Fields in the editor and inspector now have proper accessible names and labels that point at the right control. The "Simulate as a user" field in the inspector is now named too.

⚡ Improvements

• Colors in the editor and inspector now meet WCAG AA contrast in light and dark mode: warning text, solid danger buttons, field borders, muted text on tinted surfaces and the upload progress overlay. A new automated contrast check guards this.
• All story components in the editor and inspector now pass automated accessibility checks (axe). Lists, step cards, the sticker picker and validation messages were fixed along the way.
• Form fields share one API and one keyboard focus ring, including the color picker, which previously showed no focus.
• The editor's Segmented control now behaves like a native radio group: Tab reaches the selected option and the arrow keys move the selection.

⚠️ Breaking changes

• Legacy survey distributions are removed. Hosted survey links now serve only the link and email interactions.

v0.70.1 — 2026-10-12

🐛 Bug fixes

• Fixed the screenshot editor's top bar showing an extra empty band above it on phones with a notch or status bar. The survey already sits below the notch, so the editor no longer adds the inset a second time. Side and bottom spacing is unchanged. (#3291)
• Fixed surveys on Android appearing under the status bar, together with the next Android SDK release. The widget now respects the system bars and display cutouts, so the editor's toolbar also clears the gesture bar. (#3291)

⚡ Improvements

• The Android SDK now shares the device's system-bar insets with the tag and the widget re-lays out when they change. iOS is unaffected. (#3291)

v0.70.0 — 2026-10-12

🐛 Bug fixes

• Fixed the screenshot editor for long captures, such as scrolling phone screenshots: they used to be shrunk into an unusable strip, and the editor now opens on a fitted overview you can zoom into and annotate.
• Fixed the screenshot editor's top bar being covered by a phone's status bar. The editor now respects the device's top and side safe-area insets.
• Fixed the keyboard focus ring disappearing in the widget.
• Fixed rating buttons' focus ring using the primary text color, which is white on many themes. It now uses the call-to-action color, like neighboring choice buttons.

⚡ Improvements

• Screenshot editor zoom: pinch to zoom and pan, scroll to pan, and use ctrl/cmd+scroll to zoom. One finger still draws. A new zoom control in the canvas corner offers zoom in, zoom out and fit to screen, translated in all supported languages. Stroke widths are unchanged if you never zoom, and resizing no longer shifts annotations you already drew.
• Under the hood, the widget's look (cards, conversational surveys, in-app messages, shared components and the feedback button) now comes from a single resolved theme, with the same default appearance as before.

v0.69.0 — 2026-10-12

🐛 Bug fixes

• Fixed email survey links and previews: surveys starting with an NES, Likert, or AI follow-up question now render correctly in the email channel; links with &, #, or spaces in their parameters no longer break; clicking a choice in a multi-select email question now preselects it on the hosted page (instead of being ignored), so respondents can add more choices before continuing; email previews now open correctly on custom hosted-page domains; and merge tags from ActiveCampaign, Mailjet, and other emailing tools are preserved instead of being corrupted when building survey links.
• Fixed survey and message widget accent colors (selected choices, buttons, focus rings, typing indicator) becoming invisible on workspaces whose brand color is white.
• Fixed broken images collapsing to a thin strip instead of keeping their intended size.
• Fixed tap/click areas on pinned messages (beacons, embedded modals, sidebars, floating banners), which were sometimes too small or blocked legitimate taps.
• Fixed screenshot annotations (drawing and cropping) landing away from the cursor when the screenshot zoom level wasn't 100%.
• Fixed the inspector's custom property type picker, which was stuck on "string" and couldn't create properties of other types.

v0.68.0 — 2026-10-02

⚠️ Breaking changes

• Removed the "Close response on page/screen change" targeting option, which conflicted with the No Follow + Hide closing rule. Surveys that relied on it were automatically migrated to the equivalent No Follow + Close closing rule, so no action is needed.

v0.67.1 — 2026-10-01

No user-visible changes in this release.

v0.67.0 — 2026-10-01

🚀 New features

• Targeting rules can now be organized into sub-groups, and every group (plus the top-level rule set) can have its own AND/OR operator — matching exactly what you build in the rule editor.
• Added a "matches pattern" operator (using * as a wildcard) for text-based targeting rules, wherever contains is offered.
• Added a rule to target identified vs. anonymous visitors, based on whether the visitor has a user ID, name, or email — not just how many aliases they carry.
• The targeting debug console output and the widget inspector now show the full rule tree (groups and sub-groups, with their operators) instead of a flat rule list, making it much clearer why a survey is or isn't eligible.

🐛 Bug fixes

• Fixed several edge cases where AND/OR groups, sub-groups, and hidden or organization-level rules could be evaluated inconsistently, so complex targeting now always behaves as configured.
• contains no longer treats spaces in the value as a wildcard — it now matches the literal substring you typed.

v0.66.1 — 2026-09-28

🐛 Bug fixes

• Fixed a bug where a targeting rule saved without any screen selected would break targeting for every survey on the page in mobile in-app webviews. Malformed rules now simply fail to match instead of blocking all other surveys.

v0.66.0 — 2026-09-28

🚀 New features

• Multiple-choice questions can now have an optional maximum number of selections. Once the limit is reached, remaining options are disabled and a "Select up to N" hint is shown, available in both card and conversational formats and translated into all supported languages.

v0.65.0 — 2026-09-28

🚀 New features

• Open-text, email, and phone questions can now have a custom placeholder, set per question and per language, instead of always showing the generic default.

⚡ Improvements

• Session recording generates less work on the page while capturing events, improving performance on pages with heavy DOM activity.

v0.64.0 — 2026-09-28

🐛 Bug fixes

• Clicks that trigger a navigation in single-page apps are now recorded on the page where the click happened, instead of being misattributed to the page the user lands on.
• Session replay: shadow roots attached after recording starts and nested CSS rules inside the tag's own frame are now captured, and the touch cursor is visible again in replays of touch sessions.

⚡ Improvements

• Session recording is faster and each recording batch is now compressed before upload, roughly halving the data sent per session.
• Heatmap element identification is more accurate: elements are named after stable developer identifiers (field names, class names, link targets) instead of visible text, so the same element no longer fragments across languages or wording changes; build-generated class names are no longer used as identifiers, and pages already tagged for other analytics tools are recognized automatically.

v0.63.3 — 2026-09-25

🐛 Bug fixes

• Markdown headings (# Title) now render properly in messages and survey previews instead of being silently stripped out (#2926).
• Fixed title and text blocks showing literal ** asterisks on screen when their content included a heading, list, or other block-level markdown (#2926).

v0.63.2 — 2026-09-25

🐛 Bug fixes

• Fixed screenshot answers on iOS sometimes capturing the system "Screen Sharing" sheet instead of the page — the capture now waits for that sheet to be dismissed before grabbing the frame (#2951).
• Fixed the hold-to-record microphone button getting permanently disabled after a single short tap; it's now only disabled when microphone access is actually denied. Also fixed a long press on iOS/WebKit sometimes triggering the native text-selection menu, which could leave a recording stuck running (#2950).

v0.63.1 — 2026-09-24

🐛 Bug fixes

• Fixed the survey progress pill (e.g. "2/5") showing a blank progress bar on dark card headers, where it could blend into the background and become invisible.

v0.63.0 — 2026-09-24

🚀 New features

• Surveys can now show an optional progress indicator as a small pill (e.g. "2/5") next to the widget's close/minimize controls — in the header for card-based surveys, and alongside the chrome buttons for conversational ones. It only counts actual questions, so welcome messages, closing screens, and other text-only steps don't inflate the count. Enable it from the survey's progress bar setting.

🐛 Bug fixes

• The progress indicator now reliably appears in conversational surveys (it previously never showed up) and reports accurate values to screen readers.

⚡ Improvements

• Card survey headers are now vertically centered, fixing a slight visual offset that showed up when the progress pill was displayed.

v0.62.0 — 2026-09-24

🚀 New features

• New identity.anonymous_id command (and matching identity.anonymous_id init option) lets you tell Screeb the anonymous id your CDP already uses (e.g. an Amplitude device id, or a Segment/RudderStack anonymousId). Screeb binds it to the current respondent, or switches to the respondent your CDP webhook already created for it — the visitor stays anonymous and is never merged into an identified profile.

🐛 Bug fixes

• Passing the literal string "undefined" or "null" as an identity no longer silently resets the visitor to a brand-new anonymous respondent on every page load; it's now rejected with a clear error and the current respondent is kept.

v0.61.0 — 2026-09-23

🐛 Bug fixes

• Fixed a rare case where a survey or in-app message recovered from a previous browser tab could be replaced by a brand-new response instead of continuing the original one, sometimes showing a response to a visitor who no longer matched the targeting rules.
• Fixed star rating scales saved with certain emoji variants: they now correctly keep their hover fill and display order (previously showed as reversed on mobile).
• Fixed brand-colored score emoji (e.g. tinted stars) becoming invisible against the answer bubble background in conversational surveys and messages.

⚡ Improvements

• Sped up the time to first paint for surveys and in-app messages by removing unnecessary sequential network round trips during load.

v0.59.2 — 2026-09-22

🐛 Bug fixes

• Fixed surveys, messages, and session replay recordings sharing the same time-between capping rule to no longer always pick the same one when tied — the winner is now chosen fairly at random instead of favoring one deterministically, and stays consistent across checks until it's no longer tied.

v0.59.1 — 2026-09-21

🐛 Bug fixes

• Fixed "On Element Clicked" targeting rules never triggering when the target element was inside a shadow root.
• Fixed the screenshot/upload picker menu drifting away from its attach button when the widget was displayed at a size other than 100%.

v0.59.0 — 2026-09-17

🚀 New features

• Cards can now be positioned in the middle center of the screen, with all four corners rounded to match.
• The in-tag editor image picker now accepts SVG uploads. SVGs are shown inline (and tinted to match your color settings when they use currentColor), or masked to your color for artwork with baked-in fills.

🐛 Bug fixes

• Fixed the background overlay never appearing behind Card-format responses, even when the Overlay Visibility setting was set to show it.

v0.58.0 — 2026-09-16

🚀 New features

• Exit intent triggers now support a sensitivity setting (low, medium, high) so you can control how deliberate a visitor's exit gesture must be before an exit-intent survey or message fires. Low only reacts to a genuine cursor exit through the top of the page (or a strong mobile swipe); medium (the default) also catches fast upward moves near the top edge; high keeps the previous, most permissive behavior.

v0.57.1 — 2026-09-16

🐛 Bug fixes

• Fixed a rare case where two mutually-exclusive surveys or in-app messages could both display at once, or where a valid survey could be permanently blocked from showing when a competing one was denied by an integration's display hook (#2836).

v0.57.0 — 2026-09-16

🚀 New features

• The in-context editor now has a "Duplicate step" action, so you can repeat a step in a journey without rebuilding it from scratch (#2771).
• Added automatic translation to the in-context editor's settings — translate all step content from your default language into your workspace's other languages in one click, with an option to overwrite existing translations (#2774).

🐛 Bug fixes

• The in-context editor's "Navigate to step?" prompt no longer fires for steps that don't actually depend on the current page, and now offers a "Don't ask again for this session" option (#2772).
• Fixed the "Location example" URL field in the in-context editor losing focus and interrupting typing on every keystroke (#2819).
• Patched a denial-of-service vulnerability in the HTML sanitizer used when rendering message content (#2776).

v0.56.4 — 2026-09-14

🐛 Bug fixes

• Fixed an issue where a visitor temporarily refused for hitting the daily respondent quota could lose their identity on their next visit. The tag now keeps the respondent's stored ID after a daily refusal, so returning visitors keep their properties, aliases, and response history instead of starting over as a new respondent.

v0.56.3 — 2026-09-10

⚡ Improvements

• The targeting.debug command now flags when a currently-open survey's targeting rules are evaluating as not eligible, instead of always reporting it as "RUNNING" — making it easier to understand why a survey stays open on a page.

⚠️ Breaking changes

• Removed the identity.alias (identify.alias) command; the endpoint it relied on no longer exists. If your integration calls this command, remove it — it is now a no-op call that will fail.

v0.56.1 — 2026-09-08

No user-visible changes in this release.

v0.55.0 — 2026-09-05

🚀 New features

• Added support for Observe, a new behavioural capture mode (heatmaps, zoning, friction) that samples visitor traffic independently of Session Replay. Coverage is spread evenly across the month using a stable per-visitor sample, so the same visitor's full journey is always captured together. $screeb("debug") now reports Observe status, coverage rate, and whether the current visitor was sampled in.

🐛 Bug fixes

• Fixed explicitly stopping session recording (session-replay.stop) being silently undone about a minute later when a visitor's session rotated — capture no longer resumes after an explicit stop.
• Console output is no longer captured at all for visitors outside of a Session Replay recording, instead of being sent and discarded server-side, reducing the risk of sensitive data leaving the browser unnecessarily.

v0.54.1 — 2026-09-03

🐛 Bug fixes

• Survey "link" answer buttons opened inside a native app webview now wait for the answer to be recorded before leaving, and open reliably instead of silently failing to open a new tab (a known limitation of target="_blank" inside app webviews). Behavior outside of webviews is unchanged.
• Fixed dropdown menus in the in-context editor (action type, target, campaign selectors, targeting rule fields, checklist conditions, and various sidebar style pickers) opening behind sibling buttons and choices instead of on top of them.
• Fixed the action count badge on a choice showing "1 actions" instead of "1 action".
• Fixed the custom beacon visual upload tile not clearing after a successful upload, which made it hard to tell you could upload another image.

⚡ Improvements

• Resized the custom beacon visual upload tile in the picker to match the size of the built-in stickers.

v0.54.0 — 2026-09-03

🚀 New features

• Custom beacon visuals: upload your own image for in-app message beacons instead of picking from the built-in sticker set, with an optional tint and a shadow toggle to match your brand. Uploaded visuals can also be deleted from the picker library.
• The "Start survey/message" action now has a "Force restart" option, letting it close an already-open response for the targeted campaign and start a fresh one instead of leaving it untouched.

🐛 Bug fixes

• Fixed the scroll indicator on long multiple-choice lists overlapping the Next button in full-page survey mode.
• Fixed multiple-choice buttons losing their centered alignment in full-page survey mode.
• Fixed scrolled choice bubbles showing a hard-cropped edge under the sticky navigation bar in full-page survey mode.
• Fixed the scroll indicator never appearing in full-page survey mode even when there were more choices to scroll to.
• Fixed the question label scrolling out of view together with a long choices list in full-page survey mode; only the choices list scrolls now.
• Fixed the disabled Next button's validation hint appearing on simple hover and being hidden behind the arrow icon; it now shows reliably on click, positioned above the arrow.
• Fixed the disabled Next button growing in size whenever its validation hint appeared.
• Fixed "Start survey/message" actions with "Force restart" enabled silently failing to restart a survey that was already displayed.

v0.53.0 — 2026-09-01

🚀 New features

• IAM beacons can now have contextual actions (navigate, track event, set property, etc.), triggered when the visitor clicks the beacon's sticker — configurable from a new "Actions" section in the beacon step editor.
• The "Start a campaign" action is now "Start a survey/message": pick the campaign type explicitly and choose the target from a searchable list of your surveys/messages, instead of pasting a raw campaign ID.

🐛 Bug fixes

• Fixed a "Start a campaign" action failing to launch when it targeted an in-app message instead of a survey.
• Fixed campaigns picked before this update sometimes appearing unselected when reopening the action editor.

v0.52.3 — 2026-08-31

🐛 Bug fixes

• Fixed bold text (e.g. <strong>, markdown bold) rendering at regular weight in surveys when the visitor already had the font family installed locally.

v0.52.2 — 2026-08-31

🐛 Bug fixes

• Fixed the "Next" button not appearing for input questions even when the "Display a 'Next' button" option was enabled in the builder.
• Fixed the "Next" button becoming unreachable on link-distributed surveys when a long list of multiple-choice answers made the card content scroll — it now stays pinned in view.

v0.52.1 — 2026-08-31

🐛 Bug fixes

• Fixed a required input question sometimes letting a survey advance to the next step even though no valid answer had been entered; the click is now fully blocked until a valid value is provided.
• Fixed the "answer required" hint on the Next button disappearing later than it should, or reappearing incorrectly after an answer was submitted.

⚡ Improvements

• Multiple-choice answer lists on link-distributed surveys now grow to use the available page space instead of being capped at a fixed height with an internal scrollbar.

v0.52.0 — 2026-08-28

🚀 New features

• The tag can now run under a Content Security Policy with no 'unsafe-inline' at all (neither for scripts nor styles), with a new security-requirements guide documenting exactly what each CSP directive needs to allow.
• Added a no-inline-script install method: add data-channel-id to the loader <script> tag instead of calling init() from an inline script.

🐛 Bug fixes

• Fixed the editor's emoji picker firing hundreds of requests per second when it encountered an emoji with no matching image asset.
• Fixed recolored and keycap emoji rendering as blank under a strict CSP (their styling was being silently dropped).
• Fixed several edge cases in the new attribute-based install: the documented window.$screeb stub pattern now works correctly, the loader can no longer be confused by an injected page element sharing its id, and a page's own manual init() call could previously be silently duplicated/ignored.

⚡ Improvements

• Upgraded emoji artwork to Twemoji 17.0.3, fixing around 289 emoji that previously failed to render and adding every emoji introduced since Unicode 15 to the editor's picker.
• The editor's emoji picker now loads its emoji list from Screeb's own servers instead of a third-party CDN, so it works out of the box under a locked-down connect-src CSP.

v0.51.2 — 2026-08-27

🐛 Bug fixes

• Closed several ways the editor/inspector session could be hijacked or its credentials leaked: editor mode can no longer be forced onto a customer page by a crafted link (the token from a link is now validated the same way as a stored one, and a rejected token clears itself instead of re-arming on the next page load); cross-frame messages can no longer be spoofed to impersonate the admin app or another part of the tag; and the mobile SDK webview page no longer allows an arbitrary script origin to be loaded via its host parameter.
• Fixed a security issue where a crafted host page URL could break out of the tag's iframe boot script and execute arbitrary code in the customer's origin.
• Error and crash reports sent to Screeb's logging backend are now scrubbed of PII and sensitive data (page query strings/fragments, request bodies, headers, and response contents), matching the redaction already applied to on-device error logs.

v0.51.1 — 2026-08-26

🐛 Bug fixes

• Rating scale, scoring, and slider questions now describe the meaning of their scale endpoints (e.g. "1 = hard, 5 = easy") to screen readers, not just the numeric position — fixing announcements on every scoring surface, including the in-app editor preview.
• Fixed a security issue where a crafted link in a survey or message could execute arbitrary script when opened, including via middle-click, instead of navigating to the intended URL. This closes the sink for every clickable link across surveys, messages, and the in-app editor/inspector.
• Fixed a security issue where inspector commands reachable from the page's public tag API could be used to read another respondent's event history and identity properties using the admin's inspector credentials. These commands now only work when triggered from the inspector itself.
• Fixed a security issue where the admin's editor/inspector session token was exposed on the page's global scope and readable by any script on the host page when native browser storage was unavailable or restricted.

v0.51.0 — 2026-08-25

🚀 New features

• Session replay: choose which console levels are recorded — assert, error, and warn as before, with info now available as an opt-in — via checkboxes next to the existing "Enable console" toggle.
• Smoother popover repositioning inside mobile SDK webviews: surveys and messages that track a moving target (scrolling, resizing, in-app animations) now glide into place instead of visibly snapping between frames.

🐛 Bug fixes

• Fixed a security issue where, if the page hosting the tag was itself embedded in another site's frame, session recordings could be sent to that outer frame instead of Screeb. Pages that were legitimately embedded and were silently producing empty recordings now record correctly again.
• Fixed a security issue in the "set element attribute" contextual survey action that allowed arbitrary script execution on the customer's page (e.g. via onclick, onerror, or srcdoc values). Ordinary attributes and real URLs continue to work exactly as before.
• Hardened SVG rendering in surveys and messages against XSS: malicious markup hidden on child elements or placed after the visible SVG is now rejected instead of being rendered.
• Fixed a security issue where the calendar booking button's URL could be crafted to execute arbitrary script instead of loading a real booking page.
• Fixed the in-app editor and element inspector appearing unstyled on sites with a strict Content Security Policy — their styles now load as proper stylesheets instead of being blocked as inline styles.

v0.50.0 — 2026-08-24

🚀 New features

• New "inactivity" targeting rule: trigger a survey or in-app message after a configurable period (10s–3600s) with no visitor interaction on the page or screen. It's available as a trigger option in the wizard, alongside delay and exit intent.
• Exit intent is now detected across desktop web, mobile web, and native iOS/Android apps, instead of desktop web only. Detection adapts automatically to the device: mouse movement toward the browser edge on desktop, a scroll-flick gesture on mobile, and screen-leave signals in native apps.

v0.49.0 — 2026-08-24

🐛 Bug fixes

• Fixed a case where a host Content Security Policy blocking our stylesheet would silently stop all surveys, in-app messages, and feedback buttons from rendering, even though tracking and targeting kept working. The tag now falls back to alternate ways of applying its styles so widgets still render, and logs a clear error naming the fix (adding the tag origin to style-src) when a fallback is used.

v0.48.2 — 2026-08-21

🐛 Bug fixes

• Fixed a silent failure where a host Content Security Policy blocking the widget stylesheet would stop all surveys, in-app messages, and feedback buttons from rendering, while tracking and targeting kept working normally with no error surfaced anywhere. This is now reported as an error.
• The integration health inspector now checks the CSP directive that actually matters for widget rendering (style-src) instead of an outdated font directive the tag no longer needs, and reports it as the top-priority check since its failure blocks everything a respondent sees.

⚡ Improvements

• Removed the tag's last two uses of inline styles, so integrations can adopt a stricter Content Security Policy without style-src 'unsafe-inline' and still have widgets, fonts, and the editor's emoji picker render correctly.

v0.48.1 — 2026-08-20

🐛 Bug fixes

• Fixed session replay anonymization silently having no effect for sessions recorded from native iOS/Android apps, even when enabled in channel settings.
• Fixed native mobile session replay recordings sometimes opening on a blank screen for the first moment before any content appeared.

v0.48.0 — 2026-08-20

🐛 Bug fixes

• Fixed the tag hanging or failing to boot when the host page was itself embedded in another cross-origin frame, or when the core script was blocked by CSP, an ad blocker, or a CDN outage — these cases now fail fast with a reported error instead of leaving $screeb() calls stuck forever.
• Fixed a false "boot failed" error on slow connections — only bundles that actually fail to load or never start are now reported as failures.
• Fixed session recording crashing instead of gracefully skipping when the host page is cross-origin and unreadable.
• Fixed emoji images failing to render in session replay recordings due to a cross-origin canvas error.
• Fixed a bug where a single failing event handler (e.g. an undeliverable survey answer) could permanently stop all further events — tracking, targeting, widget lifecycle — from being processed.
• Fixed survey answers getting stuck instead of failing promptly when the realtime connection couldn't be established (now gives up after 30 seconds instead of retrying for up to 6 hours).
• Fixed the tag crashing instead of falling back to in-memory storage for identified visitors when browser storage access is blocked (e.g. strict privacy settings).
• Fixed surveys rendering unstyled or not at all on pages with a strict style-src CSP policy, and removed a duplicate stylesheet/script request that could occur in some cases.
• Fixed custom fonts failing to load in most browsers — together with the styling fix above, surveys no longer need 'unsafe-inline' in style-src or blob: in font-src.

⚡ Improvements

• When a targeting rule (scroll position, DOM element, etc.) can't be evaluated because the tag can't read the host page's content, a clear one-time console warning now explains why, instead of the survey just silently not appearing.

v0.47.2 — 2026-08-13

🐛 Bug fixes

• Fixed screenshot/photo attachments not being submitted on iOS: the file picker input could be garbage-collected while the native photo picker was still open, so the survey never received the picked (or cancelled) image. Photo attachments now work reliably on iOS.

v0.47.1 — 2026-08-13

Fix internal tests.

v0.45.1 — 2026-08-13

🚀 New features

• The debug inspector now shows a "Closing" section for each survey/message, revealing whether it uses Follow, No Follow, or Custom closing rules, whether it will Hide or Close, and live pass/fail status for each rule — making it much easier to understand and troubleshoot why a survey or message stays visible or disappears.

v0.45.0 — 2026-08-12

🚀 New features

• Added configurable closing rules for surveys and in-app messages: choose Follow Mode (default, keeps redisplaying), No Follow (stop once a targeting condition no longer matches), or Custom rules (close only once your chosen conditions are all met).
• Closing rules now support a Hide or Close action, controlling whether a closed survey/message can still reappear later in the session or is dismissed permanently everywhere.

🐛 Bug fixes

• Fixed in-app messages spamming the console with "already running" errors and failing to reappear after a page reload.

v0.44.2 — 2026-08-11

🐛 Bug fixes

• Fixed an unwanted focus ring flashing on a modal in-app message's close button when it appeared; focus now lands on the dialog itself, and keyboard navigation (Tab, Escape) works correctly from the first keystroke.
• Fixed the feedback button's rating scores getting hidden behind tall host page headers on hover instead of appearing on top; also corrected the vertical spacing around the rating buttons.

v0.44.1 — 2026-08-11

🐛 Bug fixes

• Security: closed an XSS vector where a crafted message could smuggle a javascript:/data: URL into a "navigate" call-to-action (in-page navigation and open-in-new-tab), which could otherwise execute attacker-controlled script in the visitor's browser. All navigation targets are now consistently sanitized before use.
• Security: fixed postMessage origin validation on the host page trusting a URL query parameter that could be set by anyone linking to the page, which could let an attacker spoof a trusted origin and trigger contextual actions on your site. The tag now only honors that parameter within its own sandboxed iframes, never on the top-level host page.

v0.44.0 — 2026-08-07

🚀 New features

• The in-app message builder is now platform-aware: it knows which formats, CTA actions, blocks, and design settings work on web, iOS, Android, Flutter, and React Native, and warns or disables the ones that won't work on your chosen targets before you publish.
• Structural message editing (adding/removing/reordering steps, and drag-to-reorder or inline insertion of blocks) now happens in the tag editor. Messages can also be edited live from inside a mobile app via QR code / deep link, with the web builder automatically syncing changes saved from the phone.

🐛 Bug fixes

• Fixed "navigate" CTA actions (including "open in new tab") doing nothing inside the iOS/Android app webviews; they now correctly hand off to the device's browser or app.
• Fixed copy-to-clipboard CTA actions silently failing outside Chrome, and properly disabled (with a clear warning) where the native app can't support clipboard access at all.
• Fixed CTA navigation being silently dropped on older Android WebViews due to an outdated URL-validation check.
• Fixed localized (per-language) CTA content occasionally failing to fire.
• Fixed full-height sidebar/modal messages being clipped by mobile browser chrome, notches, or home indicators, and made corner rounding/shadows render consistently between iOS and Android.
• Fixed floating messages (popovers, banners) rendering under the device notch or home indicator; a configurable extra offset is now available too.
• Fixed accidental deletion of message blocks on touch devices — a block's edit/delete controls now only appear after it's explicitly selected.
• Fixed banner corner rounding and safe-area padding being wrong at some sizes and placements.
• Fixed the editor's markdown toolbar squeezing its buttons on narrow panels; overflowing tools now collapse into a menu instead.
• Fixed the editor leaving a phantom gap in the widget after being closed.

⚡ Improvements

• The editor now flags unsupported CTA actions, targeting conditions, and design settings with "Web only" / "Mobile only" tags right in the picker, so you can see platform restrictions before configuring them, not just after.

v0.43.3 — 2026-08-07

No user-visible changes in this release.

v0.43.2 — 2026-08-07

🐛 Bug fixes

• Fixed a bug where a running survey or in-app message response (e.g. a persistent feedback button) could stay open even after the condition that triggered it was no longer true. Responses tied to an element appearing/disappearing on the page or to scroll position now correctly close when those conditions change back.

v0.43.1 — 2026-08-07

No user-visible changes in this release.

v0.43.0 — 2026-08-05

🐛 Bug fixes

• Fixed scroll-depth percentages on heatmaps that could show more than 100% on pages taller than about two screens; depth is now measured against the actual page height everywhere it's displayed.
• Fixed the "lowest scroll depth" page insight sometimes highlighting the wrong page by comparing scroll depths without accounting for differences in page length.
• Fixed scroll-depth tracking carrying over the previous page's height after an in-app (SPA) navigation, which could under-report scroll depth on the new page.

v0.42.3 — 2026-08-04

🐛 Bug fixes

• Fixed colored emojis (used in survey and message text) rendering incorrectly or losing their color tint in Safari.

v0.42.2 — 2026-07-30

🐛 Bug fixes

• Fixed surveys and in-app messages targeted by DOM element presence not being correctly re-evaluated on page/state changes, alongside existing URL and screen targeting rules.

v0.42.1 — 2026-07-30

🐛 Bug fixes

• Fixed end card text appearing shifted and clipped (with an unclickable Close button) when a survey's final "end" card briefly rendered while a leave animation was in progress.

v0.42.0 — 2026-07-30

🚀 New features

• The webview bridge used by native SDKs (iOS/Android/Flutter/React Native) now supports pinning the tag to a specific released version instead of always loading the latest build.

🐛 Bug fixes

• Fixed the media attach picker not reopening when picking the same source (e.g. "file") twice in a row, which could leave the attach button stuck unresponsive after the app returned from background.

v0.41.1 — 2026-07-30

🐛 Bug fixes

• Fixed the hidden webview widget container being exposed to screen readers, ensuring it's properly ignored by assistive technology until visible.

v0.41.0 — 2026-07-29

🐛 Bug fixes

• Fixed rating and Likert scale questions showing an unwanted horizontal scrollbar on desktop and tablet embeds (in-page, email, and link widgets). These now only scroll horizontally on real mobile devices; on desktop/tablet, compressed scales (e.g. NPS) wrap to fit instead.

v0.40.3 — 2026-07-28

🐛 Bug fixes

• Fixed an issue where a survey or in-app message that appeared on its own could steal keyboard focus and show an unwanted focus outline on page load. Focus is now only moved automatically for modal widgets, and closing a widget no longer resets focus unless it actually took it. (#2229)

v0.40.2 — 2026-07-27

🐛 Bug fixes

• Fixed a remaining case where the visual survey editor's dialog window didn't resize correctly when switching between fullscreen and minimized modes.

v0.40.1 — 2026-07-27

🐛 Bug fixes

• Fixed the "Insert variable" picker for survey contextual actions: it's now available on every applicable field (navigate URL, set value, copy to clipboard, custom event detail, set attribute value, track event properties, not just one), and no longer appears invisible, gets clipped, or closes itself before you can click it.
• Fixed number input fields in the survey editor rendering visibly larger than neighboring text fields.
• Fixed dialog and window sizing/centering issues in the visual survey editor when switching between fullscreen and minimized modes.

v0.40.0 — 2026-07-24

⚡ Improvements

• Modal and embedded in-app messages can now use a configurable stacking order (z-index), so they no longer always render above every other element on the page. Centered modals with an overlay always keep the maximum stacking order to guarantee they stay visible; modals and messages inserted in-flow via embed_selector can be positioned relative to surrounding page content instead.

v0.39.7 — 2026-07-23

⚡ Improvements

• Events sent in quick succession (e.g. session start, page view, identify, and track calls firing together) are now batched into a single network request instead of one per event, reducing network overhead. Buffered events are also flushed immediately when the page is hidden or unloaded, so nothing is lost during navigation.

v0.39.6 — 2026-07-23

🐛 Bug fixes

• Fixed the "add block" dialog in the visual editor getting pushed off-screen and clipped in narrower or offset embed containers — it now reliably centers within the actual visible viewport. (#2178)

v0.39.5 — 2026-07-23

What's Changed

• fix(builder): keep add-block popover inside viewport when step is left.

v0.39.4 — 2026-07-21

🐛 Bug fixes

• Fixed calendar embeds (e.g. Microsoft Bookings) on narrow mobile screens where part of the calendar was cut off and couldn't be reached by touch scrolling. The calendar now scrolls horizontally as needed so all days and time slots stay reachable on small devices. (#2160)

v0.39.3 — 2026-07-20

🐛 Bug fixes

• Fixed the "Set value of" contextual action so that {variable} placeholders typed into its value field are now properly resolved against the visitor's properties before being sent, matching how variables already worked in labels. A variable picker was also added to the value field so you can insert available variables directly instead of typing them by hand. (#2159)

v0.39.2 — 2026-07-17

🐛 Bug fixes

• Fixed surveys that end with an app store rating step preceded by a text step: the review prompt now reliably shows up, and the preceding thank-you/text message now renders correctly as the closing card instead of leaving the widget blank. (#2135)

v0.39.1 — 2026-07-17

🐛 Bug fixes

• Fixed a bug where embedding the Screeb tag in a cross-origin iframe could throw errors during session recording, in some browsers (e.g. Firefox). The tag now safely falls back instead of breaking. (#2122)

v0.38.1 — 2026-07-16

🐛 Bug fixes

• Fixed an issue where a survey consisting only of an App Store rating prompt would silently fail to trigger the rating dialog and related integration events for a first-time visitor. (#2115)

v0.38.0 — 2026-07-16

⚡ Improvements

• In the in-app message editor, picking an element with a CSS selector that matches zero or multiple elements on the page no longer blocks you with an error. Instead you get a warning explaining the issue, with the choice to edit the selector or continue anyway. (#2110)

v0.37.4 — 2026-07-15

🐛 Bug fixes

• Fixed compatibility detection so the tag never requires unsafe-eval in a page's Content Security Policy. Sites with strict CSP rules (which previously could be pushed onto the legacy bundle, or blocked entirely) now get the same modern/legacy routing as every other page. (#2108)

v0.37.3 — 2026-07-15

🐛 Bug fixes

• Fixed an issue where calling identify() on a visitor who already had an active anonymous session could create a duplicate respondent instead of attaching the identity to the existing one. Identifying a visitor now preserves their prior anonymous history and does not consume extra MTU. (#1811)

v0.37.2 — 2026-07-15

🐛 Bug fixes

• Fixed an in-app message issue where confirming a step (via the CTA button or by clicking the highlighted host element) could sometimes skip the next step entirely, silently swallowing its actions like navigation. Steps now only advance from the interaction the visitor actually performed.
• Fixed a rare case where an answer could be lost if a survey CTA navigated to a new page immediately after answering, which could leave the conversation stuck on an already-completed step.
• Corrected the German translation for the skip button, which now reads "Überspringen" instead of the previous, less natural wording.

v0.37.1 — 2026-07-14

🚀 New features

• Added onRecordingStarted and onRecordingStopped lifecycle hooks, so integrations can react when session recording begins or ends. Works the same way as the existing onReady hook, providing channel and user info, and is available across all supported SDK wrappers (JS, browser, React, Angular, Vue, Svelte, Ionic).

🐛 Bug fixes

• Fixed a bug where the tag could leak internal helper variables onto the host page's global scope (window), which could silently break customer scripts that happened to declare a global with the same name — and vice versa. The tag no longer defines any global variables.

v0.37.0 — 2026-07-13

No user-visible changes in this release.

v0.36.2 — 2026-07-10

No user-visible changes in this release.

v0.36.1 — 2026-07-09

🐛 Bug fixes

• Fixed crashes on older browsers and pinned Android WebViews (Chromium versions below 97) that support JavaScript modules but not all the modern APIs the tag relies on. These engines are now automatically served the legacy, fully-compatible bundle instead of the modern one, restoring survey and in-app message delivery on affected devices.

v0.36.0 — 2026-07-09

🐛 Bug fixes

• Fixed the step sidebar allowing the single step of a Conversation Starter to be removed or duplicated, which left the builder unable to add a new step back. The Remove/Duplicate actions are now disabled for Conversation Starters, with an explanatory tooltip, while other survey types keep full step management.

v0.35.4 — 2026-07-08

🐛 Bug fixes

• Fixed surveys and in-app messages that could stay permanently invisible in mobile webview integrations when the host app sized the webview late (e.g. certain Android WebView races) — the tag now detects this and automatically repositions and redisplays widgets once the webview is properly sized (#2043).
• Fixed the tag getting permanently stuck with no widgets or targeting when a stale, expired, or malformed editor-mode session was left behind — it now recovers automatically on the next load (#2046).
• Fixed unrecoverable boot failures being silent: calls to $screeb() no longer hang forever if the tag fails to start — they now fail immediately with a clear error (#2046).

v0.35.3 — 2026-07-08

🐛 Bug fixes

• Fixed the French "previous question" button label, which read "Retour" (easily confused with closing the survey) and now reads "Précédent".
• Fixed persistent feedback-button widgets (surveys that stay visible unanswered until the visitor engages) that could remain permanently empty and never show a question after being displayed.

v0.35.2 — 2026-07-07

🐛 Bug fixes

• Fixed an issue on mobile apps (React Native/Expo, Flutter) where surveys could stop appearing entirely after an over-the-air update or hot restart, until the app was fully restarted. This fix is applied server-side and requires no SDK update.

v0.35.1 — 2026-07-07

🐛 Bug fixes

• Choice, score, Likert, and tips buttons no longer show a focus highlight on mouse clicks or when a step auto-focuses them — the highlight now only appears during keyboard navigation. (#2037)
• In the editor preview, the "take me there" navigation prompt no longer appears when running inside a mobile app's webview, so the preview stays put instead of breaking the native app's in-app browser. (#2036)

v0.35.0 — 2026-07-07

🚀 New features

• Rating (NPS/CSAT/CES/NES) and Likert questions can now disable the mobile horizontal scroll, matching the option already available on multiple-choice questions. Creators can force a wrapped/grid layout instead of a scrollable row. Existing surveys keep the current scrolling behavior unless changed. (#2021)

🐛 Bug fixes

• The record-audio icon in the response input now uses the same outline style as the send and attachment icons for a more consistent look. (#2022)
• Fixed the scoring legend floating over the middle of the row instead of staying anchored above the last button when scrolling on mobile in conversational surveys. (#2021)

⚡ Improvements

• Redesigned the compressed rating layout on cards: scores now render as a full-width grid of rounded buttons that wraps neatly on narrow screens, replacing the old segmented bar that could clip on desktop. Tap targets are larger and legends stay aligned with their buttons. (#2021)

v0.34.3 — 2026-07-06

🚀 New features

• New audience sampling targeting rule: show a survey or in-app message to only a chosen percentage of otherwise-eligible visitors, with a stable per-visitor result that persists across reloads. (#2004)

🐛 Bug fixes

• Fixed the in-app message preview in the visual editor getting stuck on top of a block editing dialog after picking a DOM element on the page. (#2028)

⚡ Improvements

• Surveys and messages triggered by CDP events (Amplitude, Segment, Rudderstack) now use adaptive, server-driven polling: the tag checks targeting more frequently while a match is imminent and automatically backs off otherwise, reducing unnecessary requests while keeping triggers responsive. (#2023)

v0.34.2 — 2026-07-03

🐛 Bug fixes

• Fixed a bug where a single-choice button configured to navigate within the same single-page app (in-page-spa) would incorrectly open a new browser tab instead of navigating in place, and would skip firing the onButtonNavigate* hooks. (#2013)

v0.34.1 — 2026-07-02

No user-visible changes in this release.

v0.34.0 — 2026-07-02

🚀 New features

• Message and tour buttons that navigate to a URL now support a new "single-page app" navigation mode: instead of reloading the page, the navigation updates the browser history in place so SPA hosts keep their app state. This mode is available both via spaNavigationHandler configuration and as a toggle in the editor's action target settings.
• Added onButtonNavigateStarted and onButtonNavigateCompleted hooks that fire when a message/tour button triggers a "Navigate to URL" action, letting integrators react to (and confirm completion of) these navigations, including for the new SPA and new-tab targets.

🐛 Bug fixes

• Fixed session replay on newer mobile webviews (WebView 5+) incorrectly forcing an internal container to display: block during recording, which is no longer needed and could affect replay rendering on those versions.

v0.33.8 — 2026-07-01

No user-visible changes in this release.

v0.33.7 — 2026-07-01

🐛 Bug fixes

• Fixed an issue where the Android in-app webview page (webview.html) was served through a redirect that stripped the .html extension, which could break the webview integration. It's now served directly without any redirect.

v0.33.6 — 2026-07-01

No user-visible changes in this release.

v0.33.5 — 2026-07-01

No user-visible changes in this release.

v0.33.4 — 2026-07-01

No user-visible changes in this release.

v0.33.3 — 2026-07-01

No user-visible changes in this release.

v0.33.2 — 2026-07-01

🐛 Bug fixes

• Fixed "Take me there" style navigation links so they reliably navigate the whole page instead of getting stuck inside the tag's embedded frame, even in apps with complex framework routing or sandboxed embeds.

v0.33.1 — 2026-07-01

🚀 New features

• The debug inspector's Messages and Surveys tabs now show the live state of started campaigns (status and display conditions) even when targeting is paused, such as in preview mode, instead of just showing an error.

🐛 Bug fixes

• Fixed an occasional "WS is closed" error when closing a message or survey.
• Closing a running campaign from the inspector no longer causes it to briefly reappear.
• The inspector no longer spams the browser console or opens extra background connections while polling message/survey state.

v0.33.0 — 2026-07-01

⚡ Improvements

• Faster page loads for the vast majority of visitors: the core, widget, and message bundles are meaningfully smaller thanks to a higher modern-browser baseline, code-splitting rarely-used targeting and debug logic out of the main bundle, dependency trimming, and tighter minification. Older browsers are unaffected and keep working exactly as before.
• Survey and message text now appears immediately in a fallback font and swaps in the custom webfont once loaded, instead of staying invisible while the font downloads.
• Image placeholders (blurhash) are now loaded on demand, so widgets without images ship a smaller bundle.
• Repeat visitors load cached tag assets faster thanks to longer-lived CDN caching of versioned files.
• Browser devtools no longer show 404 errors for source map files in production.

v0.32.3 — 2026-07-01

No user-visible changes in this release.

v0.32.1 — 2026-06-30

🐛 Bug fixes

• Absolute date targeting for event time rules now works correctly. Surveys and messages using "visitor event time" targeting with a fixed calendar date (before/after a specific date) were previously broken — the tag threw an error and aborted targeting evaluation entirely. This release adds proper support for absolute date operators, matching the behaviour already present on the backend.

v0.32.0 — 2026-06-30

🚀 New features

• Screeb Inspector: A new developer panel is now bundled with the tag, giving developers and product teams real-time visibility into the tag's state on any page. The panel includes tabs for page overview, health diagnostics, tracked events, visitor properties, and active surveys and messages. A Simulate tab lets you test targeting rules against custom visitor states, events, and properties — all without reloading the page or making a deployment. Sign in with your Screeb account to unlock the full panel. (#1827)

v0.31.17 — 2026-06-29

🐛 Bug fixes

• Fixed a broken favicon data URI in the in-app webview that could cause a failed resource load or missing icon in embedded web content (#1993).

v0.31.16 — 2026-06-29

No user-visible changes in this release.

v0.31.15 — 2026-06-29

🐛 Bug fixes

• In-app message builder: Fixed an issue in the multiple-choice CTA editor where opening a button-style dropdown (variant selector) could visually cover choices below it, including the "No actions" button. Dropdowns now correctly appear on top of all other elements while open. (#1987)

v0.31.14 — 2026-06-29

🐛 Bug fixes

• Fixed vertical alignment of content blocks inside banner widgets — items now center-align correctly instead of snapping to the text baseline.

v0.31.13 — 2026-06-29

🐛 Bug fixes

• Fixed an issue where the last step of a multi-step in-app message with a Stop & Close call-to-action was not recorded as completed — the step completion event now always fires before the widget closes. (#1967)
• Fixed a missing analytics event when a popover CTA combined Stop & Close with another action (e.g. scroll or navigate) — the simulated click on the pin target is now reliably triggered. (#1967)

v0.31.12 — 2026-06-25

🐛 Bug fixes

• Fixed an issue where clicking a multiple-choice CTA button configured with a "Stop & Close" action did not record the response, causing those answer choices to show 0% in survey statistics (#1964).

v0.31.11 — 2026-06-23

🐛 Bug fixes

• Delay rules now work correctly in message preview mode. When previewing a multi-step in-app message that includes a "delay between steps" condition, the required page-load timestamp was never seeded because the full targeting engine is disabled in preview. The tag now seeds that timestamp on preview init and keeps it fresh on SPA navigation, so delay-gated steps behave the same in preview as they do in production.

v0.31.10 — 2026-06-22

No user-visible changes in this release.