> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/general/dashboard-and-analytics/google-analytics-4.md).

# Google Analytics 4

Google unveiled its first measurement tool, Urchin from Google, in 2005. Google followed this up with Google Analytics (or Google Analytics Classic) in 2007 and in 2012, Universal Analytics was released. So it was no great shock to the DoctorLogic team to learn that Google was again upgrading its measurement tools to Google Analytics 4 (GA4).

What does this mean for DoctorLogic clients, exactly? Rest assured, we are fully prepared for this change and ensuring that our clients' performance metrics and reporting are ready for this change. 

### To read more about this upcoming adjustment, click here to visit our blog posts: 

<https://doctorlogic.com/blog/doctorlogic-future-forward-approach-to-google-analytics-4>

<https://doctorlogic.com/blog/doctorlogic-paves-the-way-to-google-analytics-4>

<br>


---

# 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://help.doctorlogic.com/docs/general/dashboard-and-analytics/google-analytics-4.md?ask=<question>&goal=<user_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.