> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/amplitude/configuration.md).

# Configuration

With the basic onboarding complete, let’s go through the form fields and their usage. Since the API Key was already provided during onboarding, we’ll skip that step.\
\
Now we need to select the server where your project resides in.

### **Amplitude Servers**

#### **Standard Server**

* Hosted on **U.S.–based infrastructure**.
* Project accessible at **`app.amplitude.com`**.
* API endpoint: **`https://api2.amplitude.com/2/httpapi`**.
* Data is stored in the U.S. and may be subject to U.S. laws (e.g., CLOUD Act).
* Default option in most integrations unless otherwise specified.

By looking at the url of the project window, we can decide the server,

<figure><img src="https://app.edgetag.io/assets/images/docs/amplitude/standard-server.png" alt=""><figcaption></figcaption></figure>

***

#### **EU Server**

* Hosted entirely within the **European Union (e.g., Frankfurt)**.
* Project accessible at **`app.eu.amplitude.com`**.
* API endpoint: **`https://api.eu.amplitude.com/2/httpapi`**.
* Ensures **all data stays within the EU**, providing stronger GDPR alignment and data sovereignty.
* Must be explicitly selected when setting up integrations.

By looking at the url of the project window, we can decide the server,

<figure><img src="https://app.edgetag.io/assets/images/docs/amplitude/eu-server.png" alt=""><figcaption></figcaption></figure>

Based on your server url, select the **Sever** in Edgetag,

<figure><img src="/files/yqRDYijQvF8Xls4MXfo0" alt=""><figcaption></figcaption></figure>


---

# 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.edgetag.io/channels/amplitude/configuration.md?ask=<question>&goal=<endgoal>
```

`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.