# Amplitude: track event

The **Amplitude: track event** Point template sends one event to an Amplitude project through the [HTTP API V2](https://amplitude.com/docs/apis/analytics/http-v2), with the properties you list.

Pushwoosh sets Amplitude's `insert_id` for you from the traveler and this step, so the same traveler passing through this exact point twice — for example on a second lap of a looping journey — lands as one deduplicated event in Amplitude, not two.

## Configure the point

1. Drag **Amplitude: track event** from the **Integrations** section onto the canvas.
2. Double-click the point and enter a **Step Name**.
3. In **API key**, enter the project API key from Amplitude: **Settings > Projects > your project > General**. It's stored masked, like a webhook secret header — Pushwoosh never displays or returns it once saved, and it never appears in the point's stored request or in the [Calls log](/product/customer-journey/journey-elements/channels/webhook/#calls-log).
4. In **Amplitude endpoint**, pick the region the Amplitude project was created in: `api2.amplitude.com` for a US project, `api.eu.amplitude.com` for an EU one. A key from one region is rejected by the other.
5. In **Event name**, enter the event as it should appear in Amplitude, for example `journey_welcome_push_sent`. It takes the same macros as **Event properties**.
6. In **Event properties**, add the property name mapped to the value to send — see [key/value fields](/product/customer-journey/journey-elements/integrations/#configuring-list-and-keyvalue-fields). A value that's a single macro keeps its own type in Amplitude (`{{tag:Age}}` arrives as a number, `{{tag:Trial Ends}}` as a date); any other text is sent as a string.
7. Click **Save**.

## Response

After the step runs, the number of events Amplitude ingested is available in later steps as attribute **`amplitude_events_ingested`** — use it the same way you'd use a [Webhook response attribute](/product/customer-journey/journey-elements/channels/webhook/#map-webhook-response-data-to-variables).

A failed request drops the traveler from the journey — see [Errors and failed requests](/product/customer-journey/journey-elements/integrations/#errors-and-failed-requests).