# sendings_stats (statistics)

| Required permit | Rate limit tokens cost |
| --- | --- |
| Reporting:Api:Report:SendingsStats | 2 |

This report allows you to get statistics which are produced during sending.

It includes events which are common for each available channel.

## Fields

### loyalty_club_id

| Type | Filterable |
| --- | --- |
| Integer | <Icon icon="material-outline-done"/> (via `X-Customer` header) |

ID of loyalty club.

### event_type

| Type | Filterable |
| --- | --- |
| Enum | <Icon icon="material-outline-done"/> |

Type of sendings event.

This field is an enum, possible values are:

* new
* transmitted
* transiently_failed
* delivered
* opened
* opened_event
* failed
* delivery_errored

### channel

| Type | Filterable |
| --- | --- |
| Enum | Depends on aggregation |

Channel of sending.

This field is an enum, possible values are:
* sms
* email
* push

### service_type

| Type | Filterable |
| --- | --- |
| Enum | Depends on aggregation |

Sending's service type.

### campaign_id

| Type | Filterable |
| --- | --- |
| Integer | Depends on aggregation |

ID of campaign to which sending was scheduled.

### reporting_id

| Type | Filterable |
| --- | --- |
| Integer | Depends on aggregation |

Sending's reporting_id. This field can be used to attribute reported sending to its source.

## Query without aggregations

Query returns series with sending events labeled by `event_type`.

### Labels

| Key | Type | Description |
| --- | --- | --- |
| event_type | Enum | See in `Fields` |

## Aggregations

### service_type

#### Labels

| Key | Type | Description |
| --- | --- | --- |
| service_type | Enum | See in `Fields` |
| event_type | Enum | See in `Fields` |

:::note
There is also `total_service_type` aggregation which works the same way but removes loyalty_club_id from series when working on cross-customer data.
:::

### campaign_id

#### Labels

| Key | Type | Description |
| --- | --- | --- |
| campaign_id | Integer | See in `Fields` |
| event_type | Enum | See in `Fields` |

:::note
There is also `total_campaign_id` aggregation which works the same way but removes loyalty_club_id from series when working on cross-customer data.
:::

### channel

#### Labels

| Key | Type | Description |
| --- | --- | --- |
| channel | Enum | See in `Fields` |
| event_type | Enum | See in `Fields` |

:::note
There is also `total_channel` aggregation which works the same way but removes loyalty_club_id from series when working on cross-customer data.
:::

### reporting_id

#### Labels

| Key | Type | Description |
| --- | --- | --- |
| reporting_id | Integer | See in `Fields` |
| event_type | Enum | See in `Fields` |

:::note
There is also `total_reporting_id` aggregation which works the same way but removes loyalty_club_id from series when working on cross-customer data.
:::