Dashboards let you build and organize your own views of product analytics — charts, funnels, and key metrics — without leaving Appcues. You can create as many dashboards as you need, fill each one with cards, and filter the whole dashboard by date or audience.

Dashboards are available in the Appcues App at app.appcues.com.

Dashboards are part of the Appcues App, which is in beta and rolling out gradually. If you don't see the Appcues App for your account yet, it hasn't been enabled — it's on the way. See Introducing the Appcues App for more.

How Dashboards are organized

There are three building blocks:

• Dashboards — a named collection of cards. Find them under Dashboards in the left nav. Build as many as you want.
• Cards — a single chart, funnel, or metric on a dashboard. Each card answers one question, like "How many users started this experience?"
• Filters — date range and audience conditions you set at the dashboard level. Every card on the dashboard inherits them.

Find and open a dashboard

1. Click Dashboards in the left nav. The dashboard list opens on the left, with your most recently used dashboard shown.
2. Use the Search bar at the top of the list to find a dashboard by name.
3. Click any dashboard in the list to open it.

Create a dashboard

1. In the Dashboards panel, click the + next to Custom dashboards. A new, empty dashboard opens.
2. Click the dashboard title to rename it.
3. Add cards (see below). The dashboard saves automatically as you build.
4. You can also ask Appcues AI to build one for you by describing what you want to measure.

Set dashboard filters

Filters at the top of a dashboard apply to every card on it.

1. Click the Date is filter (for example, Last 30 days, daily) to change the time range and granularity.
2. Click Add filter to scope the dashboard to a specific segment of users and web or mobile platform.
3. Cards update to reflect the dashboard-level filters. Anyone viewing the dashboard sees the same filtered data.

Dashboard date ranges cover the full calendar day of included days in UTC — from midnight on the first day to 23:59:59 PM UTC on the last

Add a card

1. Open a dashboard and click Add card. The card builder opens.
2. Under What do you want to measure?, choose a card type:

• Metrics — track a measurement, visualized as a trend over time, a breakdown, or a single value.
• Funnel — measure conversion across a sequence of steps within a conversion window (see below).

3. Configure the card, then click Save card. The card is added to your dashboard.

Metrics cards

A Metrics card tracks one measurement, shown as a chart or a single large number.

