Audit Log
The Audit Log is a chronological record of every action on your account: API calls, dashboard sends, Zapier triggers, webhook events, and logins.
Access the Audit Log
Click your name in the top right of the dashboard and choose Audit Log (Settings → Audit Log). It is the last item in the settings menu and is available from a sub-account as well as the main account.
Use the filter at the top to show one kind of entry: All, API Actions, AI Actions, Zapier Actions, Webhooks, Dashboard Logins, Dashboard Actions, or Dashboard Password Change. Each entry shows its type, date, and details. Use First, Previous, and Next to page through older entries.
What's recorded
| Event type | Includes |
|---|---|
| API requests | Endpoint, method, response status, validation errors |
| AI actions | Each change an AI assistant made through the thanks.io MCP server: the tool, which assistant or API key made it, the details it sent, and whether it succeeded |
| Dashboard actions | Sends, creative saves, list uploads, account setting changes, and deleted creatives and campaigns (deleting a mailing list logs each of its campaigns) |
| Webhook deliveries | Event type, target URL, response code, retry attempts |
| Zapier/Make/n8n triggers | Action taken, response status |
| Logins | Timestamp, IP, user agent |
Actions taken by AI assistants
When an AI assistant works on your account through the thanks.io MCP server, every change it makes is listed under AI Actions. The Agent line shows who made it:
- A connected AI app, such as Claude or ChatGPT, shown by the name the app registered when you connected it.
- An API key, shown by the name you gave the key under Settings → API Access.
Orders an assistant places this way show AI Agent in the Method column of your Orders list and as Triggered By on the order. They are priced and processed like API orders, and the API method filter includes them.
Assistants that use a browser
An AI assistant can also operate the dashboard in a web browser, for example through a browser extension. It is then signed in as you, so its actions are recorded as Dashboard Actions, the same as your own.
When the browser reports that it is automated, the entry adds Automated browser detected. Many AI browser tools don't report this, including extensions that run in your own browser. An entry without that line may still have been made by an assistant, so it doesn't prove a person made the change.
To keep a clear record of what an assistant does, connect it through the MCP server instead of letting it drive your browser.
When to use it
- Debug a failed API call - find the exact 422 validation errors returned.
- Verify a webhook fired - confirm the event was sent and see the response code from your endpoint.
- Audit user activity - review who did what and when for compliance or security review.
- Diagnose a campaign - confirm sends were triggered and orders were created.
- Confirm a setting change - account settings that affect what recipients see, such as the gift card redemption contact requirement, are logged when they are switched on or off.