Captures every mutation
Creates, edits, deletes, schedules, sends, and suppressions are all recorded — the full set of state changes on the account, not just sign-ins. If it changed something, it's in the log.
Account control
Every mutation across your account — create, edit, delete, schedule, send, suppress — is recorded with the actor, the source IP, the action, the target resource, and the timestamp. Filter by any of them to reconstruct exactly what happened.
Sent broadcast "Spring picks"
Created segment "Engaged 30d"
Suppressed [email protected]
Edited sending domain acme.example
What's recorded
Creates, edits, deletes, schedules, sends, and suppressions are all recorded — the full set of state changes on the account, not just sign-ins. If it changed something, it's in the log.
Each entry carries the actor — the account owner's session or a specific API token — plus the source IP, the action, the target resource, and the timestamp. Accountability traces to exactly who or what made the change.
Narrow the log by actor, action type, target resource, or time window to answer 'who changed this, and when' in seconds — and export the filtered slice to CSV for a review package.
When you reach for it
"What triggered that?" A campaign went out that shouldn't have. The log shows whether it came from the account session or a specific API key, from where, and exactly when — so you fix the cause, not just the symptom.
"What changed?" Deliverability dropped after someone edited a sending domain. Filter to that resource and you see every change made to it, by whom, in order.
"Prove it." A compliance or security review asks for an account history. Filter the window, export to CSV, and you have the evidence trail without reconstructing anything from memory.
What it prevents
A wrong send or a deleted list with no record is a mystery and a repeat risk. The log names the actor and the moment, so the cause is clear.
When deliverability shifts after a quiet settings change, an unlogged account leaves you guessing. Per-resource filtering shows exactly what changed.
A compliance or security review needs an evidence trail. Without one you scramble; with the log you filter and export.
When programmatic changes can't be told apart from manual ones, accountability evaporates. Each action is tagged with its actor — the account session or the specific API key behind it.
“A campaign went out one morning that we hadn't scheduled, and the log answered it in under a minute — it was a stale API key, not anyone on the team, firing from an IP we recognised. We rotated the key and moved on. Before, that would've been an afternoon of guesswork and finger-pointing.”
Verified review
Mumara ONE customer
Common questions
Every mutation on the account — creates, edits, deletes, schedules, sends, and suppressions — whether made in the dashboard or via the API. It's a record of state changes, not just login events.
The actor (the account session or an API token), the source IP address, the action performed, the target resource, and the timestamp — enough to reconstruct exactly what happened and what made the change.
Filter the log by actor, action type, target resource, or time window — alone or in combination — to narrow thousands of entries down to the handful you care about in seconds.
Yes. Filter to the slice you need and export to CSV — for a compliance package, a security investigation, or your own records.
Yes. Actions taken through the REST API are logged with the API key as the actor, so programmatic changes are as traceable as ones made in the interface.
Related
The activity log is the evidence trail a compliance review asks for.
Read moreAPI actions are logged with the key as the actor — programmatic changes stay traceable.
Read moreWhen a reputation rule fires an action, the log captures it alongside everything else.
Read moreMumara ONE · Activity Logs
Every change recorded with actor, IP, target, and timestamp — filterable in seconds and exportable for any review.