Audit Log Actions
What the audit log records, how to filter it, and what the action names mean.
The audit log keeps a record of important actions in your organization: who did what, on which resource, from which IP address and when. It is available on the Business plan. The API allows owners and admins to read it, and the menu entry (Audit Log in the user menu) is shown to owners.
Filtering
Owners and admins see an Activity per day chart above the table. Click a day to show only that day in the table, shift-click or drag to choose a range, or use the arrow keys, Enter and then Shift + Enter on another day. The category buttons below the chart filter the table by kind of action. You can also set From and To dates in the toolbar; days are UTC, both dates are included and the range can be at most 120 days. Use Clear filters to start over. The filters are kept in the page address, so you can bookmark or share a view.
Use Filter by action to show a single kind of event. The menu groups the actions as follows.
- Campaigns: created, sent, deleted, recurring enabled.
- Contacts and privacy: merged, unsuppressed, auto-suppressed, consent withdrawn, CSV export, data subject requests, GDPR deletion, CCPA opt-outs, processing restrictions and tracking opt-outs.
- Webhooks: created, updated, deleted and delivery replayed.
- API keys: created, revoked and locked.
- Organization: DPA accepted or reset, and changes to compliance, deliverability, preference center and open tracking settings, plus automatic locks and unlocks.
- Team invites: created, resent, revoked and accepted. An accepted invite is recorded against the organization that sent it.
- Domains: created, DNS rechecked, verified, deleted, and DMARC policy updated. “Verified” is only recorded when a domain changes to verified, not on every check.
- Billing: plan changed (from the app or through the Stripe customer portal), subscription started, cancellation requested, subscription canceled, seats added or removed, payment failed, and coupon changes.
- Account and sign-in: registration, account review, email verified, password changed, sign-in success and failure, sign-out, and two-factor authentication changes (turned on or off, recovery code used, failed code, recovery codes replaced).
- Deliverability: complaints and bounces recorded, transactional suppression bypassed and other security events.
Names you may see in exports and the API
Newer actions are written as resource.event, for example invite.created or domain.dns_rechecked. Some older actions use a flat name such as api_key_created or login_success. They keep their original name so existing entries and saved filters still match, and the API key actions appear in both forms in the filter.
What is not recorded
Removing a member or changing a member’s role is not available in the app today, so there is no audit action for it yet. A failure to write an audit entry never blocks the action itself.