[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Get a weekly Plausible traffic report from your agent

> An agent reads each Plausible dashboard every Monday, compares it with the week before and sends one short report. No Business plan needed.

Source: https://cotlet.dev/integrations/plausible-api-mcp-server/weekly-traffic-report

Every Monday you open each Plausible site, switch the date picker to last week, turn on the comparison and copy the numbers somewhere you can read them together.

Cotlet does it in your own Plausible account with list\_sites, get\_site\_stats, get\_top\_pages, get\_sources and get\_goal\_conversions, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=plausible) [All Plausible tools](https://cotlet.dev/integrations/plausible-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Plausible do this on its own?

Plausible's Stats API can return these numbers, but it is a Business plan feature (checked 22 Oct 2026). Plausible's own email reports go out weekly on Monday or monthly on the first, with the stats embedded in the email. They do not compare sites or add your commentary.

## How you do it in Plausible today

1. On the Sites page, the admin opens a site and sets the date picker to last week.
2. The admin picks Compare in the date picker, or presses X, and chooses previous period.
3. The admin reads the Top Graph for visitors, visits, pageviews, views per visit, bounce rate and visit duration.
4. The admin scrolls to Sources, Top Pages and the Goals tab, noting the top rows of each.
5. The admin repeats this for every site and pastes the numbers into a message or a sheet.

## How to get a weekly Plausible traffic report from your agent

Prompt

```
Every Monday, report visitors and pageviews for each of my Plausible sites for last week against the week before, with the top 3 pages, the top 3 sources and goal conversions.
```

1. 01  
### Fix the week  
The agent works out last Monday to Sunday from the date it runs and passes the same from and to to every site, so all sites in the report cover identical days. It never uses a range that ends today, since the current day is incomplete.
2. 02  
### Walk the sites  
list\_sites gives the sites on your team. Every site is read, including a quiet one, so a site that dropped to near zero shows up as a drop and is not skipped.
3. 03  
### Read the numbers with a comparison  
get\_site\_stats runs per site with compare set to previous\_period, and the agent flags a site whose visitors moved by 20 percent or more in either direction, a threshold you can change in your prompt.
4. 04  
### Read what moved  
For flagged sites, get\_top\_pages and get\_sources are read for the same week, so the report says which page or channel is behind the change. For quiet sites they are skipped to keep the report short.
5. 05  
### Add conversions  
get\_goal\_conversions is read for sites with goals. A site with goals set up but none shown is reported as having no conversions, because Plausible lists a goal only after its first conversion.

### What you get back

Example data

```
12 to 18 Oct, against 5 to 11 Oct
acme-shop.example: 4,210 visitors (+8%), 9,120 pageviews
- Top page: /pricing, 1,180 visitors
- Top source: Organic Search, 1,480 visitors
- Checkout complete: 212 visitors, 5.0% conversion rate
blog.acme-shop.example: no change worth flagging
```

### Other ways to ask

- Do the same report for the month so far against the previous month, every first of the month.
- Only report sites whose visitors changed by more than 15 percent.
- Add a site note on the day the biggest change started.

## What Plausible allows, and what to know first

- The Plausible date picker offers a comparison against the previous period, the same period a year earlier or a custom period, and lets you match the day of the week.
- The Top Graph of the dashboard shows unique visitors, visits, pageviews, views per visit, bounce rate and visit duration.
- A dotted line in the Plausible chart marks the current, incomplete period.
- The Sources report has a Campaigns tab with UTM data by Medium, Source, Campaign, Term and Content.
- Plausible's Stats API allows 600 requests per hour by default and is a Business plan feature.

Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.

Sources: [Plausible Docs: Stats Dashboard guided tour](https://plausible.io/docs/guided-tour) · [Plausible Docs: Email reports](https://plausible.io/docs/email-reports) · [Plausible Docs: Stats API](https://plausible.io/docs/stats-api) · [Plausible Docs: The Sites page](https://plausible.io/docs/landing-page)

## Call get\_site\_stats from a script

curl

```
curl "https://cotlet.dev/api/v1/plausible/site-stats?site=acme-shop.example&from=2026-10-12&to=2026-10-18&compare=previous_period" \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"site": "acme-shop.example",
"from": "2026-10-12",
"to": "2026-10-18",
"visitors": 4210,
"visits": 5033,
"pageviews": 9120,
"views_per_visit": 1.81,
"bounce_rate": "58%",
"visit_duration": "1m 34s",
"compared_to": {
"from": "2026-10-05",
"to": "2026-10-11",
"visitors": 3890,
"pageviews": 8410
},
"visitors_change": "+8%"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is plausible\_read → get\_site\_stats. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/plausible-api-mcp-server.md#automations)

## Plausible tools this automation uses

__Cotlet Plausible tools used to get a weekly Plausible traffic report from your agent__
| Tool | Parameters |
| ---------------------- | --------------------------- |
| list\_sites | team |
| get\_site\_stats | site, from, to, compare |
| get\_top\_pages | site, view, from, to, limit |
| get\_sources | site, view, from, to |
| get\_goal\_conversions | site, from, to, goal |

[All 14 Plausible tools with descriptions](https://cotlet.dev/integrations/plausible-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Plausible to Cotlet?

Yes. You sign in to Plausible yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Plausible once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Plausible automations

- [Set up a new Plausible site with goals](https://cotlet.dev/integrations/plausible-api-mcp-server/set-up-new-site-goals.md)
- [Share a Plausible dashboard with a client](https://cotlet.dev/integrations/plausible-api-mcp-server/share-client-dashboard.md)
- [Plausible API and MCP server: every tool](https://cotlet.dev/integrations/plausible-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Plausible.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Plausible.

[Sign up free](https://cotlet.dev/app/signup?app=plausible)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.