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

# Twitter analytics

**In short:** Twitter analytics show how your posts are actually doing, on real data pulled live from Twitter, with a written read from audenAI on what to do more of. Analytics are platform-aware, so a Twitter profile and a LinkedIn profile each get their own (this page covers Twitter; see LinkedIn analytics for that).

Open **Analytics** from the sidebar. On a Twitter profile it has four tabs: **Overview, Tweets, audenAI Intelligence, and Reports**.

### What the Overview shows

* **Headline numbers**: followers, impressions, engagement rate, and total engagements, each with a change versus the previous period.
* **Posting activity**: your posting streak against your daily goal.
* **Performance over time**: a trend, a heatmap, and your best times to post.
* **What works for you**: length, hooks, posts versus replies, and your top and bottom performers.
* **Engagement breakdown**: likes, replies, reposts, and bookmarks.

The **Tweets** tab is a sortable, filterable table of your posts with per-post metrics.

### Where the numbers come from

Twitter analytics are pulled live from the Twitter API, including the non-public metrics that match Twitter's own Creator Analytics for recent posts. VoiceMoat stores snapshots over time so it can show you real change, not just a single moment.

{% hint style="info" %}
When a profile is new to VoiceMoat, you may see a "building history" note while it gathers enough snapshots to show trends. This resolves on its own as history accumulates.
{% endhint %}

### Syncing

Analytics refresh on a schedule set by your plan, and you can sync within that window:

|               | Free          | Creator       | Pro           | Enterprise   |
| ------------- | ------------- | ------------- | ------------- | ------------ |
| Sync cadence  | not available | every 30 days | every 15 days | every 7 days |
| History range | 7 days        | 28 days       | 90 days       | all time     |

Between syncs you see your stored data, with a countdown to the next sync.

### Who can see what

The full analytics (deltas, charts, the Tweets table, the deeper breakdowns) are available on Creator and above. Free plans see a limited, blurred view. LinkedIn analytics have their own setup; see LinkedIn analytics.

### Common questions

**Is this the same as Twitter's own analytics?** For recent posts it uses the same non-public metrics Twitter shows creators, so the numbers line up. VoiceMoat adds history, a written read, and voice-aware suggestions on top.

**Where is voice-match tracking?** Voice match lives in Studio and Voice Lab, not Analytics. Analytics is about reach and engagement; voice match is about how closely a draft sounds like you.

**Why can't I sync more often?** Sync cadence is set per plan. Higher plans sync more frequently.


---

# 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.voicemoat.com/twitter-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.