1.119.00 (17.03.2026)

A deployment of a new version of SodaStream and Client Portal inside the regular release window.

Client Portal updates

Update: Filtering by Source domain on Intent Tracker & 'Search' tabs improvement #Ops #CS #CX

What was the issue?

When the same web plugin ID was installed on multiple domains, the Intent Tracker did not show which website a visit came from.

Companies and prospects appeared without source context, making it hard to interpret engagement.

Additionally, the page was retrieving information too slow, which affected the 'Search' bars in each column, and users were experiencing slow loading times, and sometimes, results were not being displayed at all.

What was fixed?

• A Source dropdown filter was added to the Intent Tracker for clients who have the plug-in implemented on multiple domains/websites.

Users can now filter companies and prospects by domain, see multi‑domain visitors correctly, and keep the “All” view de‑duplicated.

*NOTE*

This Source dropdown field is only visible to clients who have installed the plug-in on more than one domain/website.

Clients who have only one website being tracked will not be viewing the Source dropdown field.

• 'Search' tabs for each column now work as expected.

We've improved the procedure of data retrieval, and users can now browse through each column with the desired filter.

Possible options should be displayed as expected, so that users can select their filter.

Update: Unqualified/Non-ICP companies are now displayed in 'Audience Segmentation: Demographic data' widget #Ops #CS #CX

What was the issue?

The Audience Segmentation: Demographic data widget only exposed Total, Engaged, and ICP segments, making it unclear how many companies were unqualified.

This limited TAM and ICP refinement conversations for CS and clients.

What was fixed?

A Non‑ICP (unqualified) segment was added to the widget, alongside clear breakdowns by industry, size, and country.

Users can now see qualified vs unqualified traffic and understand how Total is composed, without losing any existing metrics.

Where found: Portal/Dashboard ⇒ Intent tab ⇒ Widget: Audience segmentation: demographic data

Update: URL/Website validation implemented in 'Filter website traffic' page #Ops #CS #CX

What was the issue?

On WebTrackingSetup → “Filter website traffic”, the “Pages to include/exclude” fields accepted any text, including invalid strings.

This risked saving malformed URLs that could disrupt tracking logic.

What was fixed?

URL validation, similar to the Intent goals & alerts section, was implemented on the filter tab.

Users can no longer save random characters, and correctly formatted URLs work as expected, protecting the tracking workflow.

Update: Dashboard UI Consistency Improvements #Ops #CS #CX

What was changed?

As part of our ongoing efforts to improve the clarity, consistency, and professionalism of the dashboard user interface, we undertook a comprehensive review and update of dashboard widget headings and terminology.

This work addressed two main areas:

1. Standardisation of Widget Headings to Sentence Case

Previously, dashboard widgets and section headers used a mix of Title Case (e.g., “Email Performance”, “Lead Velocity”) and sentence case (e.g., “Audience reached”). This inconsistency created a fragmented visual experience and detracted from the overall polish of the product.

What we did:

• Audited all dashboard widgets and similar section headers for inconsistent casing.

• Updated every widget title and relevant header to use sentence case, ensuring a unified and modern look throughout the dashboard.

• Verified the changes with attached screenshots and manual QA to ensure no areas were missed.

• The update was tested and validated on the test environment and staging, with feedback confirming the new style is clear and visually consistent.

2. Renaming “Touchpoints” to “Activities/Activity”

The dashboard previously used the term “Touchpoints” in various UI elements, which was not aligned with the rest of the platform’s terminology. This could cause confusion for users, especially as “activities” is the standard term elsewhere in the product.

What we did:

• Identified all instances of “Touchpoints” in dashboard labels, widget titles, and related UI copy.

• Replaced “Touchpoints” with “Activities” or “Activity” as appropriate, matching the context and ensuring consistency with platform-wide terminology.

• Ensured that all changes were reflected in both the UI and any related documentation or help text.

• The update was tested and confirmed by QA and product stakeholders, with positive feedback that the new terminology is clearer and more intuitive.

---

Impact

• Improved User Experience: The dashboard now presents a cohesive and professional appearance, making it easier for users to scan and understand key metrics.

