> For the complete documentation index, see [llms.txt](https://docs.subscripta.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subscripta.app/analytics-and-webcard/use-analytics.md).

# Use analytics

Analytics show how recipients engage with deployed signatures.

## Availability

| Plan     | Analytics    |
| -------- | ------------ |
| Free     | Not included |
| Pro      | 30 days      |
| Business | All time     |

## What Analytics Shows

* Total clicks
* Active signatures that generated engagement
* Top clicked link type
* Top performing signature
* Clicks by link type
* Top signatures
* Clicks by source, including email signature and WebCard
* Recent click activity

## Link Types

Analytics can group clicks by:

* Email
* Phone
* Website
* Social
* Banner
* QR code

## Time Filters

1. Open **Analytics**.
2. Choose **7d**, **30d**, or **All time**.

All-time analytics require Business.

## When Data Appears

Analytics appear after recipients click tracked links in saved and deployed signatures. Builder previews are not tracked until the signature is saved and exported with tracking.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.subscripta.app/analytics-and-webcard/use-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.