Documentation
Sign inGet started

bird email stats by-mailbox-provider

Usage

Codebeispiel
bird email stats by-mailbox-provider [flags]

Description

Email delivery and engagement stats grouped by recipient mailbox provider (gmail, microsoft, yahoo, ...); covers the delivery stage onward, no accepted/processed counts. For a per-region split use email_stats_by_mailbox_provider_region; for exact destination domains use email_stats_by_recipient_domain.

Examples

Codebeispiel
bird email stats by-mailbox-provider

Options

NameDescription
--categoryNot supported on breakdown endpoints; supplying it returns 422. To compare categories use GET /v1/email/stats/categories; the summary, daily, and hourly statistics accept category as a filter.
--fromStart date (inclusive) in YYYY-MM-DD, interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to 30 days before to when omitted; with include_trend=true and trend_grain=hourly the default tightens to 29 days before to, keeping the defaulted window within the 720-hour trend cap.
--include-trendWhen true, each row also carries a trend array: a short per-bucket series of that provider's delivery and engagement rates over the window. Returned only when limit is 50 or fewer and the window is at most 90 days (trend_grain=daily) or 720 hours (trend_grain=hourly); a larger request returns 422. When from is omitted and trend_grain=hourly, the default window is 30 days (720 hours), so a request built entirely from defaults always fits the cap.
--limit <n>Maximum number of mailbox-provider rows to return, ranked by the sort field descending.
--response-schemaPrint the fields this command returns, then exit
--sortMetric to rank rows by, applied descending. Any count or rate in the response may be used; rows whose rate is undefined (zero denominator) sort last. Defaults to delivered. processed, rejected, and oob_bounces are not part of this breakdown's rows, so they are not sortable here.
--timezoneIANA timezone identifier (for example Asia/Kathmandu or America/New_York) to report the statistics in. It is the single source of timezone: day and hour boundaries, and the relative window defaults used when from and to are omitted, are computed in this timezone instead of UTC, so a timezone with a sub-hour offset (such as India at +05:30 or Nepal at +05:45) still gets correct local-day and local-hour totals. When it is set, a from or to given as a calendar day names a local day in this timezone, and one given as an instant stays an absolute point in time but is rounded down to its hour and bucketed in this timezone (so the hour boundaries are local, not UTC). To avoid specifying the zone twice, a from or to that carries its own numeric UTC offset (for example +05:45) is rejected when timezone is set; use a calendar day or a Z (UTC) instant instead. Defaults to UTC.
--toEnd date (inclusive) in YYYY-MM-DD, interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to today in that timezone when omitted. Window may not exceed 365 days.
--trend-grainBucket grain for the trend series. Has no effect unless include_trend=true.
NameDescription
bird email stats by-bounce-codeBounces by SMTP error code
bird email stats by-broadcastStats by broadcast
bird email stats by-categoryStats by category
bird email stats by-clientEngagement by email client
bird email stats by-complaint-typeComplaints by type
bird email stats by-locationEngagement by location
bird email stats by-mailbox-provider-regionStats by mailbox provider region
bird email stats by-recipient-domainStats by recipient domain
bird email stats by-sending-domainStats by sending domain
bird email stats by-sending-ipStats by sending IP
bird email stats by-tagStats by tag
bird email stats by-templateStats by template
bird email stats dailyDaily sending statistics
bird email stats hourlyHourly sending statistics
bird email stats summaryAggregate stats summary