molted analytics

Command	Description
`molted analytics fatigue`	Check contact fatigue score
`molted analytics velocity`	Check send velocity metrics
`molted analytics deliverability`	Check deliverability metrics
`molted analytics segment-check`	Check if a contact belongs to a segment
`molted analytics policy-decisions`	Breakdown of allowed/blocked policy decisions
`molted analytics suppressions`	Suppression growth and reason-code breakdown

Agent context

Analytics provides real-time insight into your sending behavior and contact engagement. Use it to make data-driven sending decisions and avoid over-mailing.

Fatigue-aware sending (check before every send)

molted analytics fatigue --contact alice@example.com
# → {
#     "contactEmail": "alice@example.com",
#     "fatigueScore": 10,
#     "factors": { "sendFrequency": 2, "bounceCount": 0, "complaintCount": 0,
#                  "replyRate": 0.3, "daysSinceLastEngagement": 3 },
#     "recommendation": "safe_to_send"
#   }

Response fields:
contactEmail - the contact being scored
fatigueScore - 0 (fresh) to 100 (highly fatigued) factors - inputs used to compute the score: sendFrequency is the
sends to this contact in the last 7 days;
daysSinceLastEngagement is null if they never replied recommendation - safe_to_send (score < 40) | reduce_frequency (40-69) |
stop_sending (70+)

Recommendations:
safe_to_send - proceed normally
reduce_frequency - consider delaying or reducing send volume stop_sending - do not send; contact is fatigued

Send velocity (throughput monitoring)

molted analytics velocity
# → { "tenantId": "tenant_abc123", "lastHour": 12, "last24Hours": 156,
#     "last7Days": 892, "hourlyTrend": [{ "hour": "2026-04-10 08:00:00+00", "count": 5 }, ...] }

Deliverability metrics

molted analytics deliverability --period 7d
# → { "tenantId": "tenant_abc123", "period": "7d", "totalSent": 962,
#     "delivered": 950, "bounced": 10, "complained": 2,
#     "deliveryRate": 0.987, "bounceRate": 0.0104, "complaintRate": 0.0021,
#     "hasData": true }
# hasData is false when totalSent is 0 for the period -- the rates are 0 too,
# but that means "nothing sent yet", not a perfect score.
# Periods: 24h, 7d, 30d

Check if a contact is in a segment

molted analytics segment-check --contact alice@example.com --segment <segmentId>
# → { "isMember": true, "evaluatedLive": true }
# The segment's filters run live against the contact's current data, not a
# membership snapshot (evaluatedLive is always true). An address with no
# contact is not a member. This check sees name and ownerEmail as empty and
# no behavioral events, so filters on those can disagree with segments compute.

Policy decision breakdown (what the send policy blocked, and why)

molted analytics policy-decisions --period 7d
# → { "period": "7d", "totalAllowed": 900, "totalBlocked": 42,
#     "blockRate": 0.045, "hasData": true,
#     "blocksByReason": [{ "reason": "hourly_limit_exceeded", "count": 20 }, ...],
#     "dailyTrend": [{ "day": "2026-09-20", "reason": "hourly_limit_exceeded", "count": 3 }, ...] }
# hasData is false when there were no policy decisions in the period -- blockRate
# is 0 too, but that means "no data", not "nothing was blocked".
# Periods: 24h, 7d, 30d (default 7d)

Suppression breakdown (growth and reasons)

molted analytics suppressions --period 7d
# → { "period": "7d", "totalActive": 340, "suppressedDomains": 4,
#     "byReasonCode": [{ "reasonCode": "hard_bounce", "count": 120 }, ...],
#     "dailyGrowth": [{ "day": "2026-09-20", "count": 5 }, ...] }
# Periods: 24h, 7d, 30d (default 7d)

Recommended pre-send pattern

molted analytics fatigue --contact <email> # check fatigue
molted budget # check quota
molted send simulate --to <email> --template <t> # dry-run
molted send ... # send if all clear

Commands

molted analytics fatigue

Check contact fatigue score

molted analytics fatigue [options]

Option	Description	Default
`--contact <email>`	Contact email address

molted analytics velocity

Check send velocity metrics

molted analytics velocity

molted analytics deliverability

Check deliverability metrics

molted analytics deliverability [options]

Option	Description	Default
`--period <period>`	Time period: 24h, 7d, or 30d	`7d`

molted analytics segment-check

Check if a contact belongs to a segment

molted analytics segment-check [options]

Option	Description	Default
`--contact <email>`	Contact email address
`--segment <id>`	Segment ID

molted analytics policy-decisions

Breakdown of allowed/blocked policy decisions

molted analytics policy-decisions [options]

Option	Description	Default
`--period <period>`	Time period (one of: 24h, 7d, 30d)	`7d`

molted analytics suppressions

Suppression growth and reason-code breakdown

molted analytics suppressions [options]

Option	Description	Default
`--period <period>`	Time period (one of: 24h, 7d, 30d)	`7d`

See CLI overview for global options, credentials and output format.

On this page