# sendings_links_stats (records)

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

This report allows you to get information about clicks in sendings.


## Fields

### loyalty_club_id

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

ID of loyalty club.

### source_id

| Type | Filterable | Can change? |
| --- | --- | --- |
| String | <Icon icon="material-outline-done"/> | <Icon icon="material-outline-highlight_off"/> |

Source_id defines from which place the sending was sent.

It can take two forms:

| Form | What is it? | When? |
| --- | --- | --- |
| stringified number | `reporting_id` of sending | Always when `reporting_id` is present on sending. It's always set e.g. in campaign or triggered sendings. |
| text value | service_type of sending | When `reporting_id` is empty |

### visits_count

| Type | Filterable | Can change? |
| --- | --- | --- |
| Integer | <Icon icon="material-outline-highlight_off"/> | <Icon icon="material-outline-done"/> |

Number of how many times link was resolved.

Visits done by bots are not included.

### unique_visits_count

| Type | Filterable | Can change? |
| --- | --- | --- |
| Integer | <Icon icon="material-outline-highlight_off"/> | <Icon icon="material-outline-done"/> |

Number of how many members visited the link.

Visits done by bots are not included.


## Query without aggregations

Query returns list of sendings.

```json
{
    "records": [
        {
            "loyalty_club_id": 42,
            "source_id": "7385",
            "visits_count": 1516,
            "unique_visits_count": 1276
        }
    ],
    "pagination": {
        "next_page_info": "KgkRAAAAAACgcUA"
    },
    "result_type": "records"
}
```