Connect your app and verify the first activity
Know what to prepare, what your developer connects, and how to confirm UserGist is receiving activity.
Last updated 9 September 2026
On this page
Before you start
Choose the app you want to work on from the app switcher at the top of the sidebar. Each app keeps its experiences, customer context, and configuration together. Use separate apps for a test environment and a live product when you need their data kept apart.
Connect the right platform
Open your app’s setup flow or App settings and select the platforms your product uses.
Give your developer the SDK guide for that platform and the app’s SDK key. Web, iOS, Android, React Native, and Flutter have platform-specific setup instructions.
Agree on one useful event to send, such as route_saved. Decide which user properties, such as plan, are needed for your audience rules.
For a website, add the site’s exact allowed origin and enable Web. A desktop preview alone does not enable delivery to your website.
Verify before launching
Open a test build, perform the action you instrumented, and check Events and the test user’s activity. Then publish one experience to a test audience and complete it in the product. Confirm that the response appears in its results. The editor’s preview helps with appearance; it does not prove the SDK connection or record a real response.
If nothing appears
Confirm the selected app and key match the build, the SDK has an active anonymous or identified user, and the relevant consent is granted. Event-triggered experiences also depend on the event reaching UserGist. Ask your developer to use the platform setup guide rather than copying another platform’s code.
Related guides
Build, preview, and launch your first experience