Skip to main content

What's New

Follow new updates and improvements to Netcore CE.

EnhancementsImprovement

Avoid disturbing customers during quiet hours with day-level DND control

You can now configure Do Not Disturb windows separately for each day of the week, so your journeys only send messages during the allowed communication hours for that specific day.

For example, you can pause weekend communication completely, keep weekday messages active during business hours, or set different quiet-hour windows for high-engagement and low-engagement days.

What’s new

  • Choose the exact days when messages are allowed to go out.

  • Set different DND hours for each selected day.

  • Copy one day’s schedule across the week to save setup time.

  • Automatically hold messages triggered during quiet hours and send them when the next open window starts.

This helps you avoid disturbing customers at the wrong time, respect regional quiet-hour requirements, and continue delivering triggered journey messages without dropping them.

Go to Account Configuration to set up custom day-level DND windows for your journeys.

WhatsAppImprovement

WhatsApp & RCS Reporting Update: Bounce Metrics Now Available

We have refined how message outcomes are reported for WhatsApp and RCS, aligning Netcore CE with industry standards. Previously, messages that could not be delivered, such as numbers that were not available on WhatsApp, were counted under Failed. This dragged down failed metrics, unrelated to the campaigns and journeys actual performance.

What is Changing

  • Made Sent a deterministic, Netcore-derived metric — no longer dependent on channel webhooks.

  • Clarified what Not Sent means and how it is reported.

  • Introduced a new Bounce metric for WhatsApp and RCS.

  • Updated the Failed % calculation to exclude bounced messages.


These changes apply uniformly across Campaigns and Journeys, across WhatsApp and RCS.

Impact Areas
You will see these changes reflected in:

  • Campaign Summary and Detailed Reports — for WhatsApp and RCS campaigns.

  • Journey Summary and Detailed Reports — for Journeys using WhatsApp and RCS nodes.

  • Campaign listing page — Bounce now appears as a reporting metric.


    Heads up: After the release, your Failed count will reduce and Failed % may shift. This is expected — the underlying performance of your campaigns & journeys hasn’t changed, only how it’s reported. For more details, refer to detailed documentation.

    PS Note - It will be released on India IDC thursday (May 21) and next week it will be on EU and US idc.

Improvement

Enhanced Duration-based Reporting for Onsite Campaigns (WebMessage & In-App)

We’ve enhanced the Onsite Reports for WebMessage and In-App channels to provide marketers with more precise insights into campaign performance. Previously, reports displayed cumulative campaign data from the start date to the present. With this update, marketers can now download performance reports for a selected time duration.

This improvement enables better visibility into how campaigns are performing within specific periods. Marketers can now easily analyze key metrics—such as views, clicks, and conversions—within a chosen timeframe, helping them make informed decisions and take timely corrective actions to optimize campaign effectiveness.

💡 The report download functionality remains unchanged—only the data inside the downloaded report now reflects the selected duration.

Report Documentation Link

EnhancementsImprovement

Streamlined Campaign Duplication Workflow

Users are now redirected to the campaign edit page immediately after using the ‘Copy Campaign’ action, instead of being taken back to the campaign listing screen. This enhancement applies across all campaign types, including:

  • Email

  • SMS

  • App Push Notifications (APN)

  • Web Push Notifications (WPN)

  • WhatsApp

  • Onsite Messaging – In-App and Web Message

This update ensures a smoother editing experience post-duplication, reducing navigation friction and improving overall campaign setup efficiency.

Watch Video

EnhancementsImprovement

Bulk Delete option for Draft Push Campaigns

You can now delete draft campaigns in bulk from the Campaign section. This enhancement introduces a 'Delete' option via the standard bulk selection component. Users can select multiple draft campaigns and perform a single delete action.

🧩 Tip

Use the bulk select checkbox at the top of the campaign list to quickly select multiple drafts for deletion.

Watch Video

