Page cover

1.96.00 (08.04.2025)

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

Client Portal updates

📊 New: Export Data from the Intent Tracker to Excel #CX

You can now export your Intent Tracker data directly to Excel — making it easier to analyze engagement trends, identify high-intent companies, and refine your targeting strategy.

Here’s what’s included:

🔄 Full Export — Not Just One Page Clicking the Export button now downloads all companies in your Intent Tracker — not just the ones visible on your current screen. All visible table columns are included in the export.

📁 Excel Format (.XLSX) The exported file arrives in a clean and structured Excel format with all column headers and data preserved — perfect for filtering, sorting, or sharing with your team.

⚙️ Background Processing Exports are processed in the background, so your page won’t freeze or slow down. You can keep working while the file is being prepared.

📧 Email Notification When Ready Once your export is complete, you’ll get an email from Sopro ([email protected]) with a download link — no need to wait around.

🚫 No Duplicate Requests While your export is in progress, the Export button will be temporarily disabled to prevent duplicate requests. It reactivates once the export is complete.

Why it matters: You now have more flexibility and control over your intent data — helping you prioritize and act on opportunities more effectively.

🎯 Update: Only Active Audiences Now Shown in Email Template Preview #CX

We’ve improved the Audience selection dropdown in the Email Template Preview to ensure it only shows active audiences — making your preview experience cleaner and more accurate.

What’s changed:

📉 Before: Previously, inactive audiences were still appearing in the dropdown, even if they were no longer in use or had the “Show prospects in Portal” toggle turned off.

Now: The dropdown will only display active audiences with the “Show prospects in Portal” toggle enabled — helping you focus on relevant, live audiences when previewing email templates.

Why it matters: This update reduces clutter and confusion when selecting test audiences and ensures your previews reflect the real, active campaign setup.

🛠 Fix: Corrected Summary Notification Timing for IP Match Alerts #CX

We’ve resolved an issue affecting clients who switched their Intent goal alerts from “Real-time instant alerts” to “Batch and send daily summary.”

What was happening: When switching to the daily summary setting, the first email included all historical prospect visits, rather than just those from the past 24 hours.

What’s changed: The system now correctly sends summaries based on the intended timeframes:

  • Daily summaries include visits from the past 24 hours only.

  • Weekly summaries include visits from the past 7 days only.

This fix ensures you're only seeing the most relevant and recent activity in your notifications.

🛠 Fix: Improved Accuracy of Website Session Tracking in Activity Feeds #CX

We’ve fixed an issue in the Intent Tracker that was causing multiple sessions to be displayed incorrectly in the Activity Feed (found under Prospects and Company pages in the Portal).

What was expected: Website sessions should group together all visits from the same IP or prospect within a 4-hour window. A new session should only start after a 4+ hour gap in activity.

What was happening: In some cases (e.g. with LawyerLink), visits to pages like the Privacy Policy were mistakenly triggering new sessions — even if they happened just 2 minutes apart. This led to inflated session counts and cluttered activity feeds.

What’s fixed: Website sessions are now correctly grouped, even if the visit includes pages like the Privacy Policy. This means:

  • Fewer, more accurate sessions in the feed

  • A clearer view of how each prospect or company is engaging with your site

This update ensures your intent signals are more reliable and easier to interpret.

🛠 Fix: Prevented Duplicate Leads from Being Created via Zoho Integration #CX

We’ve resolved an issue where duplicate leads were being created in Zoho CRM for the same prospect when triggered by a website visit.

What was expected: When a prospect visits your website, the integration should:

  • Check for existing records in your CRM,

  • And either update the existing lead or skip the import, based on your integration mapping settings.

What went wrong: Due to a bug, the system was re-importing the same prospect multiple times, creating duplicate leads in Zoho — even though the contact already existed in the CRM.

What’s fixed: The system now correctly:

  • Detects existing prospects before attempting to import,

  • Follows your configured mapping rules to either update or skip the import,

  • Ensures no duplicate leads are created from repeated website visits.

Why it matters: This fix keeps our clients' CRM clean and avoids confusion or redundancy in your lead management process.

Internal process updates

✨ New: Choose Your Preferred AI Model for Generative Email Templates #CS #Ops

We’ve introduced a new option in the Email Templates > Generative Template Settings section that allows you to select which AI model is used to generate your email messages — giving you more control over performance, efficiency, and cost optimization.

What’s new:

  • A new AI Model dropdown menu is now available in Generative Template Settings.

  • You can choose from the following AI models:

    • OpenAI (default)

    • Grok

    • DeepSeek

    • Anthropic

Access Control: This new setting is only available to Super Admins, ensuring consistency and control across campaigns during these initial testing phase.

Why it matters: Selecting the right model helps you balance speed, quality, and cost based on your campaign needs — without disrupting your existing workflows.

✨ New: Re-Generate Generative Messages by Upload Date #Ops

We’ve added more control to the Generate/Re-generate feature, allowing you to select a specific date range when updating generative email messages — so you can target only the prospects you need, without affecting others.

What’s new:

🗓 Filter by Upload Date: When using the Generate/Re-generate button, you’ll now see an option to specify a date range. This lets you re-generate messages only for prospects uploaded within that period.

Smart Validation:

  • Accepted format: DD/MM/YYYY

  • If you enter an invalid date (e.g., in the wrong format like MM/DD/YYYY), the system will show an error and ask for a correction.

💡 Helpful Tooltip: Hover over the date field to see a quick reminder of the correct date format — no guessing needed.

🔁 Flexible Re-Generation Options:

  • If you enter a valid start date (e.g., 28/03/2025), the system will re-generate messages for all prospects uploaded on or after that date.

  • If you leave the date field empty, it will re-generate messages for all prospects.

Why it matters: This update makes it easier to refresh messaging only where needed — perfect for fine-tuning outreach after template updates or campaign changes.

🛠 Fix: Proper Handling of Previously Engaged & Excluded Prospects During Re-Uploads #Ops

We’ve fixed an issue that affected how excluded prospects were handled when re-uploaded to a campaign.

What was happening: When a prospect was:

  • Previously engaged in a campaign,

  • Later added to the exclusions list,

  • And re-uploaded to the same campaign (with CampaignDuplicateDays > 0),

The system was incorrectly uploading that prospect again with a status like New or Verify, and showing them in the "Prospect Search Again" category — rather than flagging them as excluded.

What’s changed: Now, when you re-upload a prospect who is:

  • On the exclusions list, and

  • Already engaged in that campaign previously,

The system will:

  • Skip the upload of that prospect,

  • Accurately log them as excluded in the upload results,

  • Ensure campaign rules and exclusion logic are fully respected.

Why it matters: This fix helps maintain clean prospect lists, reduces costs for Generative messaging, and ensures your upload logs clearly reflect exclusion behavior.

Last updated