Page cover

1.101.00 (24.06.2025)

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

Client Portal updates

Apostrophe Search Bug Fixed in Campaign Inbox #CX

What was the issue? When using the Campaign Inbox search bar to filter messages by the full “From” field, typing an apostrophe (') in the search caused an error to appear instead of showing relevant results.


What’s fixed?

The search bar now correctly handles apostrophes when searching by the "From" field. You can freely search for names, companies, or email addresses that contain apostrophes without triggering errors.


Benefits to You:

✔️ Improved search functionality in the Campaign Inbox ✔️ No more errors when searching with special characters like apostrophes ✔️ Faster and more reliable message filtering

Positive Response Not Displayed in Campaign Inbox #CX

What was the issue? The CS team reported that a Positive Response for the campaign “Best SAP” was not showing in the Campaign Inbox as expected.

Upon investigation, we found that the response was recorded with an incorrect Response Type = 0, which prevented it from being displayed properly. Response Type 0 is invalid for classifying responses, leading to missing data in the Portal.


What’s fixed?

✅ The underlying issue causing incorrect Response Types to be assigned has been resolved. ✅ Positive responses are now correctly classified and displayed in the Campaign Inbox. ✅ We’ve also added additional checks to prevent invalid response types from being saved in the future.

Right to Erase (RTE) Timeout Issue Resolved #CX

What was the issue? We identified a problem with the Right to Erase (RTE) process in the Client Portal, where attempts to remove a prospect's data resulted in a timeout error. As a result, the system did not successfully anonymize the prospect, and their details remained visible.

This issue was reported in the Sopro UK 2025 James Mills campaign but may have affected other campaigns under similar conditions.


Example of the issue:

  • Campaign: Sopro UK 2025 James Mills

  • Prospect email: [email protected]

  • Attempting RTE resulted in a timeout, no anonymization occurred.


Expected behaviour:

  • Submit a data removal request under Compliance → Right to Erase (RTE).

  • The system hashes all personal data, replaces the prospect’s details with "[Compliance Removal]", and confirms success with a green message.

  • Searching for the prospect after removal shows no identifiable information.


What’s fixed?

✅ The system now processes RTE requests as expected without timing out. ✅ All prospect data is properly anonymized during the removal process. ✅ Confirmation messages appear, and removed prospects display as "[Compliance Removal]" across the Portal.


Benefits to You:

✔️ Fully functioning Right to Erase (RTE) process. ✔️ Improved compliance with data privacy regulations. ✔️ Reliable removal of prospect data with visible confirmation.

Broken Redirect for Company URLs in Prospect Details #CX

What was the issue? On the Prospect Details page, we discovered that for some prospects, the Company URL was incorrectly formatted — it included part of the Portal URL, causing the redirect to fail when clicking the link. Instead of opening the company website, the link was broken.


What we did:

  • We investigated the impact and confirmed that this issue affected multiple prospects across different clients.

  • The root cause was identified and resolved to prevent the Portal URL from being mistakenly included in Company URLs.


What’s fixed?

✅ Company URLs on the Prospect Details page now redirect correctly to the intended website. ✅ All previously affected records have been updated.


Benefits to You:

✔️ Reliable redirects to company websites from the Prospect Details page. ✔️ No more broken links caused by incorrect URL formatting. ✔️ Improved user experience when researching or viewing prospect information.

Product/Process updates affecting clients

Email Stage Sync with Zoho CRM #CX

What’s new? We’ve enhanced the Zoho CRM integration by adding support for syncing the Email Stage of prospects directly into your Zoho CRM. This allows your sales team to see exactly where each prospect is in the email outreach sequence and take action accordingly.


How it works

  • When setting up your Zoho CRM integration in the Sopro Portal, you can now map an “Email Stage” field to any suitable field in your Zoho CRM.

  • Once activated, Sopro will create or use a custom field in Zoho to store the Email Stage (e.g., M1, M2, etc.) for each prospect.

  • As prospects are sent from Sopro to Zoho (either all prospects or a custom selection), the Email Stage field will be populated with the correct initial stage.

  • For every email interaction — such as opens, clicks, or replies — Sopro will update the Email Stage in Zoho in real time, keeping your CRM data current.


What this means for you

✔️ Your sales team can see exactly which email stage each prospect is at inside Zoho CRM without switching platforms. ✔️ The Email Stage mapping is visible in the CRM integration details in the Sopro Portal, and supports backdated Zoho integrations.

Smarter CRM Integration to Avoid Overwriting Key Lead Statuses #CX

What’s new? We’ve improved how our system handles lead status updates for integrated CRMs like Zoho, ensuring your sales team's updates are respected and not accidentally overwritten by website activity or intent signals from Sopro.


Why this matters

Previously, if a client’s sales team manually updated a prospect’s status in the CRM (e.g., to “Positive Response”), Sopro could unintentionally overwrite that with a lower-priority status, such as a website visit or web goal, creating confusion or disrupting your sales process.

With this update, we’ve introduced smarter logic to compare new events with the current lead status in your CRM, ensuring only higher-priority updates are applied.


How it works now

✅ When importing or updating prospects through the CRM integration:

  • The system checks the current status of the prospect in your CRM, not just historical data from Sopro.

  • It compares the new event (e.g., website visit, lead event) with your mapped lead statuses and priorities, as defined in the Sopro Portal.

  • If the new event has a higher priority than the existing CRM status, the system updates the prospect.

  • If the new event has a lower priority, no update is made — preserving your team’s latest CRM updates.


Example Scenario

  • Prospect is imported with a "Delivered" status.

  • Your sales team changes their status in Zoho to "Positive Response".

  • The prospect later triggers a website visit.

  • Our system checks Zoho and sees "Positive Response" is a higher-priority status than a website visit.

  • Result: No update is made, and your CRM data remains intact.


Additional Safeguards

  • If a prospect doesn’t exist in your CRM, we create them with the new event.

  • If we’ve imported the prospect before, and the new event has a higher priority than previous ones, we update them.

  • If Update Contacts is set to "NO" in your CRM integration settings, no updates are made to existing prospects.


Benefits for You

✔️ Prevents accidental overwriting of important CRM statuses. ✔️ Ensures your sales team’s updates always take priority. ✔️ Provides a more reliable, seamless CRM integration experience.


This enhancement is live for all CRM integrations under SodaStream → CRM Integrations, ensuring smoother collaboration between your sales team and the Sopro platform.

Fix for Website Plugin Verification Accuracy #CX

Issue: Previously, when verifying website plugins in the Client Portal, the system incorrectly verified plugins even if the installed plugin had the wrong ID or only a partial (short) script was used. This caused false confirmation of successful installation, but visits were not tracked correctly.


Who was affected?

All users who installed the plugin with an incorrect ID or only the shortened version of the script.


What happened?

  • The verification process would show a successful result despite the plugin ID being wrong or incomplete.

  • This led to visits not being tracked, although the system indicated the plugin was properly installed.


What’s fixed?

The verification process now correctly detects when the plugin ID is incorrect or when the full script isn’t installed. The plugin verification will only succeed when the correct plugin is properly installed and tracking visits.


Benefits:

✔️ Reliable verification of your website plugin installation ✔️ Eliminates confusion caused by false success messages ✔️ Ensures accurate visit tracking from your verified plugin

Internal process updates

Ensuring Up-to-Date Subject Lines for Generative Email Templates #Ops

What’s new? We’ve improved how subject lines are handled in generative email templates to make sure your prospects always receive emails with the most current fallback subject line.


What was the issue?

When new prospects are added, the system generates messages using the current fallback template’s subject line and saves it for each prospect.

If the fallback subject line was later edited, the changes were not reflected for prospects who already had messages generated, meaning some prospects could get emails with an old or incorrect subject line.


What’s fixed?

  • Now, when sending emails, the system always uses the latest subject line from the fallback template.

  • This happens either by dynamically referencing the current template status at send time, or by updating the saved subject lines in prospect records whenever the fallback subject line is edited.


Why this matters

✔️ Avoid sending outdated or incorrect email subject lines. ✔️ Ensure consistent, professional communication with your prospects. ✔️ Reduce confusion and improve engagement by always using the current, approved subject line.

Enhanced Match Rate Tracking by Channel #CS #Ops

What’s new? We’ve upgraded the “Add Match Rate” functionality under SodaStream → Ops & Delivery → Campaign Audiences to provide more detailed, channel-specific tracking for AdSync audiences.


What’s Changed?

Previously, users could add a single match rate for an audience to support AdSync reporting. Now, we’ve expanded this to give you greater control and visibility, with the following new features:

Match Rate Per Channel You can now add individual match rates for each AdSync channel: Google, Meta, and LinkedIn, making your reporting more precise and insightful.

Automatic Date Population When adding match rates, the system will automatically display the date of the last audience refresh. This field is non-editable, so you always have a reliable reference for when the match rates were applied.

Improved Audience Tracking in the Database

  • We now save the number of matched prospects per channel, calculated using the audience size and the provided match rate.

  • The system also tracks which AdSync channels are active for each campaign (active = more than 1 matched prospect).

  • Once Intent-based AdSync audiences are available, the system will automatically record whether a campaign has a TAM audience, an Intent audience, or both — clearly reflected in the reporting as 1 or 2 active audiences.


Updated User Flow

Here’s how the process works:

  1. Audience Created – You create the audience.

  2. Audience Exported – Audience is exported.

  3. Audience Uploaded – Uploaded into the AdSync platform.

  4. Audience Pushed – Once pushed live, you can add match rates by channel.

When clicking the Add Match Rate button:

  • A pop-up window appears with fields for Google, Meta, LinkedIn match rates.

  • The date of the last audience refresh is shown, non-editable.

  • Enter the match rates by channel — the system handles the calculations behind the scenes.


Why This Matters

✔️ More accurate channel-level reporting for AdSync ✔️ Improved visibility of campaign performance across platforms ✔️ Easier handover and tracking with automatically populated audience data ✔️ Prepared for future enhancements, including Intent-based AdSync audiences


This enhancement ensures your campaign data is consistent, granular, and ready for the latest AdSync reporting standards.

Boolean String Visibility for Market Mapping #CS #Ops

What’s new? To improve the handover process between Sales and Client Success/Ops teams, we’ve added Boolean String visibility for each Market Mapping (MM).

Why this matters: When a new client signs on, the Sales team often provides search criteria used to build the target audience. Now, the original Boolean search string is clearly visible for each MM, ensuring Client Success and Ops can exactly re-create or review the search criteria. This minimizes miscommunication and speeds up campaign setup.

Where you’ll see this: The Boolean String is displayed directly in the Market Mapping view, using the same solution we already apply for visibility in the Campaign Audience section.

Benefit: ✔️ Smooth Sales to CS/Ops handover ✔️ Reduced risk of errors in audience targeting ✔️ Faster campaign kick-off with precise search replication

More Flexibility When Saving Schedules Without Active Audiences #Ops

What’s new? We’ve added a new option that allows you to save a schedule even when no audiences are active, giving you more flexibility when planning campaigns or adjusting setups in advance.


How it works

✔️ If all audiences are turned off:

  • The Save button is disabled by default.

  • You can enable the Save button by turning on the new checkbox, allowing you to save the schedule without active audiences.

✔️ If at least one audience is active:

  • The Save button is always enabled, as before.


Why this matters

This improvement allows you to: ✅ Prepare or adjust schedules in advance, even if audiences aren't ready yet. ✅ Avoid losing configuration changes when audiences are temporarily turned off. ✅ Maintain better control over your campaign setup process.


Note: When no audiences are active and the new checkbox remains off, saving is disabled to prevent unintentional schedule setups without audiences.

Fixes for Audience Cloning & Improved Label Clarity #CS #Ops

What was the issue?

We identified a few issues when cloning an audience in SodaStream → Ops & Delivery → Companies and Prospect Search:

  1. Funding filters were not being transferred to the new search when cloning an audience.

  2. The "Founding Date From/To" labels on the overview modal were incorrect — these fields referred to Funding Dates, not Founding Dates, causing confusion.

  3. The Type of Search field was not updating properly when cloning — for example, searches set as “Company Export” retained that type even when cloned as an Audience search.


What’s fixed?

Funding filters are now fully transferred when cloning an audience, ensuring all original filter criteria are preserved. ✅ The incorrect “Founding Date From/To” labels have been updated to “Funding Date From” and “Funding Date To” for clarity. ✅ The system now correctly updates the Type of Search field to “Audience” when cloning, avoiding incorrect search types in cloned audiences.


Benefits to You:

✔️ Accurate and complete cloning of audiences, including funding filters. ✔️ Clear, correct labels to avoid confusion between funding and founding dates. ✔️ Reliable search type updates when cloning, ensuring correct audience setup.

Industry Filter Bug Fix #CS #Ops

What was the issue? We identified and resolved two issues affecting the Industry filter on the Companies and Prospects Search page, specifically when selecting or adjusting sub-industries within broader industry categories like Retail.


Issue 1 – Sub-Industry Incorrectly Removed After Deselecting Some Sub-Industries

When selecting a parent industry (e.g., Retail) with all its sub-industries and then deselecting only some of them, the system was incorrectly removing the main Retail category from the filter display—even though it was still marked as selected in the filter modal.

What’s fixed: Now, only the sub-industries you deselect are removed from the filter. The parent industry and all remaining selected sub-industries stay visible, as expected.


Issue 2 – Sub-Industry Disappearing After Adding Additional Sub-Industries

Previously, if you selected several sub-industries under a parent category (e.g., Retail) and later added another sub-industry, the system would incorrectly remove the Retail sub-industry from the filter, even though it remained selected in the modal.

What’s fixed: All selected sub-industries will now remain visible in the filter after adding more sub-industries. No selected industries will disappear unexpectedly.


Where this applies:

✔️ Companies Search ✔️ Prospects Search


Benefit: ✔️ Industry filters now behave consistently ✔️ No loss of selected industries during adjustments ✔️ More reliable, frustration-free audience filtering

Messaging Setup Now Displays Correctly Across Campaigns #Ops

What was the issue? When copying a Messaging Setup from one campaign to another within the same client account, the system did not immediately display the messaging from the default campaign.

To see the messaging, users had to manually select a different campaign in the dropdown and then re-select the original campaign — an unnecessary extra step.


What’s fixed?

The system now properly displays the messaging from the selected campaign immediately, without requiring you to switch between campaigns in the dropdown.


What to Expect Now

✅ When configuring messaging for a campaign and selecting another campaign to copy messaging from, the messaging is displayed instantly.

✅ No need to toggle between campaigns — messaging visibility works as expected right away.


Benefit to You

✔️ Faster, smoother messaging setup across campaigns. ✔️ Fewer steps and less confusion when sharing messaging within your account. ✔️ More reliable experience when managing multiple campaigns.

Batch Requests for Multiple Email Profiles #Ops

What was the issue? When an audience was connected to multiple email profiles, batch requests (used to process prospect transfers) were only being sent for one email profile, instead of all profiles linked to the audience. This meant some email profiles didn’t receive the expected batch of prospects for sending.


When this occurred:

✔️ You had multiple email profiles connected to the same audience. ✔️ The M1 and Batch fields were enabled for those profiles. ✔️ Active send schedules were set for all profiles.

Despite this, batch requests were only processed for one of the profiles.


What’s fixed?

The system now correctly sends batch requests for all connected email profiles, ensuring prospects are transferred to each profile as expected.


Benefits to You:

✔️ Reliable batch processing for all email profiles linked to an audience. ✔️ No missing prospects across multiple email profiles. ✔️ Smoother campaign execution with consistent prospect distribution.


This update ensures all your email profiles receive their assigned prospects when using batch processing, preventing gaps in your outreach.

Audience Cloning Now Working as Expected #CS #Ops

What was the issue? When attempting to clone an audience in SodaStream, clicking the Clone button had no effect. The same modal remained on the screen, and the new search based on the audience parameters was not created.


Steps That Previously Caused the Issue:

  1. Find an existing audience and click the eye icon to view it.

  2. Click the Clone button.

  3. Actual result: Nothing happens, the same modal stays open.

  4. Expected result: A new search, pre-filled with the parameters from the cloned audience, should be displayed.


What’s fixed?

✅ The Clone button now works as expected. ✅ After clicking Clone, a new search is generated, using the same parameters from the original audience. ✅ You can now efficiently duplicate audiences for faster campaign setup.


Benefits to You:

✔️ Saves time when creating similar audiences. ✔️ Smooth and reliable cloning functionality. ✔️ Avoids unnecessary manual re-entry of search criteria.

Last updated