> 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-self-hosted/configuration/usage-tracking/tracking-activity-data-from-public-maps.md).
# Tracking Activity Data from Public Maps
Track activity data from public maps in CARTO Self-Hosted
CARTO supports tracking activity data from public maps, allowing administrators to measure the impact of their public maps by tracking interactions from unauthenticated visitors (e.g., views, exports, most active maps).
For more details, see the [announcement](https://docs.carto.com/whats-new#tracking-activity-data-from-public-maps).
This feature is **not enabled by default**. Enable it using the method that matches your deployment:
{% tabs %}
{% tab title="Kots" %}
Set the following setting in your config from the Admin Console:
{% endtab %}
{% tab title="Helm" %}
Add the following configuration in your `customizations.yaml` file:
```yaml
appConfigValues:
publicEventsApiEnabled: true
```
{% endtab %}
{% endtabs %}
You'll have to deploy the new changes to your environment to ensure that the new component handling the events triggered by your public maps is ready.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.carto.com/carto-self-hosted/configuration/usage-tracking/tracking-activity-data-from-public-maps.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
Set the following setting in your config from the Admin Console:
Add the following configuration in your `customizations.yaml` file:
```yaml
appConfigValues:
publicEventsApiEnabled: true
```
{% endtab %}
{% endtabs %}
You'll have to deploy the new changes to your environment to ensure that the new component handling the events triggered by your public maps is ready.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.carto.com/carto-self-hosted/configuration/usage-tracking/tracking-activity-data-from-public-maps.md?ask=