nitrosend-analytics
Inspect Nitrosend account, campaign, flow, or message performance and turn live metrics into bounded recommendations. Use when: "email analytics", "campaign performance", "how are my emails doing", "email insights", "check my stats", "open rate", or "deliverability report".
Analytics
Use live Nitrosend data as the source of truth. Do not apply fixed global "good", "warning", or "critical" thresholds from this skill.
Select Scope
- Account overview:
nitro_get_insightswithscope: "account" - Campaign:
scope: "campaign"plusentity_id - Flow:
scope: "flow"plusentity_id - Individual message and events:
scope: "message"plusentity_id
Supported periods for account, campaign, and flow insights are 7d, 30d, and
90d.
Interpret Responsibly
- Lead with delivery, volume, opens, clicks, unsubscribes, complaints, and the trend data the tool actually returns.
- Prefer benchmarks and recommendations returned by
nitro_get_insights, then compare with the same account's prior period and similar sends. - Treat opens as directional because mailbox privacy features can inflate or obscure them. Give clicks, conversions, replies, complaints, and revenue greater weight when available.
- State the sample size and period. Do not call a change meaningful when the evidence is too small or the compared periods differ materially.
- Label external industry ranges as contextual, source them freshly, and do not present them as Nitrosend product facts or guarantees.
Deeper Review
For a broader account review:
- Pull 30-day and, when useful, 90-day account insights.
- Query recent campaigns with
nitro_queryentitycampaigns. - Query relevant flows using statuses allowed by the live
nitro_queryschema, such asliveorpaused. - Inspect audience and deliverability context from
nitro_get_statusand the returned insights rather than deriving unsupported counts. - Prioritize one or two testable changes and define the metric and observation window before recommending a rollout.
Typical hypotheses include subject or sender clarity for weak opens, content hierarchy and CTA clarity for weak clicks, consent/frequency/targeting for unsubscribes or complaints, and flow coverage for missed lifecycle moments. These are hypotheses to test, not diagnoses from one metric alone.
Scheduled Reports
Recurring reports run only when a user has configured them through a host that actually exposes scheduling. Never imply that installing this plugin creates background jobs by itself.
Related skills
- Downloads
- Security audit
- Pass
- Last updated
- 3w ago
- Current version
- v1.0.0
- License
- MIT-0
