Understand what integrations export and how to troubleshoot them
Know which fields leave UserGist and how to investigate a missing event.
Last updated 9 September 2026
On this page
What destinations receive
Exports include readable event names, a stable UserGist event key, app and identity context, and the allowed fields for each product area. Structured feedback and survey answers can include ratings, NPS values, choice IDs and labels, and supported dates.
What stays in UserGist
Raw short-text and long-text answers, request descriptions, comments, and arbitrary custom properties are not forwarded as unrestricted content. Text-answer events can indicate that an answer exists and its length without exporting the actual answer. Keep the complete response review in UserGist.
If an event is missing
Confirm the destination is connected and enabled for the selected app.
Check that the relevant product category is enabled.
Use Test connection and search the provider for the displayed synthetic device ID.
Review delivery attempts and any failure reason in UserGist.
Check the provider project, region, and time range, and allow for processing delay.
Remember the history boundary
Connecting today does not import yesterday’s UserGist events into the provider. Pausing or changing a connection affects subsequent delivery, not events the provider has already accepted. Copies held by a destination are separate; a UserGist privacy deletion does not automatically remove data already accepted by Amplitude or Mixpanel.