Source: https://cli.nylas.com/docs/commands/deliverability-tracking-events-summary

# nylas deliverability tracking-events summary

Show engagement totals and open and click rates.

Written by [Qasim Muhammad](https://cli.nylas.com/authors/qasim-muhammad) Staff SRE

Published November 3, 2026

Updated November 3, 2026

## What does nylas deliverability tracking-events summary do?

The nylas deliverability tracking-events summary command reports engagement totals and open and click rates, with the change against the prior period. It covers only messages sent from an Agent Account or through Transactional send; messages from connected grants such as Google or Microsoft accounts are not included. Only messages sent with open or link tracking turned on have tracking events. Open and click rates count first interactions per tracked message.

## Usage

```bash
nylas deliverability tracking-events summary [--start YYYY-MM-DD] [--end YYYY-MM-DD] [--sending-domain DOMAIN] [--json]
```

## Flags

| Flag | Description |
| --- | --- |
| --json | Output as JSON |
| --no-color | Disable color output |
| --verbose(-v) | Enable verbose output |
| --config | Custom config file path |
| --help(-h) | Show help for the command |
| --limit | Limit results (most list commands) |
| --yes(-y) | Skip confirmations |
| --end | Last UTC day, YYYY-MM-DD, inclusive (default: today) |
| --sending-domain | Only this sending domain |
| --start | First UTC day, YYYY-MM-DD (default: 6 days before --end) |

## Examples

The nylas deliverability tracking-events summary command reports engagement totals and open and click rates, with the change against the prior period.

### Engagement since October 1

```bash
nylas deliverability tracking-events summary --start 2026-10-01
```

## Example output

```text
Prior period:  2026-08-29 → 2026-09-30

TRACKED OPENS  OPENED  OPENS TOTAL  TRACKED LINKS  CLICKED  CLICKS TOTAL
900            410     820          600            75       110

RATE   VALUE   CHANGE  PRIOR
open   45.56%  —       —
click  12.50%  —       —
```

## Troubleshooting

### invalid --start value on a metrics command

Metrics windows take UTC dates in YYYY-MM-DD form, both days included, and can span at most 365 days. Unix timestamps and look-backs are for the activity list commands only.

### A rate shows a dash instead of 0%

A dash means the rate has no denominator in the window (for example no sends), so there is no data. It is not a 0% rate.

## Related commands

[nylas deliverability send-alerts createCreate a send alert rule.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-create)

[nylas deliverability send-alerts deleteDelete a send alert rule.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-delete)

[nylas deliverability send-alerts listList send alert rules.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-list)

[nylas deliverability send-alerts showShow a send alert rule.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-show)

[nylas deliverability send-alerts updateChange a send alert rule; flags you leave out keep their value.](https://cli.nylas.com/docs/commands/deliverability-send-alerts-update)

[nylas deliverability send-events breakdownShow send counts and rates per sending domain, agent account, or recipient domain.](https://cli.nylas.com/docs/commands/deliverability-send-events-breakdown)

## Recommended guides

[Track Email Opens, Clicks, and RepliesSend tracked email and receive open, click, and reply events over webhooks from the terminal. Verify the signatures, and learn why email open rates overcount.](https://cli.nylas.com/guides/track-email-opens-replies-cli)

[SMTP Reply Codes ExplainedDecode SMTP reply codes: 2xx success, 4xx transient retry, 5xx permanent. Read bounce DSN enhanced codes and debug delivery from the terminal.](https://cli.nylas.com/guides/smtp-reply-codes-explained)

[Email Bounce Codes Reference (DSN)Decode bounce DSNs: RFC 3463 enhanced status codes (5.1.1, 5.2.2, 4.x.x), hard vs soft bounces, and finding them with nylas email search from:mailer-daemon.](https://cli.nylas.com/guides/email-bounce-codes-reference)

[Validate Email Addresses from the CLIValidate email addresses from the terminal with an RFC 5322 syntax check and a dig MX lookup, then gate nylas email send to cut hard bounces.](https://cli.nylas.com/guides/email-address-validation-cli)

[AI Agent Email Bounce Detection and RetryDeterministic bounce rules for AI agents: classify soft vs hard from DSN codes, retry 4.x.x with backoff, suppress 5.x.x, and escalate edge cases to humans.](https://cli.nylas.com/guides/ai-agent-email-bounce-retry)

[Soft Bounce vs Hard Bounce ExplainedSoft bounces (4xx) are transient and retried for up to 5 days; hard bounces (5xx) are permanent. Code ranges, suppression rules, and terminal detection with the CLI.](https://cli.nylas.com/guides/soft-bounce-vs-hard-bounce)

Run `nylas deliverability tracking-events summary --help` for full help output.