Skip to main content

​
Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Amplitude connector page.

​
Register the StackOne webhook in Amplitude

This connector uses Manual Webhooks. You add StackOne’s Native Webhook URL as a Webhook destination in Amplitude Data. Amplitude sends no verification ping, so the destination is ready as soon as it is saved.

1

Retrieve StackOne Native Webhook URL

The Native Webhook URL is generated once an account has been linked. It identifies your linked account, so no other routing field is needed.

  • Open the linked account in StackOne.
  • Copy the value from Native Webhook URL.
2

Sign in to Amplitude

Sign in to your Amplitude account in the region your project lives in.

Amplitude sign-in page with the Work Email field highlighted
3

Open Destinations

In the left navigation, open Data and click Connect Destinations. On Destinations, click Add Destination.

Amplitude Destinations page with the Add Destination button highlighted
4

Select the Webhook destination

Type Webhook into Search and click the Webhook card under Create Destinations.

Destination catalog search for Webhook with the Webhook Cohorts card highlighted
5

Configure the destination

On Add New Webhook Destination, fill in the Destination Settings.

  • Display Name: StackOne
  • Webhook URL: paste the Native Webhook URL you copied from StackOne.
  • Leave Headers as they are. The preset Content-Type and User-Agent headers are all StackOne needs.
  • Optionally set Number of users per batch to limit how many users each delivery carries.
Add New Webhook Destination form with Display Name and Webhook URL highlighted
6

Keep the default payload

Expand Define cohort update payload and keep Send Amplitude’s default payload selected. StackOne routes events by the default payload fields, so a customized payload is not delivered to any event.

Define cohort update payload section with Send Amplitude's default payload highlighted
7

Save the destination

Click Save.

Destination Settings with the Save button highlighted and the Webhook URL hidden
8

Confirm the destination is connected

The new Webhook destination named StackOne appears on Destinations with the status Connected.

Destinations table showing the StackOne webhook destination as Connected

​
Sync a cohort to StackOne

Cohort events are sent when a cohort is synced to the StackOne destination. Repeat these steps for every cohort you want to receive events for.

1

Open the cohort

In the left navigation, open Users > Cohorts, open the cohort, and click Target Users.

Cohort details page with the Target Users button highlighted
2

Choose the Webhook destination

Under or sync this cohort to…, click Webhook.

Use this cohort in a dialog with the Webhook option highlighted
3

Select the StackOne destination

In Select Defined Destination, pick the StackOne destination you created and click Next.

  • Optionally use Add A User Property to include user properties with each user in the payload.
Select Defined Destination dialog with the StackOne destination and Next highlighted
4

Choose a cadence and start the sync

On Define Cadence, pick how often Amplitude sends the cohort, then click Sync.

  • One-Time Sync sends the users currently in the cohort. Running it again later sends only the changes since the last sync.
  • Scheduled Sync sends changes every hour or every day, and Real-Time Sync every minute. Both require a plan that includes them.
  • Static (uploaded) cohorts do not change on their own, so scheduled syncs will not update them.
Define Cadence dialog with One-Time Sync and the Sync button highlighted

​
Stream events and user properties

To receive analytics events and user-property updates as they are ingested, add a second destination of type Webhook: Events · User Properties from Data > Connect Destinations > Add Destination, paste the same Native Webhook URL, keep the default payload, and enable the event and user streams you need. This destination is only listed on plans that include Event Streaming. See Amplitude Webhook Streaming for plan details.

​
Available webhook events

The following Amplitude events can be enabled. Only events selected in StackOne are delivered, and Amplitude only sends events for the destinations and cohort syncs you configure.

1

Cohort events

Sent by the Cohort Webhook destination for every synced cohort.

  • Cohort Users Entered (cohort.users_entered) — Fired when a cohort sync delivers a batch of users who joined the cohort
  • Cohort Users Exited (cohort.users_exited) — Fired when a cohort sync delivers a batch of users who left the cohort
2

Event streaming events

Sent by the Webhook Events · User Properties streaming destination.

  • Event Streamed (event.streamed) — Fired for each analytics event Amplitude ingests and forwards
  • User Streamed (user.streamed) — Fired for each user-property update Amplitude ingests and forwards

​
Delivery format

Details of how Amplitude delivers events to StackOne.

1

Batched cohort payloads

Each cohort delivery carries a list of users for one cohort, marked as entering or leaving it. Large cohorts are split into several deliveries, sized by Number of users per batch. Every delivery has its own message_id, which StackOne uses as the event ID, so retried deliveries can be deduplicated.

2

Retries

Amplitude retries failed deliveries, so the same event can arrive more than once. Deduplicate on the event ID.

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.