3.42.2 — Analytics Update
Pages
Some visits from links, bookmarks, or refreshes went uncounted because tracking sent the event before the Page could identify itself. Opening a Demo from a Page could also add an extra Page view, and clicks and scrolls inside the Demo could count toward the Page. Historical reports now recover visits where the URL and later activity identify the Page, and exclude Demo activity from Page totals. Recovering missed visits can raise view counts, while removing extra views from Demo opens can lower them. Click and scroll totals may also drop on Pages where Demo interactions were included. For about 30 days after release, comparisons with the previous period may reflect changes in tracking as well as changes in engagement. Estimated time on Page now stops at 30 minutes, and time spent across different sections of the same Page is added together. On mobile, tracking sends the duration when someone switches away. For dates before release, counts for clicks that took people off-site and time on Page may read slightly low. Bounce rate shows “Not available for this period” because earlier tracking could miss the timing needed to calculate it. The Embedded Demos card now uses the activity recorded for embedded Demos.Forms
Counting starts and submissions separately meant that a submission without a recorded start could push abandonment below zero. Reports now link starts and submissions within the same session. They also count unique visitors across the full date range you select. Average completion time could appear much longer than it was because the report treated milliseconds as seconds. It now displays the correct duration. The Form detail panel now shows the version most viewed in the selected date range, out of the latest version (for example, “v10 of 12”). The corresponding CSV column is now labeled “Latest Version.”Featurettes
Starting around 9/21/26, some large batches of analytics events failed to send. Retries caused some events to be recorded more than once, and a separate delivery issue on 11/2/26 added duplicates. These extra events inflated views and clicks and caused some views to count as drop-offs before Slide 1. Starting with this release, each new event counts once. Reports for the affected dates can still include duplicates, so views and clicks may look lower in post-release periods.Devices and activity dates
Device reports now identify Android and iPad in new activity. Previously, Android could appear as Linux and iPads as Unknown. The server also adjusts new timestamps when a device’s clock is off. Historical device labels and timestamps retain their original values. The “activity starting” banner now uses the date WaveCX first received activity.Report reliability
Some reports searched the full activity history and could fail when the amount of data exceeded a query limit. Reports now read only the dates you select. Tracking also preserves more events when someone leaves shortly after opening content.Affected clients should have received a full report of their updated data.
3.42.1 — Domain Removal Safeguard
Removing a domain from the External Content list now always asks you to confirm first. Before, you were only warned when content was using the domain, so an unused domain was removed straight away.Domain not in use
The dialog says nothing refers to the domain right now, and content added later won’t be able to load from it. Choose Remove or Cancel.Domain in use
The dialog lists the Pages, Featurettes, Demos, Forms, and branding that use the domain. Choose Remove Anyway or Cancel.Unticking a single content type on a domain, such as turning off Fonts but keeping Images, still asks only when something uses the domain.
