Activity Data Changelog
This page collects useful information about historical updates and fixes to the Activity Data 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.
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
AIAgentprefix 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→AIRequestAIAgentResponse→AIResponseAIAgentError→AIErrorAIAgentToolInvoked→AIToolInvokedAIAgentToolExecuted→AIToolExecutedAIAgentConversationDeleted→AIConversationDeletedAIAgentResponseStopped→AIResponseStoppedAIAgentFeedback→AIFeedback
Removed event type:
AIAgentConversationStartedis no longer emitted as a standalone event. To count new conversations, queryAIRequestevents whereisNewConversation = 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 frommapId). For Builder this is the map id; for other features, the corresponding resource.
New
AIRequestfields:isNewConversationis set totruewhen the request opened a new conversation (use it to count new conversations now thatAIAgentConversationStartedis gone).mode(testing/live) is now only included for Builder AI Agent requests; other AI features no longer carry amodefield.New
AIRequestGotOverquotafield: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 for details.
May 7th, 2026
New columns in API Usage: the API Usage table now includes
map_idandworkflow_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 for details, and the examples page for a SQL snippet to get you started.Data is populated from May 4th, 2026 onwards; rows before that date will have
NULLin both columns.
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
January 29th, 2026
Update — now events are always sent for public maps: previously, public maps 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
OpenBuilderMaporBuilderReportDownloadto understand how public maps are being used in your organization.This update has been in place since January 21st, 2026.
December 16th, 2024
Update — now
OpenBuilderMapis 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,WorkflowsExtensionInstalledOther minor payload changes and fixes.
August 30th, 2024
Activity Data was released: read our full announcement for details, and head over to the Activity Data documentation for complete guides and technical reference.
Last updated
Was this helpful?