• Consistent Terminology: Aligning on “Activities”/“Activity” eliminates confusion and supports a unified product language.

• Quality Assurance: All changes were manually tested, reviewed, and validated by QA and product owners, ensuring a high-quality release.

Update: Response Type and Intent Type implemented for Zoho CRM Integrations #Ops #CS #CX

In addition to last week's deployment of this feature for the other three CRMs (HubSpot, Pipedrive, Salesforce), we're now deploying this update for Zoho CRM as well.

Zoho integrations remained lacking a dedicated Response Type field, leaving clients unable to see the specific response classification behind imported leads/contacts.

This reduced visibility into why records appeared and how they should be prioritised.

What has changed?

A Response Type field was added for Zoho Leads and Contacts, mirroring current Lead Status values.

Users can map it to text or dropdown fields, and it appears in the Portal integration details, improving downstream reporting and workflows.

Bug Fix: Prospect status not being updated on intent for 'All Prospects' integration #Ops #CS #CX

What was the issue?

For "All Prospects" integrations, later events like web visits or gift redemptions were not updating the prospect status in connected CRMs.

Records stayed at “email delivered”, hiding important intent signals.

What was fixed?

The CRM sync logic for email‑delivered imports was corrected so subsequent intent events trigger status updates across supported CRMs.

Prospects now move from “email delivered” to the correct mapped intent state as new activity occurs.

Sodastream updates

Automated LinkedIn Outreach Updates #Ops

1. Improved logic of successfully executed sends for Automated LinkedIn Outreach

What was happening?

For LinkedIn Outreach schedules, failed connection attempts (e.g. missing Connect button, send errors) caused the activity to stop early.

This affected daily send volumes as they were not reached as per the daily send limit, and Ops owners sometimes weren’t notified, creating delivery delays and last‑minute volume corrections.

What has changed?

The LIO sending logic was updated to work against a pool of up to 30 valid prospects per day while respecting the configured daily connection volume.

The system now aims to meet the daily target without exceeding 30 opened profiles and without stopping prematurely when a few attempts fail.

2. Swedish language profiles are now supported for LinkedIn Outreach

What was the issue?

The automated LIO process could not recognise the Swedish “Connect” button on LinkedIn profiles, as we did not have Swedish language support through the automated LinkedIn Outreach process.

This prevented connection requests from being sent when the client's LI profiles were set in Swedish language, blocking automation for those campaigns.

What has changed?

The LIO automation was extended with Swedish language support for LinkedIn UI elements.

The system now correctly detects and clicks the Swedish “Connect” button, enabling automated outreach in Swedish.

3. Event Priority groups are now updated as expected

What was the issue?

When new LIO messaging with multiple priority groups was created, only the first priority group appeared in the Prioritisation tab.

Despite priority groups showing as In Use, Sodastream only recognised a single group, shrinking the contact pool.

This required additional manual work from Ops as a workaround to activate all priority groups.

What was fixed?

The messaging save flow now correctly registers all created priority groups in the Prioritisation tab.

All In Use groups are respected during prioritisation, ensuring the intended data pool is available for LinkedIn engagement.

4. New Clients not being automatically added to the LI Response Auto-Classification model

What was the issue?

There was an issue affecting new clients, as they were not being automatically added to the Auto-classification model for LI Responses.

This affected incoming LI responses from being automatically categorised, and responses were left as uncategorised, while chaser emails kept going out.

What was fixed?

The issue has been resolved, and the fix has been implemented.

Newly created clients that are performing Automated LinkedIn Outreach will now be automatically added to the Auto-classification model as expected.

Update: CC'd email addresses in Responders will now be automatically added to exclusions #Ops

What was the issue?

CC’d email addresses were only added to exclusions when responses went to Manual Resolution.

For auto‑resolved responses (including referrals), CC’d contacts were not excluded, risking unwanted follow‑ups to referred or secondary recipients.

What was fixed?

The existing CC parsing and validation logic was extended to auto‑resolved responses with a standard exclusion duration.

CC’d addresses now enter exclusions consistently across response types, without changing manual resolution behaviour.