Activity Log
What is logged, how to use it for auditing and tracking changes
The Activity Log records all operations that you or your colleagues (via API keys) perform in the system. It is an audit tool — it helps understand who made changes and when, if something went wrong.
What Gets Logged
The log records the following types of operations:
| Category | Example Actions |
|---|---|
| Applications | Creating, editing, deleting an application |
| Push Templates | Creating, editing templates and translations |
| Schedulers | Creating, changing settings, activating, deactivating, archiving |
| Instant Sends | Launching an instant campaign |
| API Keys | Creating, rotating, deactivating a key |
| Push Packs | Creating, editing, publishing a push pack |
| Audience Groups | Creating and editing segments |
| App Groups | Creating and editing groups |
| Events | Creating, activating, deactivating custom events |
Log Entry Structure
For each log entry the following is displayed:
| Field | Description |
|---|---|
| Date and time | When the action was performed |
| Action | Operation type: create / update / delete / activate / archive |
| Resource type | What was changed (app, push, scheduler, api_key, ...) |
| Resource ID | Identifier of the specific object |
| IP address | Where the request came from (user's browser or server IP for API keys) |
Use Cases
Incident Investigation
If pushes stopped sending or scheduler settings changed — open the log and filter by resource type scheduler. You will see who made changes and when.
Change Auditing
If multiple people work with the same account via different API keys, the log lets you track every action — by IP address you can determine which service performed the operation.
Unauthorized Access Monitoring
If unfamiliar entries appear in the log from an unknown IP address — this is a signal to change the password and recreate API keys.
Configuration Recovery
If a setting was accidentally deleted or changed, the log will show exactly what changed — update with the previous resource state (by its ID) can be restored manually.
Relationship with API Keys
When using Scoped API Keys with project_id, the log only records activity related to that project's resources. This allows you to distinguish operations from different teams or services by the source request IP address.
More details on access management — in the API Keys section.
Log Filtering
In the dashboard, the log can be filtered by:
- Date and date range.
- Action type (create / update / delete / activate / archive).
- Resource type (app, push, scheduler, ...).
This simplifies finding the required entry when investigating a specific incident.