# Amplitude: set user properties

The **Amplitude: set user properties** Point template updates the Amplitude user profile of the traveler with the properties you list, through the [HTTP API V2](https://amplitude.com/docs/apis/analytics/http-v2)'s `$identify` operation — so segmentation and cohorts on the Amplitude side see the same data as Pushwoosh.

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 — updates the same Amplitude profile instead of writing a duplicate identify event.

## Configure the point

1. Drag **Amplitude: set user properties** 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 **User properties**, add the property name mapped to the value to set — 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.
6. 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).