# Understand analytics and transactions

Analytics and transaction history help you improve results and manage finances responsibly.

## What to monitor weekly

Key signals:

* Profile visits
* Update engagement patterns
* Link-sharing impact
* Contribution and sponsorship conversion trends

## What to monitor monthly

* Revenue by funding model (one-off, recurring, sponsorship)
* Retention trends for recurring support
* Tier performance and uptake
* Sponsorship pipeline progression

## Transaction hygiene

Review transactions regularly to:

* Track incoming support
* Reconcile expected vs actual amounts
* Spot delays and exceptions early

## Connect insights to action

Use this loop:

1. Publish updates and share profile
2. Review analytics and conversion
3. Improve offers and messaging
4. Repeat with small weekly improvements

## Troubleshooting

### Traffic is rising but revenue is flat

* Improve sponsorship tier clarity
* Add stronger calls to action on profile and updates
* Share progress-linked funding asks

### Revenue is inconsistent month to month

* Build recurring support options
* Improve posting consistency
* Strengthen sponsor follow-up and reporting

## FAQ

### Which metric matters most?

There is no single metric. Track the full journey from visibility to conversion to retention.

### How often should I review transactions?

Weekly for active profiles, and after major campaign or race periods.

## Next steps

* [Pricing](/reference-guides/pricing.md)
* [Receiving payouts](/reference-guides/receiving-payouts.md)
* [Troubleshooting index](/troubleshooting/troubleshooting.md)


---

# Agent Instructions: 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.sponsordriven.com/reference-guides/analytics-and-transactions.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.