> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/settings/activity-data/activity-data-changelog.md).

# Activity Data Changelog

{% hint style="success" %}
This page collects useful information about historical updates and fixes to the [Activity Data](/carto-user-manual/settings/activity-data.md) to help you understand the data. We will also make an effort to clarify event cutoff dates where applicable, so that you can reliably build metrics starting from said dates.
{% endhint %}

{% updates %}
{% update date="2026-06-03" %}

## June 3rd, 2026

* **AI event schema unified.** The events emitted by CARTO's AI features (Builder AI Agents, the AI Assistant in Data Observatory, and the Agent Config Assistant) have been restructured. This is a **breaking change** to historical event names — past activity data keeps the old names, and new activity data uses the new names from this date onwards. If you have dashboards filtering on these event types, update them accordingly.
  * **Renamed event types** (the `AIAgent` prefix has been dropped from events that track generic AI interactions; events that track changes to an AI Agent itself — `AIAgentCreated`, `AIAgentDeleted`, `AIAgentConfigurationChanged` — keep their names):
    * `AIAgentRequest` → `AIRequest`
    * `AIAgentResponse` → `AIResponse`
    * `AIAgentError` → `AIError`
    * `AIAgentToolInvoked` → `AIToolInvoked`
    * `AIAgentToolExecuted` → `AIToolExecuted`
    * `AIAgentConversationDeleted` → `AIConversationDeleted`
    * `AIAgentResponseStopped` → `AIResponseStopped`
    * `AIAgentFeedback` → `AIFeedback`
  * **Removed event type:** `AIAgentConversationStarted` is no longer emitted as a standalone event. To count new conversations, query `AIRequest` events where `isNewConversation = true` (a new field, see below).
  * **New required fields on every AI event:**
    * `userId` — the user who triggered the AI interaction.
    * `feature` — which AI feature emitted the event (e.g. Builder AI Agents, AI Assistant in Data Observatory, Agent Config Assistant).
    * `resource` — the related resource id (renamed from `mapId`). For Builder this is the map id; for other features, the corresponding resource.
  * **New `AIRequest` fields:** `isNewConversation` is set to `true` when the request opened a new conversation (use it to count new conversations now that `AIAgentConversationStarted` is gone). `mode` (`testing`/`live`) is now only included for Builder AI Agent requests; other AI features no longer carry a `mode` field.
  * **New `AIRequestGotOverquota` field:** `model`, identifying the model that the blocked request was targeting.
  * **New event types** are also being captured to give better visibility into the AI conversation UI: `AIChartRendered`, `AIToolResultExpanded`, `AIToolResultCollapsed`. See the [event reference](/carto-user-manual/settings/activity-data/activity-data-reference.md#event-reference) for details.
    {% endupdate %}

{% update date="2026-05-07" %}

## May 7th, 2026

* **New columns in API Usage:** the [API Usage](/carto-user-manual/settings/activity-data/activity-data-reference.md#api-usage) table now includes `map_id` and `workflow_id`, attributing each request to the specific Builder map or Workflow that produced it (when applicable). This gives admins full visibility into where their Usage Quota is going, making it easy to identify high-cost maps and workflows and tie consumption back to specific teams or projects. See the [API Usage schema](/carto-user-manual/settings/activity-data/activity-data-reference.md#api-usage) for details, and the [examples page](/carto-user-manual/settings/activity-data/activity-data-examples.md#sql-top-maps-and-workflows-by-usage-quota-consumed) for a SQL snippet to get you started.
  * Data is populated from *May 4th, 2026* onwards; rows before that date will have `NULL` in both columns.
    {% endupdate %}

{% update date="2026-02-06" %}

## February 6th, 2026

* **New events:** during the past months, we've progressively added these new events, covering new features: `AIAgentConfigurationChanged`, `AIAgentConversationDeleted`, `AIAgentConversationStarted`, `AIAgentCreated`, `AIAgentDeleted`, `AIAgentError`, `AIAgentFeedback`, `AIAgentRequest`, `AIAgentResponse`, `AIAgentResponseStopped`, `AIAgentsListed`, `AIAgentToolExecuted`, `AIAgentToolInvoked`, `AIConsumed`, `AIRequestGotOverquota`, `AppOwnershipTransferred`, `AppPrivacyChanged`, `ConnectionBookmarkCreated`, `ConnectionBookmarkDeleted`, `ConnectionOwnershipTransferred`, `ConnectionTransferred`, `CopyMapToken`, `CrossFilteringWidgetSettingsChanged`, `CustomAIModelAdded`, `CustomAIModelRemoved`, `CustomAIModelUpdated`, `ImportDropFileLoaded`, `LayerAggregateByGeometry`, `LayerMapListStatusChanged`, `LegendVisibilityChanged`, `MapCopyCoordinates`, `MapCreatedFromOldVersion`, `MapGetCoordinates`, `MapOwnershipTransferred`, `MapSelectedForAIAgentCreation`, `MapVersionCreated`, `MapVersionManagerOpened`, `MapVersionRestored`, `MapVersionUpdated`, `SettingsCartoAIDisabled`, `SettingsCartoAIEnabled`, `TokenOwnershipTransferred`, `WidgetAggregationUsed`, `WidgetFilteringInteraction`, `WorkflowLocked`, `WorkflowOwnershipTransferred`, `WorkflowUnlocked`, `WorkflowsExtensionFailed`, `WorkflowsMcpToolDisabled`, `WorkflowsMcpToolEnabled`
  {% endupdate %}

{% update date="2026-01-29" %}

## January 29th, 2026

* **Update — now events are always sent for public maps:** previously, [public maps](/carto-user-manual/maps/sharing-and-collaboration.md) wouldn't send all events related to their activity due to users not being authenticated. We have added an event pipeline for unauthenticated users, which allows you to track interactions such as `OpenBuilderMap` or `BuilderReportDownload` to understand how public maps are being used in your organization.
  * This update has been in place since *January 21st, 2026.*
    {% endupdate %}

{% update date="2024-12-16" %}

## December 16th, 2024

* **Update — now `OpenBuilderMap` is also sent for viewers:** you can now use that event to track how many of your authenticated users are *viewing* a map, not just editing it.
  * This update has been in place since *November 27th, 2024.*
* **New events:** during the past months, we've progressively added these new events, covering both existing and new features: `GroupDeleted`, `NamedSourceDeleted`, `ChangeDatasource`, `NamedSourceUpdated`, `NamedSourceCreated`, `TableWidgetInteraction`, `CartoAIFeedback`, `CartoAccessConsent`, `SpatialColumnTypeDefined`, `WorkflowTemplateCreated`, `WorkflowsTemplateExplored`, `ShowOnlyThis`, `ZoomToLayer`, `WorkflowsExtensionUninstalled`, `WorkflowsExtensionInstalled`
* Other minor payload changes and fixes.
  {% endupdate %}

{% update date="2024-08-30" %}

## **August 30th, 2024**

* **Activity Data was released:** read our full [announcement](/whats-new/q3-2024.md#monitor-whats-happening-in-your-carto-organization-with-the-new-activity-data) for details, and head over to the [Activity Data documentation](/carto-user-manual/settings/activity-data.md) for complete guides and technical reference.
  {% endupdate %}
  {% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carto.com/carto-user-manual/settings/activity-data/activity-data-changelog.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.