[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)

# Weekly Mautic email performance report

> Read opens, click-throughs, bounces and top links for each Mautic email and get one weekly summary, without opening every email page by hand.

Source: https://cotlet.dev/integrations/mautic-api-mcp-server/weekly-email-report

Every Monday you want to know how last week's emails did, and Mautic shows the numbers one email at a time.

Cotlet does it in your own Mautic account with list\_emails and get\_email\_stats, called by your AI agent, an n8n workflow or a script.

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

Hosted · nothing to install or maintain

## Can Mautic do this on its own?

Mautic shows these numbers on each email's detail view (checked 23 Oct 2026) and has no weekly summary across emails. The REST API is off by default and needs OAuth2 or basic auth first, so a script still has to build the report itself.

## How you do it in Mautic today

1. Open the email's detail view and read the Email overview for opens, bounces and click-throughs.
2. Scroll to the bottom of the detail view and open the Click Counts tab to see which links were clicked.
3. Repeat for each email you sent, and copy the numbers into your own sheet.
4. Bounces appear only if bounce detection is set up, through IMAP monitoring or the webhook at /mailer/callback on your Mautic address.

## How to weekly Mautic email performance report

Prompt

```
Every Monday, report opens, click-throughs and bounces for each segment email sent last week, and the most clicked link of each.
```

1. 01  
### Pick last week's emails  
list\_emails gives the emails with their type and published state. The agent keeps segment emails, because those are the broadcasts, and leaves out template emails, whose stats mix campaign sends.
2. 02  
### Read the numbers  
get\_email\_stats runs once per email. The agent reads opens, click-throughs, bounces and the link with the most clicks, and keeps the numbers as Mautic returns them.
3. 03  
### Mark what to distrust  
The agent adds a note when an email has no bounces recorded, since that can mean bounce detection is off, and states that opens come from a tracking pixel Mautic itself calls not very accurate.
4. 04  
### Compare with the week before  
If you keep the last report in the chat or in a file, the agent compares click-throughs per email and names the largest change.

### What you get back

Example data

```
Segment emails sent last week: 1
October newsletter: 614 opens, 87 click-throughs, 9 bounces
Top link: https://example.com/webinar (52 clicks)
Note: opens are tracked with a pixel and undercount some readers
```

### Other ways to ask

- Compare click-throughs of the last three newsletters and name the best subject line.
- List emails whose bounces are above 2 percent of opens, and tell me which segment they went to.
- Report only the links clicked in the Webinar reminder email.

## What Mautic allows, and what to know first

- Mautic tracks opens with a 1-pixel GIF placed before the closing body tag, and the Mautic documentation calls open tracking not very accurate.
- Mautic shows clicks under the Click Counts tab at the bottom of each email's detail view, and does not count clicks on the Send Example link, direct sends from a contact profile or form preview emails.
- A segment email reaches each contact once, like a mailing list, and a template email can reach the same contact more than once.
- Mautic does not track stats of a template email sent directly to a contact against the original template, because it clones the content for that send.
- Mautic detects bounces through IMAP monitoring or the webhook at /mailer/callback.

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

Sources: [Mautic Documentation: Emails](https://docs.mautic.org/en/5.x/channels/emails.html)

## Call get\_email\_stats from a script

curl

```
curl https://cotlet.dev/api/v1/mautic/emails/58/stats \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"email_id": 58,
"name": "October newsletter",
"opens": 614,
"click_throughs": 87,
"bounces": 9,
"clicks_by_link": [
{
"url": "https://example.com/webinar",
"clicks": 52
},
{
"url": "https://example.com/pricing",
"clicks": 35
}
]
}
```

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

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

## Mautic tools this automation uses

__Cotlet Mautic tools used to weekly Mautic email performance report__
| Tool | Parameters |
| ----------------- | ---------- |
| list\_emails | none |
| get\_email\_stats | email\_id |

[All 15 Mautic tools with descriptions](https://cotlet.dev/integrations/mautic-api-mcp-server.md#tools)

## Frequently asked questions

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

Yes. You sign in to Mautic yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Mautic 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 Mautic automations

- [Merge duplicate Mautic contacts](https://cotlet.dev/integrations/mautic-api-mcp-server/merge-duplicate-contacts.md)
- [Add Mautic contacts to segments in bulk](https://cotlet.dev/integrations/mautic-api-mcp-server/add-contacts-to-segments.md)
- [Mautic API and MCP server: every tool](https://cotlet.dev/integrations/mautic-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Mautic.

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

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

---

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.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

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.