Connecting NetCore on Clarisights
NetCore (formerly Smartech, now Netcore Cloud) is a customer engagement and email marketing platform. Connecting NetCore to Clarisights brings your email broadcast performance — sends, deliveries, opens, clicks, unsubscribes — into your reporting alongside paid and analytics channels, so you can compare email-driven engagement to spend-driven channels in a single view.
At a glance
| Authentication | None directly — the integration is mail-based. Clarisights provisions a unique mailman email address per account and you configure NetCore to email scheduled reports to it. |
| Permissions needed | Permission inside NetCore to schedule broadcast reports and send them to an external email address; password-protect the report download with the account's NetCore password |
| Account discovery | Manual — you create one Clarisights account per NetCore account / login |
| Data freshness | Tied to your NetCore report schedule. Mongo precomputation runs every 6 hours, at minute 10 (00:10, 06:10, 12:10, 18:10 UTC). |
| Lookback window | Driven by the date range of the reports you schedule in NetCore — Clarisights ingests whatever rows arrive in the email |
| Backfill on connect | Schedule a one-off historical report in NetCore for the date range you want; it lands in the same mailman address and Clarisights ingests it |
| Timezone | Configured per NetCore account in Clarisights; Sent Date in the report is interpreted in this timezone |
| Currency | Configured per account in Clarisights (NetCore reports do not include currency) |
| Levels supported | Account · Campaign (Broadcast) |
| Limited rollout | No |
Prerequisites
An active NetCore (Smartech / Netcore Cloud) account
The NetCore account password — used to decrypt the password-protected zip files NetCore sends in the report email
Permission inside NetCore to schedule broadcast reports and send them to an external email address
Knowledge of the timezone and currency you want this account to roll up to in Clarisights
Steps to Connect
Step 1 — Add NetCore in Clarisights
In Clarisights, go to Integrations → NetCore → Add Account.
[TODO: Screenshot needed — Integrations page NetCore row]
Step 2 — Provide account details
Fill in:
Name — a friendly label for the account
Email — the NetCore login email; this also doubles as the Account ID inside Clarisights
Timezone — timezone for interpreting Sent Date in the broadcast report
Currency — reporting currency to associate with this account
Click Save. Clarisights creates the account and provisions a unique mailman address for it (something like reports+nc+<id>@clarisights.com).
Step 3 — Copy the mailman address
Open the new account row in Clarisights and copy the mailman email address shown there. This is the destination NetCore will email reports to.
[TODO: Screenshot needed — NetCore account detail showing mailman address]
Step 4 — Schedule the broadcast report in NetCore
In NetCore (Smartech), go to Reports → Broadcast Report and schedule a recurring export with these settings:
Format — password-protected ZIP containing a CSV (NetCore's default secured-report format)
Password — your NetCore account password
Recipient — the mailman address from Step 3
Required columns — Broadcast Name, Message ID, From Field, Subject, Lists Names, Segments Names, Sent, Delivered, Bounce Count, Total Opens, Total Clicks, Unique Open, Unique Clicked, Unsub, Abuse, Forward, Sent Date
Cadence — daily is recommended; the report's date range determines the lookback
⚠ NetCore must password-protect the ZIP using the account password. Clarisights decrypts using the password you provided in Step 2; an unprotected ZIP, a different password, or a non-ZIP attachment will fail decryption silently and produce no rows.
Step 5 — Wait for the first report email
Once NetCore sends the first scheduled report, Clarisights' mailman processor:
Receives the email
Extracts the download link (the link with the word "here" in NetCore's email body)
Downloads the ZIP, decrypts it with your password, and parses the CSV
Imports rows as Broadcast / Campaign Reports
⚠ No data after the first scheduled run → Likely cause is the report email did not include a recognisable download link, or the ZIP password did not match. Verify the report email contains a download link (NetCore wraps it in the word "here"), and that the ZIP password matches the password attached to your NetCore account in Clarisights. Re-send the report after fixing.
Verify the connection
Go to Integrations → NetCore. The connected account should show its mailman email and "Active" status.
First broadcast data appears after the first scheduled NetCore report email arrives and the next Mongo precomputation run completes (every 6 hours).
Quick start: create a new report, add NetCore as the data source, and add Account · Campaign · NC: Sent · NC: Total Opens · NC: Total Clicks · NC: Unsubscribe.
Data available
Hierarchy
How NetCore's native objects map to the standard Clarisights levels:
Native object (NetCore) | Clarisights level |
Account / Login | Account |
Broadcast (one Message ID per send) | Campaign — NetCore's broadcast is the analogue of Clarisights' Campaign. There is no Ad Group or Ad level for NetCore. |
List / Segment | Stored as a Campaign-level dimension (List Name, Segment Name) — not its own hierarchy level. |
Dimensions
Dimension | Level | Description |
Account / Account ID | Account | NetCore account; Account ID is the login email |
Account Timezone | Account | Timezone configured at connect time |
Account Currency | Account | Reporting currency configured at connect time |
Campaign / Campaign ID | Campaign | Broadcast Name and Message ID from the NetCore report |
Subject | Campaign | Email subject line |
From Field | Campaign | Sender address used for the broadcast |
List Name | Campaign | NetCore list(s) the broadcast was sent to |
Segment Name | Campaign | NetCore segment(s) used to filter recipients |
Campaign Status | Campaign | Active / inactive flag derived from broadcast presence in subsequent reports |
Metrics
Metric | Description |
NC: Sent | Total emails sent for the broadcast |
NC: Delivered | Successfully delivered emails |
NC: Bounce Count | Total bounces (hard + soft) |
NC: Total Opens | Total open events (counts repeats) |
NC: Total Clicks | Total click events (counts repeats) |
NC: Unique Opens | Distinct recipients who opened |
NC: Unique Clicks | Distinct recipients who clicked |
NC: Unsubscribe | Unsubscribe events from the broadcast |
NC: Abuse | Spam / abuse complaint events |
NC: Forwards | Forward events |
NC: Total Open Percentage | Total Opens ÷ Sent |
NC: Total Click Percentage | Total Clicks ÷ Sent |
NC: Unique Open Percentage | Unique Opens ÷ Sent |
NC: Unique Click Percentage | Unique Clicks ÷ Sent |
NC: Click-Open Percentage | Unique Clicks ÷ Unique Opens |
Limitations & known constraints
Mail-based ingestion: NetCore is integrated through scheduled emailed reports, not via API. Data freshness is bounded by your NetCore report schedule (and is at most every 6 hours after that, when Clarisights' Mongo precomputation runs).
No Ad / Ad Group level: NetCore exposes broadcasts (campaigns) only. Treat the Broadcast as the Campaign-equivalent.
No spend / cost: NetCore reports do not include cost. Email-channel cost is typically modelled outside NetCore (e.g., as a custom metric in Clarisights).
Password-protected ZIP only: Clarisights expects NetCore's secured-report format (password-protected ZIP containing a CSV). Plain CSV attachments are not supported.
Strict CSV column expectations: column names must match the standard NetCore broadcast report (Broadcast Name, Message ID, Sent, Delivered, Total Opens, Total Clicks, etc.). Custom or renamed columns are not picked up.
Analytics joining: NetCore joins to Google Analytics via UTM tuples (source, medium, campaign name) using the GA Source/Medium mapping configured for your company. NetCore does not emit a tracking URL of its own, so the GA mapping is required for any cross-channel views.
Failures are silent at the email level: a malformed email or wrong password causes the email to be dropped and an internal error captured. The customer-facing UI does not surface ingestion errors today — file a support ticket if data stops arriving.
Operating notes
Refresh schedule: Mongo precomputation runs every 6 hours at minute 10 (00:10, 06:10, 12:10, 18:10 UTC). Underlying ingestion happens whenever NetCore sends a scheduled report email.
Lookback: bounded by the date range of the NetCore report you schedule. To backfill history, run a one-off NetCore export covering the desired range and send it to the same mailman address.
Multi-account: each NetCore login is one Clarisights account with its own mailman address. To onboard multiple NetCore accounts, repeat the flow for each.
Currency conversion: NetCore reports are unitless on cost; the currency you pick at connect time is metadata only.
Credential rotation: if you rotate your NetCore password, update it on the account in Clarisights immediately — ZIPs sent with the old password will fail to decrypt and produce no rows.
Need help?
When contacting support from the in-app messenger, please include:
The NetCore account name and the mailman email address (Integrations → NetCore)
Whether the report email was received in Clarisights' mailman — forward a sample email if possible
The exact error message or screenshot
The step where the issue occurred
When the issue started and the cadence of the NetCore report