What's New
Follow new updates and improvements to Netcore CE.
Until now, your journey summary report gave you one row for your entire selected duration.
Pull a 30 day report, and you got 30 days of performance squeezed into a single line. No day by day view. No way to compare one week against another without running separate reports.
That changes now. You can group your journey summary report data by day, week, or month, right from the export panel.
What’s New
Added a Group data by option to the journey summary report export panel.
Choose to group by Day, Week (Monday to Sunday), or Month, or keep the existing single row view with Do not group data option.
Get a new Grouped by duration column in your CSV that marks the exact period for each row.
Works for both one time downloads and scheduled downloads of the detailed summary report.
Why It Matters
No more manual date splitting: get daily, weekly, or monthly breakdowns in one export instead of running the report multiple times.
Spot trends faster: compare specific weeks or months side by side without extra spreadsheet work.
Cleaner CSVs: the new duration column tells you exactly which period each row covers, so nothing gets mixed up.
Prerequisites: Available only for the detailed summary report, not the custom detailed report.
On the CE dashboard, navigate to Engage > Journey > Export report > Group data by to try it out.
Read the documentation to know more.
Frequency Capping already controls how often users see In-App messages. Until now, it applied to all campaigns with no option to bypass it for specific campaigns.
Now, marketers can choose which campaigns should follow the global cap and which important campaigns should skip it.
What’s New
Added Skip Global Frequency Capping at the campaign level.
By pass daily, weekly, or monthly in-app channel specific frequency capping limits for selected campaigns.
Available for Regular, A/B, and Split In-App campaigns.
Why It Matters
Ensure important or time-sensitive campaigns reach users.
Keep frequency capping on for regular campaigns.
Get more control over campaign delivery.
Prerequisites
Navigation: Campaigns > In-App Messages > Create Campaign > Schedule
Learn more: Frequency Capping documentation
Until now, you add checks like check attribute or has done event at many points in your journey to stop messages for users who converted when they are part of the journey. That adds nodes and raises the risk of setup mistakes.
Now, you can set Exit Conditions once in your journey settings.
What’s New
Added an Exit Conditions block to journey settings. It applies to the whole journey.
Set rules on events, user attributes, and segments or lists.
Add up to 5 conditions and link them with AND or OR.
Filter an event by its payload, such as Price greater than 10,000.
Set event counts, such as Dismiss_Banner greater than 5.
See how many users exited in the Exits section of Journey Performance.
Why It Matters
No more extra nodes: define the rule once and Netcore applies it to the whole journey.
Stop irrelevant messages: users who buy or complete KYC no longer get reminders.
Fewer opt-outs: users stop seeing messages that no longer fit, which lowers unsubscribes and uninstalls.
Protect your margin: discounts stop for users who no longer qualify, such as repeat buyers.
Use cases
Cart abandonment: the user buys the product, leaves the journey, and reminders stop.
KYC onboarding: KYC_Status is Verified, so the user leaves the reminder journey.
Fatigue control: the user dismisses a banner more than five times and leaves the journey.
Limits to know
Netcore looks at events from the time the user enters the journey. The maximum lookback period is 30 days.
Segments refresh every 30 minutes. Users may receive messages for up to 30 minutes after they meet a segment condition.
A journey cannot use the same event as its trigger and as an exit condition.
On the CE dashboard, open your journey in the journey builder and navigate to Journey settings > Exit Conditions > + ADD CONDITIONS to set your first rule.
Read the documentation to know more
Until now, bringing warehouse data into Netcore CE meant manual uploads.
Now, you can connect Netcore CE to Databricks and import contacts/events straight from a Databricks table or view.
What’s New
Added a Databricks integration under the Data warehouse category. It connects to a Databricks SQL warehouse with OAuth M2M credentials from a service principal.
Import contacts from a Databricks table or view into the contact master. Add them to lists if you want.
Map Databricks columns to Netcore CE attributes. Create a new attribute when none matches.
Run a one-time import or a recurring schedule. The first recurring run transfers the full dataset. Later runs transfer only incremental data.
Why It Matters
No more manual uploads: keep attributes such as loyalty tier and lifetime value current on a schedule.
Use your warehouse models in campaigns: import scores, RFM segments, or churn propensity as contact attributes for segmentation.
Stay secure: the connection uses a service principal, not a personal login.
Prerequisites: read access to the Databricks catalog, schema, and table or view; the service principal’s Client ID and Secret key; the Server hostname and HTTP path of your SQL warehouse; an EMAIL column and an Updated on timestamp column in the source; an alert email address.
To integrate: Navigate to Settings > Integrations > Data warehouse > Databricks.
To start an import: Go to Settings > Data transfer > Import > CREATE NEW.
Refer to the documentation here:
Until now, App push notifications were sent to a user’s recent devices automatically, with no way to control it. A user active on one device could still receive the same push across others, and you had no say in where it landed.
Now, Device Targeting puts that choice in your hands. For every App Push campaign, decide whether a notification reaches all of a user’s active devices or only the one they’re currently using.
What’s New
Added a Device Targeting option in the App Push Audience section in campaign and on the App Push node in Journeys.
All active devices(default): reach every active device a user has.
Latest active device only: reach just the device the user most recently opened the app on.
Opted-out and uninstalled devices are automatically excluded from both options.
Why It Matters
Reach what matters: send awareness and offer campaigns to all devices for maximum visibility.
Deliver with precision: send OTPs, payment alerts, and time-sensitive messages only to the device the user is actively using.
Keep existing campaigns safe: campaigns scheduled before this release are unaffected and continue to send to all active devices.
Confirm delivery: check which devices a notification reached in your campaign report.
Important to Know
All active devices is selected by default.
For a campaign targeting both Android and iOS, the latest active device is the single most recently used device across both platforms.
If you select Latest active device only and that device has opted out or uninstalled the app, the user isn’t sent the notification on an older device instead.
Navigation: Engage > Campaigns > Create > App Push > Audience, then set Device Targeting.
Refer to documentation here.
Until now, Web Message campaigns were limited to running a single message variant, making it harder to compare different content and identify what works best with your audience. Now, you can create A/B and Split Web Message campaigns to test multiple message variants and compare their performance.
What’s New
Added support for A/B and Split campaigns for Web Messages.
Create multiple message variants within a single campaign.
Use A/B testing to identify the best-performing variant.
Use Split testing to distribute different variants across your audience and compare performance.
Why It Matters
Test different messages to identify what resonates with your audience.
Compare campaign performance without creating separate campaigns.
Optimize Web Message engagement using data-driven insights.
Important Note
Once this feature is enabled, templates created using the BEE Editor and Pseudo Editor will no longer be supported across all campaign types including Regular campaigns as well.
Only templates built with UCE or Custom HTML can be used going forward in all campaign types.
Navigation: Engage > Campaigns > Create > Web Message. Reach out to me to get this feature enabled for your account until the feature is generally available (GA).
Refer to the documentation to know more.
Schedule Netcore CE event data to export directly to your own SFTP server, in the file format your pipeline already reads.
What’s New
Added SFTP as an Egress Data Transfer destination. Pick a connection and target directory in a few clicks.
Added three export formats: CSV, JSON, and Parquet.
Added data transformations: mask fields, rename columns, convert field types, reformat dates.
Added Send Test Data to validate your setup with a sample file.
Added flexible scheduling: set start/end dates and frequency (Hourly, Daily, Weekly).
Why It Matters
Pick the format your systems already read: CSV, JSON, or Parquet.
Mask and reshape sensitive fields before data leaves Netcore.
Validate with sample data first, then let the schedule run on its own.
Prerequisites: a pre-configured SFTP connection under Settings > Integrations; supports standard and behavioural events with Standard or Consolidated schema.
Navigate to Settings > Data Transfer > CREATE NEW, select Export data > Events, and choose SFTP to start scheduling exports.
Read the documentation to know more.
Until now, clicking the unsubscribe link in your email took users to the default Netcore unsubscribe experience.
Now, you can replace that default link with your own unsubscribe page. Build an experience that matches your brand, collect feedback on why users are leaving, or give them the option to manage their communication preferences instead.
What’s New
Added support for a custom unsubscribe link that replaces the default Netcore-generated unsubscribe link.
Let users land on your branded unsubscribe page instead of a standard unsubscribe experience.
Use your custom page to collect unsubscribe feedback and understand why users opt out.
Give users a preference center option so they can adjust their communication preferences instead of unsubscribing completely.
Manage the unsubscribe process and redirect users to your custom landing page after they click the link.
Why It Matters
Keep your brand experience consistent: Extend your brand identity to the unsubscribe journey.
Understand why users leave: Collect feedback when users choose to unsubscribe and use those insights to improve your email strategy.
Retain subscribers: Offer communication preferences for users who want fewer emails instead of opting out completely.
Stay in control: Manage the unsubscribe experience and landing page based on your business requirements.
Read the documentation to know more.
Until now, email unsubscribe was mostly all or nothing. A user who wanted to stop receiving promotional emails had to unsubscribe from everything, including important updates.
Now, Subscription Management lets you give recipients control over what they want to receive. Create subscription categories, group related preferences, and give users a branded preference page where they can choose what stays in their inbox.
What’s New
Added subscription categories to let recipients opt in or out of specific types of email.
Added groups to organize related categories and keep the preference page easy to navigate.
Added a customizable preference page where you can add your logo, background color, font, headline, body text, categories, and groups.
Added a mandatory Unsubscribe from All option for recipients who want to stop all email communication.
Automatically pre-fill the preference page with each recipient’s existing choices.
Added preference data as user attributes, so you can build segments based on the categories users have selected.
Added support for secure, token-based access to the preference page without requiring users to log in.
Why It Matters
Give users more control: Let recipients choose which emails they want instead of forcing an all-or-nothing unsubscribe.
Reduce unnecessary unsubscribes: Users can opt out of promotions while continuing to receive important transactional or service updates.
Keep your brand consistent: Customize the preference page with your brand elements and messaging.
Turn preferences into targeting data: Use subscription choices to build target or suppression segments for future campaigns.
Make preference management simpler: Users can update their choices directly from the email without logging in.
Limits to know: You can create up to 25 active subscription categories and 10 groups. Preference changes sync to segments within up to 6-12 hours.
Prerequisites: Preference Page is currently available as a controlled release and must be enabled by Netcore’s SRE team. GA release will be available soon. To enable Preference Page, contact your Netcore Account Manager. Once enabled, create and configure your subscription categories and preference groups in Subscription Management. Use the generated Preference Page URL as the unsubscribe link in your email template. When users click the unsubscribe link, they will be redirected to the Preference Page to manage their subscription preferences.
Customers are responsible for using the user’s preference values to build the target audience for campaigns and ensuring that emails are sent only to users who have opted in to the relevant subscription category.
On the CE dashboard, navigate to Settings > Preference Page to configure your subscription categories, groups, and preference page.
Read the documentation to know more.
Until now, bringing data from Snowflake into Netcore CE required additional data movement or integration workflows.
Now, you can connect Snowflake with Netcore CE and import data directly into your CE panel. This helps you use data stored in Snowflake for customer engagement and personalization.
What’s New
Added Snowflake as a data source for importing data into Netcore CE.
Connect your Snowflake account and configure the data import.
Import data from Snowflake into Netcore CE for use in customer engagement.
Manage the data transfer without manually exporting and uploading files.
Why It Matters
Bring data from your existing Snowflake warehouse directly into Netcore CE.
Reduce manual data movement between platforms.
Use centralized customer data to power more relevant engagement.
Navigation: Settings > Integration > Snowflake
Refer to the documentation to know more.
