Activity Log

Go to Settings > Activity Log.

The page displays two sections:

• Statistics cards summarizing activity over the last 30 days
• Filterable event list showing individual actions in reverse chronological order

Four cards at the top give you a snapshot of the past 30 days:

Use the API vs. web breakdown to understand how much of your organization's activity comes from integrations versus manual work.

Six filters are available to narrow down the event list:

Filter by the type of operation:

• Login - user sign-in events
• Create - new records (contacts, surveys, sequences, etc.)
• Update - modifications to existing records
• Delete - record removals
• Export - data export operations

Filter by what was affected:

• Survey - survey creation, edits, deletion
• Contact - contact record changes
• Sequence - automation sequence changes
• Response - survey response actions
• User - team member account changes
• Settings - organization setting modifications

• Success - action completed without errors
• Failed - action encountered an error (error message shown in the log entry)

• API - actions triggered through API keys
• Web - actions performed in the dashboard UI

Use the start and end date pickers to view activity within a specific window. Useful for investigating incidents or reviewing changes made during a particular period.

Click Reset Filters to clear all active filters and return to the full event list.

Each event in the log shows:

• Timestamp - date and exact time (HH:MM:SS)
• Action badge - color-coded by type (green for create, blue for update, red for delete, purple for login)
• Resource type - what was affected
• API badge - appears when the action came through an API key
• Status badge - green checkmark for success, red alert for failed
• User attribution - name and email of the team member, or API key name for automated actions
• Request details - HTTP method and path for API requests
• IP address - the originating IP address
• Error message - displayed for failed actions, helps with debugging

Results are displayed 50 per page. Use the Previous/Next buttons at the bottom to navigate through older events. The total result count is shown above the list.

Filter by Action: Login and Status: Failed to detect unauthorized access attempts. Review IP addresses to identify suspicious patterns.

Filter by Source: API to see all actions performed through API keys. Combine with the resource type filter to monitor specific integration activity.

Use the date range filter to narrow down when a specific change occurred. Filter by resource type to find who modified a particular survey, contact, or setting.

API requests show the API key name, making it easy to see which integration performed each action. Failed API actions can indicate configuration issues with connected services.

If the log is empty with active filters, try resetting all filters. If still empty, no actions have been recorded yet for your organization.

Failed events include an error message explaining what went wrong. Common causes include permission issues, invalid data, or rate limits on API requests.

The activity log captures actions processed through the application. Direct database changes or actions from external systems that bypass the API are not logged.

• Team Management
• API Keys
• Organization Settings