Key highlights:

  • ✅ Only 'Draft' campaigns are eligible for deletion. Even if the user selects all campaigns, only those in Draft status will be processed for deletion.

  • ✅ Applicable across all push channels — including Web Push, App Push, Email, SMS, APN, BPN, RCS, and WhatsApp — to maintain parity and provide a consistent user experience.

  • ✅ RBAC-based access control: Delete action is enabled only for users with the required permissions.

  • 🚫 If the user lacks permission, the Delete button appears grayed out with a tooltip:
    “You do not have the necessary permissions to perform this action. Please contact your admin.”

  • 🧮 Draft campaign count is now visible in:

    • The listing page

    • Confirmation popup

    • Deletion success toaster message

  • ⚠️ The Delete button is disabled (grayed out) when no drafts are available for deletion, with appropriate visual feedback.

This improvement addresses key feedback from our customers around onboarding friction and improves control over draft campaign clean-up.

❓ Quick FAQ’s

1. Which campaigns can be deleted in bulk?

Only campaigns in 'Draft' status can be deleted in bulk. Even if users select all campaigns, only drafts will be considered for deletion.


2. Is the bulk delete available for all campaign types?

No. This feature is only available under Push Campaigns. Other modules like Content, Online, and Journey do not currently support bulk selection and are therefore excluded.


3. Which channels are supported under bulk delete?

Bulk delete applies to all push channels, including:
Web Push, App Push, Email, SMS, APN, BPN, RCS, and WhatsApp.


4. What happens if a user selects all campaigns, but some are not drafts?

Only the selected draft campaigns will be deleted. Other statuses (e.g., Scheduled, Sent) will be ignored, even if selected.


5. What if there are no draft campaigns selected?

The Delete button will remain disabled (grayed out), and no delete action will be possible.


6. Can every user access the bulk delete feature?

No. Access is controlled via RBAC (Role-Based Access Control). Only users with the required permissions will see the active Delete option.


7. What happens if a user without permission tries to delete campaigns?

The Delete button will be grayed out and show the tooltip:
“You do not have the necessary permissions to perform this action. Please contact your admin.”


8. Where can users see how many drafts will be deleted?

The draft count appears in three places:

  • In the listing view

  • On the delete confirmation pop-up

  • At the success toaster message


EnhancementsImprovement

Modify Event Payload Data Types

We are pleased to announce that users can now directly modify the data types of event payload properties from the Events section of the Netcore CE dashboard. This enhancement helps to correct misidentified fields that may result from SDK misconfigurations or integration issues.
Key Details:

  • Permissions: This action is restricted to users with Edit Event permissions.

  • Audit Trail: All modifications are logged under Event Logs for full auditability.

  • Supported Conversions:

    • String/Text → Integer

    • String/Text → Float

    • Integer → Float

Important Considerations:

  • This change applies only to future events. Historical data will not be affected.

  • To prevent data loss, please ensure your app, web SDK, or API integration is updated to send event payloads in the newly configured data type. Failure to do so may cause events to be dropped.

For detailed instructions, please refer to our documentation here.

Improvement

Important TRAI Direction: Principal Entities and Telemarketer Chain Binding on DLT for SMS Traceability

Dear Customer,

Greetings from Netcore Cloud!

This is to inform you about the implementation of TRAI direction regarding Principal Entities (PE) and Telemarketer (TM) Chain Binding for traceability of SMS delivery.

For more details on TRAI's direction, please click here

As per TRAI's direction, all Principal Entities (PEs) must disclose the complete chain through which their SMS communication will reach the end customer. This includes all involved Registered Telemarketers (RTMs).

This means that all Principal Entities are required to declare their corresponding Telemarketers, Aggregators, and Delivery Telemarketers chain on DLT to maintain transparency and visibility throughout the communication chain.

The TRAI Directions will be enforced by operators starting 1st November 2024, and failure to comply may result in SMS delivery failures from this date onward.

Please be advised that telecom operators are working to implement this feature on their DLT platforms and will share further details soon. We will keep you informed of any further updates.

For any queries, please feel free to contact us at CpaaS: [email protected] & CEE [email protected]

Thank you for your understanding and continued trust in Netcore Cloud.

Best Regards,

Team Netcore Email: [email protected]

Improvement

📊 Revenue Dashboard Enhancement

Overview:

We are pleased to announce significant improvements to the Revenue Dashboard, aimed at enhancing data accuracy and providing a clearer picture of Netcore's contribution to your revenue.

