---
title: "Results: 1Post docs"
url: "https://get1post.com/docs/analytics.md"
canonical_url: "https://get1post.com/docs/analytics"
last_updated: "2026-10-26"
type: "reference"
summary: "How 1Post collects each post's results at checkpoints, what the summary shows and how long results are kept for each plan."
related: ["https://get1post.com/tools/best-time-to-post.md", "https://get1post.com/tools/engagement-rate-calculator.md", "https://get1post.com/docs/api.md", "https://get1post.com/docs.md"]
---

# Results: 1Post docs

How 1Post collects each post's results at checkpoints, what the summary shows and how long results are kept for each plan.

After a post publishes, 1Post collects its results at a set number of checkpoints and stores each snapshot. The summary shows totals per network, your best posts and each account compared with the previous period. Reads use stored snapshots only; nothing is fetched from a network on demand.

## What you get

- GET /v1/analytics/summary: totals per platform, the best posts and account cards against the previous period.
- GET /v1/posts/{id}/analytics: the stored snapshots of each destination.

## By plan

| Plan | Checkpoints per post | Results window |
| --- | --- | --- |
| Starter | 4 | 30 days |
| Creator | 18 | 30 days |
| Agency | 20 | 90 days |

## Questions

**Why do results lag the network?**

Results are read at checkpoints, not live, so a number can trail what the network shows by a few hours.

## Related

- [Free best time to post calculator from your data](https://get1post.com/tools/best-time-to-post.md)
- [Free engagement rate calculator for social posts](https://get1post.com/tools/engagement-rate-calculator.md)
- [1Post API reference: every route, key and role](https://get1post.com/docs/api.md)
- [1Post docs: composer, scheduling, API, webhooks, MCP](https://get1post.com/docs.md)