1. Choose a Metric — for example, Unique count of users.
2. Under Filter by events, click Add event to choose the event the metric applies to. Add more than one event to compare them — each event appears as its own series on the card.
3. Use Compare by to break the metric down by a dimension (optional): Segments, Accounts, Campaign, Tactic, Page, Screen, Language, or Platform. Leave it set to None for a single series.
4. Choose how to display the card using the visualization selector in the top right: Timeseries, Bar chart, or Big value (Compare by isn't available for Big value cards).
5. Click Save card.

Funnel cards

A Funnel card shows how many users move through a sequence of events and where they drop off.

1. Set the Conversion time window — the number of days a user has to complete the funnel after entering it (defaults to 14).
2. Under Funnel events, click Add event to add the first step. Add more events to build out the sequence.
3. Preview the funnel as you add steps. You'll see the prompt "Add at least one event to preview the funnel" until the first event is added.
4. Click Save card.

Add a target to a card

Targets overlay a goal line on a Metrics card so you can see actual performance against where you want it to be.

1. In the card builder, turn on the Target toggle.
2. Choose Achieve (reach a value) or Maintain (hold a value).
3. Choose At least or At most to set the direction.
4. Enter the target value. The unit matches your metric — for example, users.
5. Click Save card (or Update card when editing an existing card). The target line appears on the chart.

Build a dashboard with AI

Instead of building cards by hand, you can describe what you want to Appcues AI in plain language and let it create the cards for you.

Open Appcues AI from the chat on your Home screen, or click the Appcues logo in the bottom-right corner to open it from anywhere — including while viewing a dashboard.

Appcues AI can:

• Create a single Metrics card — for example, "Add a card showing unique count of users over time."
• Create a Funnel card — for example, "Build a funnel from signup to activation (insert activation event)."
• Build a whole dashboard at once — several cards from one request, such as "Build a dashboard for feature adoption of (feature use) event."

Appcues AI can't yet:

• Add Compare by breakdowns or dashboard filters.
• Edit an existing dashboard or card directly — though it can offer to build a replacement card with the same setup.

To do anything Appcues AI can't — add a breakdown or filter, or change an existing card — open the card in the builder and edit it by hand.

Manage cards

Open the ⋮ (kebab) menu on any card for these actions:

• Edit — reopen the card builder to change the metric, filters, or visualization.
• Duplicate — create a copy of the card on the same dashboard. Useful as a starting point for a similar card.
• Add to dashboard — copy the card onto another dashboard.
• Remove — delete the card from this dashboard.

Dashboard ideas to get started

Each card answers one question, so a dashboard is a set of cards that together tell a fuller story. Build the cards below and arrange them on one dashboard — or describe the goal to the AI assistant and let it build the cards for you.

User Behavior

Goal: Understand how many users are active in your app, and what they're doing.

• How many users are active*? Count unique users and add Session Started and View events by selecting them from the event picker, under + Add event. Visualize as a Big value for a headline number, or a Timeseries to track over time.
• What are they doing while active?
  • Add Events per user to see how much activity users are doing, or Events per session to understand per visit engagement.
  • Break Sessions down with Compare by Dimension > Page to see what your top pages are, or by Segments to see which audiences are most active.

*Your active users number might differ very slightly from the Overview page in Appcues legacy Studio. This is because that is calculated 30 days back from the current timestamp, and then averaged. On dashboards, date ranges start from midnight on the first date, not the same time as the current timestamp.

Feature launch

Goal: Track reach and adoption after you ship a feature.

• How many people saw it? Count unique users on your experience or a key “feature awareness” event — visualize as a Big value for total reach.
• How many people used it? Count unique users on your feature's first use event — visualize as a Big value, or add your awareness and first use events on the same chart and visualize as a Timeseries, with each appearing as its own line.
• At what rate are users converting? Measure User Conversion Rate and add your conversion (first use) event followed by your awareness event. View as a Timeseries to see a trend over time, or view as a Bar chart and compare by Segments to see which audience is converting at a higher rate
• Where do people drop off between trying and finishing? Build a multi-step Funnel from your awareness event to your published event, with key steps in between, and a conversion window that 

Feature adoption

Goal: Measure how many people adopt a feature, and whether it becomes a habit.

• How many people have used it? Count unique users on the event tied to your feature (e.g., an action like "used [feature]," "created [object]," or "enabled [setting]" — whatever event fires when a user engages with it) — visualize as a Big value.
• Is usage deepening or fading? Events per user (how much users use the feature) as a Timeseries.
• Who's adopting it fastest? Set Compare by to Segments on either card to compare adoption across plans, roles, company size, or however you segment your users.

Experience performance

Goal: See whether your Appcues experiences are working.

• How many users started it? Count unique users on the experience's flow_started event — a Big value.
• How many completed it? Count unique users on flow_completed — a Big value. Turn on Target to set a goal, like "at least 500 users."
• Is performance trending up or down? Add both flow_started and flow_completed to one Timeseries card to watch the trend.
• What's the completion rate? Build a Funnel from flow_started to flow_completed.

Account engagement

Goal: Track engagement at the account level, for B2B products.

• Which accounts are most engaged? Count unique accounts on your key events as a Timeseries, with Compare by set to Accounts to see one line per account.
• What's overall engagement depth? Track Events per account as a Big value for a single engagement score.

Onboarding funnel

Goal: Find where new users drop off before activating.

• Where do users get stuck? Build a Funnel from signup through your key activation events, in order, with a conversion window that matches how long onboarding realistically takes.
• How many reach full activation? Count unique users on your final activation event as a Big value for a headline "activated" number.

Confirm it worked

• Your new dashboard appears in the Dashboards list and is searchable by name.
• Cards render data for the dashboard's date range and filters.
• Metric and funnel numbers update when you change the dashboard-level filters.

If a card has no data

• Confirm the date range is wide enough to include the events you expect.
• Check that any event filters on the card match events your users actually send.
• Confirm any segment filters on the dashboard contain users.
• For funnels, make sure the conversion time window is long enough for users to realistically complete the sequence.
• Remove or loosen dashboard-level filters to confirm the underlying data exists.