Server events
Some of the moments you most want feedback on are sent to Amplitude by your backend, not your app: an order delivered, a ride completed, a payment captured. The SDK only sees events your app tracks, so on their own these can’t trigger a survey.
Server events fix that without code. Amplitude streams the events to MicroSurveys, and your app picks them up the next time it opens (or within a minute or two if it’s already open), then triggers surveys as if the app had tracked them.
Needs an Amplitude plan with the Webhook destination (Plus, Growth or Enterprise), and an SDK version with server events support. Updating the SDK is a version bump; no code changes.
Turn on server events
In the dashboard, open Settings → Integrations → Server events and select Set up. You get a webhook URL and a secret.
Add the Webhook destination in Amplitude
- In Amplitude, open Data → Catalog → Destinations and add Webhook.
- Paste the Webhook URL from the dashboard.
- Add one header: key
Authorization, valueBearer <your secret>(copy it from the dashboard). - Turn on Send Events and select the backend events your surveys trigger on. Leave the payload as Amplitude’s default. Events your app already tracks don’t need to be here.
- Set the status to Enabled and save.
The dashboard card shows when the first event arrives and lists every event name arriving from Amplitude, so you can check the filter before any survey uses them. It warns if Amplitude sends a wrong secret, or a payload we can’t read (keep Send Events on Amplitude’s default payload, not a custom template). Send Users isn’t needed.
Use the event in a trigger
Pick the event in the survey builder like any other. It works in SINGLE triggers and as any step
of a SEQUENCE, including a mix: for example book_clicked (tracked by the app) then
ride_completed (sent by your backend).
When the survey appears
| Situation | Survey appears |
|---|---|
| App closed when the event happens, opened later | When the app opens |
| App open when the event happens | Usually within 1–2 minutes |
A server event stays usable for 24 hours by default (configurable from 6 hours to 30 days on the same card). After that it’s dropped, so nobody gets asked about a ride from last week.
Sequences work across sessions: if someone books in the app and opens it again the next morning, the sequence completes then. Sequence windows are measured from when each event actually happened, not from when the app opened.
What we store
Only events a live survey triggers on, and only the properties those triggers match on. Everything else Amplitude sends (other properties, location, user properties) is discarded on arrival. A waiting event is deleted as soon as the user’s app picks it up, or when it expires.
Users must match
Events are matched to the app by Amplitude user id (or device id, for events sent with only a device id). The app must be identified in Amplitude with the same user id your backend uses, which is the case for signed-in users.