Key Changes:

  • Accurate Netcore Contribution: The Netcore contribution (New) section now exclusively reflects revenue directly attributable to your campaigns and journeys. This eliminates any ambiguity and ensures the reported revenue aligns precisely with the performance of your marketing efforts.
  • Simplified Attribution: We've standardized on the last-click attribution model, offering a straightforward understanding of how campaigns and journeys influence conversions.
  • Conversion Goal Alignment: Revenue is now solely attributed to campaigns and journeys where a specific conversion goal has been defined. This prevents over-attribution and delivers more actionable insights.
  • Enhanced Channel Performance: We've refined the channel performance widget to focus on click-through attribution for in-apps and web messages, ensuring accuracy in measuring user engagement. Additionally, WhatsApp has been added as a new channel for comprehensive tracking.

Benefits:

  • Increased Data Reliability: The Revenue Dashboard now presents a more accurate and trustworthy view of Netcore's impact on your revenue.
  • Improved Decision-Making: Gain clearer insights into the effectiveness of your campaigns and journeys, enabling data-driven optimizations.
  • Streamlined User Experience: We've simplified the dashboard by removing controls that are no longer relevant, creating a more focused and user-friendly interface.

Technical Details:

  • Last-Click Attribution: Revenue is attributed to the last campaign or journey a user interacted with before converting.
  • Conversion Goal Requirement: Only campaigns and journeys with defined conversion goals contribute to the Netcore revenue figures.
  • Channel Performance Update: Click-through attribution is used for in-apps and web messages, and WhatsApp has been added as a trackable channel.

P.S. For the next sixty days, you can continue access both the new and old dashboards so you can get used to the new logic.

We believe these enhancements will empower you to make more informed decisions and maximize the value of your Netcore investment. Should you have any questions or feedback, please don't hesitate to reach out to our Helpdesk team or your Success Manager.

Here is the documentation link:

Documentation
Improvement

New features for In-app and web messages

We are thrilled to announce our latest feature updates and enhancements for In-app and Web messages.

Your panel will be automatically updated with the below features between 9th and 12th July.

1. Unified Onsite Listing and revamped In-app and Web Message Campaign Creation Flow

Introducing a unified listing page for onsite channels, combining both In-app and Web message campaigns.

The in-app and web messaging flows are revamped to improve usability and functionality.

Web message documentation

In-app message documentation

2. Configurable Conversion Window and Revenue Tracking for Onsite Channels

Marketers can now define the conversion window for each campaign, choosing from minutes, hours, days, or weeks. With revenue tracking capabilities, marketers can monitor and attribute revenue generated by their campaigns.

Documentation

3. Attribution Change from View-through to Click-through

Attribution for onsite campaigns is shifting from view-through to click-through.

Ensures more accurate attribution of conversions to the last-clicked campaign.

4. Report Scheduler for In-app and Web Messages

Report scheduler functionality for in-app and web message campaigns, allowing users to schedule and download summary and detailed reports.

Benefits:

  • Options to download reports immediately or schedule for later.
  • Supports multiple channels and report types.
  • Customizable scheduling frequency (daily, weekly, monthly).
  • Delivery via email or FTP.

Documentation

Impact on Existing Campaigns

- Campaign Stoppage: All in-app and web message campaigns with control groups more significant than 0% will be auto-stopped. Clients will need to recreate these campaigns due to changes in calculation logic due to changed control group logic and click attribution.

If you have any questions, please contact your respective Account Manager.

Improvement

Introducing Enhanced Goal Setting for Existing Journeys

The latest release brings a highly anticipated feature to the platform: enhanced goal-setting for existing journeys.

This new functionality allows users to add goals to journeys previously created without them. This feature is designed to provide users with more control and customization options for their journeys, enabling them to set clear objectives and track their progress towards them. The theme of this release is empowering users to optimize their journey planning and execution by adding goals to existing journeys. This feature aligns with our commitment to continuously improve the user experience and deliver innovative solutions that meet the evolving needs of our customers.

Allow Users to Add Conversation Goals and Revenue Parameters to Existing Journeys

This new feature will enable users to add conversation goals and revenue parameters to journeys previously deployed without them. As user research suggests, CE's contribution to client revenue will increase. Users can also set default values for Google Analytics tracking and conversion goals in advanced global settings. This feature will be useful for users who initially forget to configure goals but want to add them later. We hope you enjoy these new features and welcome any feedback for future improvements.