Dashboard guide

The dashboard is where non-engineers design and target surveys. This is a tour of what each area does.

Projects

A project maps to one app. It holds your SDK API key, the connected analytics source, the imported event/property catalog, the appearance theme, team members, and all surveys. Create your first project during onboarding; add more from the projects list.

Connecting analytics

Connect Amplitude to import your event and user-property catalog via the Taxonomy API, so the survey builder can autocomplete real names when you define triggers and audience filters.

Events

The Events page lists every event your app reports, whether it was imported or added by hand.

• Search and filter. Search matches event names, property names and descriptions. Filter to the events a survey uses, the unused ones, or by source. Press / to jump to search.
• See what depends on an event. Each row lists the surveys that trigger on it. Select unused events to delete them in bulk.
• Edit an event. Write a description (the survey builder shows it next to the event), and add, change or remove properties and their known values. Changes you make here are kept when Amplitude syncs.
• Rename an event. Surveys follow the new name automatically, but your app has to send it. Until it does, those surveys won’t show.
• Add events by hand. Add one at a time, or paste a list of names from your tracking plan.
• Amplitude stays in sync without deleting anything. A re-sync adds new events and properties and updates changed ones. Anything Amplitude stops reporting is marked Not in Amplitude and kept until you delete it, since a survey may still use it.

Event signals

Turn on event signals (on the Events page, or in Settings → Privacy) to see which events your app actually sends. The SDK then reports each event’s name, how often it fired, which platform sent it and its property names. Never property values or user ids. With signals on:

• Each event shows when it last fired and a seven-day trend.
• Events your app sends that aren’t in the list appear under Seen but not tracked, ready to add with their property names.
• The survey builder warns when a survey’s trigger event hasn’t arrived from a platform the survey targets in 30 days.

Event signals are off by default and only the project owner can turn them on. Apps pick up the change on their next config refresh. SDK versions released before event signals never send counts.

Live debugger

Events → Live debugger shows, as you use your app, every event a test device sends and what happened to each survey that triggers on it: shown, waiting for the rest of a sequence, the event’s properties didn’t match, outside the audience or sample, already shown within the frequency cap, and so on.

Add test devices by the user id your app passes to the SDK (identify / setUser, or your Amplitude user id). Apps pick up the change on their next config refresh; restart the app to apply it right away. Only test devices report, entries are kept for 24 hours, and removing a device deletes what it sent.

Building a survey

The survey builder covers everything about a survey in one place:

• Questions — add and order any of the question types.
• Trigger — choose SINGLE or SEQUENCE, pick the event(s), and add property match filters. Autocomplete pulls from your imported catalog.
• Audience — restrict by user properties (equality, AND-ed).
• Timing & frequency — delaySeconds, fireEvery/warmupCount, sampling %, and the maxPerUserDays per-user cap (use 0 for unlimited).
• Delivery — presentation (sheet or dialog), dismissible vs. required, and a custom success message.

Set status to Active to deliver it to the SDK. The builder offers Form, Tabs, and Split (with live preview) layouts.

Appearance

The Appearance editor sets your project-wide survey theme with a live preview:

• Colors — accent and its text, background/surface, text/secondary text, border.
• Shape — card corner radius (or match the device), control radius, or full-round pill controls.
• Layout & type — spacing rhythm, text alignment, overall text scale, and title typography (size, weight, line-height, letter-spacing).
• Fonts — system, or a curated Google font fetched at runtime (never bundled).

The theme flows to the SDK in the config and is applied automatically — no app release needed to restyle your surveys. See theming in the SDK.

Team

Invite teammates by email. Existing users are added immediately; others get a pending invitation that’s accepted automatically on their next sign-in. Owners can manage members and project settings.

Analytics

Each survey has an analytics view: impressions, response rate, completion, and the distribution of answers per question — so you can read results without exporting.