> For the complete documentation index, see [llms.txt](https://docs.gridbox.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridbox.io/integrations/setting-up-google-analytics.md).
# Setting up Google Analytics
If you'd like to track and analyze site traffic, you can optionally enable [Google Analytics](https://google.com/analytics) support by following these steps:
1. Log in to [Google Analytics](https://google.com/analytics) and obtain the site's **Measurement ID** or **Tracking ID** (per [these instructions](https://support.google.com/analytics/answer/9539598)). If you haven't already added the site to Google Analytics, you'll need to [set up a property](https://support.google.com/analytics/answer/9304153#property) for it first.
2. Back at Carrd, click on Publish & make sure that your site is live
3. From the top left, next to project title click on the settings icon
4. This will open the Project Settings Dialog
5. Under Google Analytics Tab
6. Set **Google Analytics ID** to the site's measurement ID (or tracking ID).
7. Click on Update
8. **You're done.**
---
# 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.gridbox.io/integrations/setting-up-google-analytics.md?ask=&goal=
```
`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.