> 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/extensions/google-analytics/how-to-create-an-external-ga4.md).

# How to Create an External GA4

If you choose to set up an external GA4 account to create custom event tracking, please provide the identifier to <support@doctorlogic.com> for us to add it to your website.&#x20;

1. Log into your Google Analytics Account
2. Click the Admin button
   1. In the *Account column*, make sure that your desired account is selected. (If you only have one Google Analytics account, it will already be selected.)
3. Click the blue "Create Property" button
4. Insert your property name and your practice's time zone
5. Set up your Data Stream
   1. Select "Web" and name the data stream
   2. Check the "Enhanced Measurement" option
   3. Click "Create Stream"&#x20;
6. Set up any desired custom conversion events
7. Click the "View Tag Instructions" button
   1. Select the "Install Manually" button
   2. Copy that information and paste it into an email to send to <support@doctorlogic.com>


---

# 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/extensions/google-analytics/how-to-create-an-external-ga4.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.
