Usage logs

Usage logs record all operations across your Organization, including free activity, and show how many AI Tokens each activity consumes. Use them to understand costs, analyze access, and investigate security. Open Settings → Usage to review activity from the last 24 hours, 7 days, or 14 days.

The page opens with the last 7 days selected and all usage pools except Free selected. Select one or more values in Usage type, Specific usage, and Usage pool to filter activity. Add Free to include operations that do not consume AI Tokens. Select the All option in a filter to include all its values. Filters and the chart grouping are saved in the URL, so you can bookmark or share a view.

All dates and times on the Usage page are shown in UTC.

The token overview shows your remaining plan and prepaid AI Tokens, your extra token spend for the current billing period, and your monthly spending limit. Select Manage AI Tokens to open Organization settings. This overview uses your current billing period and does not change with the activity filters.

Use the stacked chart to see how usage changes over time. Group by Usage type, Specific usage, Usage pool, or Used by, and hover over the chart to see token amounts. The last 24 hours use hourly intervals; longer periods use daily intervals. Chart times are in UTC. When there are many groups, the chart combines smaller groups as Other.

Below the chart, switch between Usage log and Summary. The log identifies the time, user, usage type, specific activity, usage pool, and AI Tokens used. The summary shows token totals, entry counts, and each group’s share of tokens for every entry matching the filters. Its grouping follows the chart. Free activity appears with zero tokens when the pool filter includes Free.

New entries can take a few minutes to appear because usage is processed asynchronously. To request usage data older than 14 days, use the contact form linked above the filters.

Use Export CSV to download all rows matching the current filters. The export includes the complete stored usage record, including detailed metadata, rather than only the columns visible in the table.

Review access changes

Access changes appear as Settings activity in the Free usage pool with zero AI Tokens. Select Settings in Usage type and include Free in Usage pool to find them. These entries cover roles and assignments, account and resource access, Groups, Service accounts and their keys, user membership and status, and activation of advanced permissions.

Expand an entry's summary in the Usage log to compare Before and After values. The entry identifies the changed item and who made the change. Key changes record settings such as the name, status, and expiry, without recording the key's secret value.

Rejected changes and saves that leave the settings unchanged do not create access-change entries. These entries appear after a successful change and may take a few minutes to reach the Usage log.

Identify Action and Export requests

New Action and Export entries created through the REST API or MCP identify the caller in usageDetails.actor. This includes the user or Service account ID, kind, and name. User entries also retain the email address. usedBy contains the caller ID, including Service account IDs. Service accounts do not have an email address.

usageDetails.credential identifies whether the request used an API key, MCP key, or OAuth. Key entries include the key ID and name, without its secret. These details reflect the caller and key when the request was made. They are also included in free Action and Export status reads and lists.

Charged Export entries include the source, selected accounts and columns, date range, grouping, aggregations, sorting, pagination, output type, and row count. Compare requestHash to find requests with the same recorded export settings. filtersHash and havingHash let you compare filters without storing their values in the usage log. reusedExportId identifies a cached export used to produce the result. Cache reuse still consumes the usual AI Tokens.

Action starts include the Action type, account, read or write access mode, and item count. Usage logs do not copy Action request payloads or results. Older entries and jobs queued before this change may lack these details. Scheduled Exports do not inherit the caller or key that created the schedule.

REST API

You can also retrieve usage logs through the REST API with GET /api/v1/usage-logs. The endpoint uses your datadoe-api-key and returns only logs for that key's Organization.

Use page and pageSize for pagination, and optionally filter by usedAtFrom, usedAtTo, usageTypes, usagePools, and specificUsageTypes. Date ranges are limited to the most recent 14 days; without dates, the endpoint returns the previous 24 hours.

Each response row includes usage details and actor fields where available. Access-change entries include the actor's kind and ID in usageDetails.actor, with the previous and new settings in usageDetails.before and usageDetails.after. User activity includes usedBy and usedByEmail when available. Other system or background activity may have null actor fields. Amazon Marketing Cloud MCP calls are attributed to the signed-in user, and API-key calls to the Organization owner.

See the DataDoe API docs (opens in a new tab) for the complete request and response schema.

If an entry looks incorrect, use the support link below the usage table to contact the DataDoe team.