What's New

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.

• Snowflake integration Overview

• Import Data from Snowflake to Netcore

Until now, visitors who browse and leave before entering contact details stay anonymous. You cannot reach them.
Now, NitroX (Nitro Commerce) identifies these visitors through cookieless tracking. It sends their profiles and website events to Netcore CE for pre-checkout campaigns.

What’s New

• Added a Netcore integration in NitroX. It sends identified visitors to Netcore CE as contacts.

• Added 12 website events, such as nitro_product_view, nitro_addtocart, and nitro_orders/create. You choose which events NitroX sends.

• Use nitro_events and the NITRO_ID attribute in segments and Journeys.

• Set up with no website code changes.
  
  Why It Matters

• Reach intent early: trigger browse abandonment, cart recovery, and checkout drop-off Journeys.

• Keep profiles clean: pick a Primary Identifier (Phone Number, Email, or Anon ID) that matches your Customer ID.

Prerequisites: a NitroX account; your Netcore account team enables data sharing with Nitro Commerce.
Best fit: D2C and retail brands.

Set it up in 4 steps

1. In NitroX, go to Integrations > Netcore.

2. In Netcore CE, copy the API key (Profile > User Profile) and the Asset ID (Settings > Website). Paste both into NitroX.

3. Select your Data Center (it must match Netcore CE), your Primary Identifier, and your events. Phone numbers need the country code.

4. Click Save and confirm the Connect with Netcore toggle is on.
   
   Refer to the documentation here:

• Nitro Commerce

• Import data to Netcore from Nitro

• Track Nitro Data in Netcore

• Nitro Event and Contact Payload Reference

Managing large template libraries just got a whole lot easier. The revamped Email Content experience introduces a unified Template Gallery, Saved Templates, and Folders view, making it simple to find, organize, and reuse templates from one place.

What's New

• One unified template workspace with Template Gallery, Saved Templates, and Folders in a single experience.

• New Folder support to organize templates at scale, while Categories continue to work as flexible tags.

• Powerful search and filters to quickly find templates by name, type, category, creation method, usage, or last edited date.

• Bulk actions to move, categorize, or archive multiple templates in a single click.

• Smarter template management with built-in safeguards that protect templates already in use.

• Consistent creation experience across HTML and AMP templates, with streamlined editor selection and updated editor names.

• Improved template reuse, including automatic copies of system templates so the originals always remain intact.

Whether you are managing a handful of templates or thousands, the new experience helps your team stay organized, collaborate more efficiently, and launch campaigns faster.

Refer to the complete documentation here:

• Template Gallery

• Folders

• Saved Template

• Create Email Template

We've received a few queries through Docbot and from our support teams regarding the Upload HTML option seemingly disappearing after the Email Content Section revamp.

Just to clarify, the functionality has NOT been removed or changed. It has simply been reorganized under the Code Editor as part of our new, streamlined Email Content experience.

Here's how to upload an HTML file in the new UI:

1. Navigate to Content → Email.

2. Under Create a new template, select HTML.

3. Choose Code Editor.

4. Click Import within the editor.

5. Select Upload HTML File.

6. Choose whether to Keep image links as-is or Download & host images.

7. Upload your HTML file and click Proceed.
   
   Important: This is purely a UI/navigation change. All existing HTML upload capabilities remain available, including the ability to import HTML files and manage image hosting preferences.