> For the complete documentation index, see [llms.txt](https://docs.candyblinks.fun/candyblinks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candyblinks.fun/candyblinks/creators/key-metrics-for-success.md).

# Key Metrics for Success

### Blink Engagement Rate

* Measure how often Blinks are clicked, shared, and interacted with across platforms. A high engagement rate indicates successful campaign distribution and audience interest.

### Creator Retention Rate

* Track the percentage of creators who return to use the launchpad for additional NFT collections. High retention reflects satisfaction with the platform and its tools.

### Engagement and Adoption in the CandyBlinks Ecosystem:

* Assess how Blinks drive traffic and participation by tracking how many users mint directly from Blinks and engage with campaigns distributed across platforms like X and Discord.

### Creator and Collector Satisfaction:

* Collect feedback from creators and collectors to ensure the platform meets their expectations and continues to innovate.

### Platform Uptime and Reliability

* Track technical performance metrics like server uptime, transaction success rates, and Blink generation speeds. A reliable platform builds trust with creators and collectors.


---

# 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:

```
GET https://docs.candyblinks.fun/candyblinks/creators/key-metrics-for-success.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.