Skip to main content
product toursanalyticsonboardinguser experienceproduct adoption

Where Your Product Tour Breaks Down: Using Beacon Analytics to Pinpoint Drop-offs

You've built an onboarding tour, but users aren't completing it. Beacon's step-level analytics show you precisely where they're bailing and how to fix it.

Engineering TeamĀ·

You spent time crafting that perfect onboarding tour. You clicked through every step, made sure the tooltips landed just right on your Salesforce instance, and even recorded a snappy video for that complex part. So why are only 60% of users making it to the end?

It’s a common scenario, and frankly, it's frustrating. The good news is, with the right data, you don't have to guess. Beacon’s analytics dashboard provides step-by-step completion rates, showing you exactly where users abandon your flow. This isn't just about raw numbers; it’s about user behavior, and it tells a story.

The Data That Matters: Step-Level Completion Rates

When I'm trying to optimize a tour, the first place I always go is the individual step analytics. A tour might have a decent overall completion rate, but that often hides significant friction points. A single poorly designed step can tank engagement for everyone who reaches it.

Here’s how you find this data in Beacon:

  1. Log into your Beacon Dashboard: You'll land on your project overview.
  2. Select the Project: Each project corresponds to a specific website or application (like your-app.com or your-hubspot.com). Choose the one relevant to your tour.
  3. Navigate to Tours: On the left sidebar, click 'Tours'.
  4. Find Your Tour: Click the name of the tour you want to analyze.
  5. Go to the Analytics Tab: You'll see several tabs across the top: 'Steps', 'Settings', 'Analytics', 'History', etc. Click 'Analytics'.

You’ll immediately see a high-level overview – total views, unique users, and overall completion rate. But beneath that, there’s a chart or table breaking down performance by each step. This is where the magic happens. Look for the steepest drops in the completion percentage between one step and the next.

I prefer visual representations, so if it's a bar chart, I’m looking for a bar that's significantly shorter than the one before it. If it’s a table, I’m scanning the 'Completed' column for a sharp decrease.

Interpreting the Drop: What's Going Wrong?

Once you've identified a drop-off point, it's time to put on your detective hat. What kind of step is it? What were you asking the user to do?

Common Drop-Off Scenarios and Their Whys:

  • Complex clickwait steps: If your users are bailing on a clickwait step, it often means they can't find the element you want them to click, or they don't understand why they should click it. Maybe the selector is flaky, or the target element isn't immediately visible without scrolling.
  • Overly Wordy tooltip or modal steps: Too much text can overwhelm users. If a tooltip has five paragraphs, most people will skim or skip. Nobody reads the manual when they're trying to do something.
  • Unnecessary navigate steps: While navigate steps are powerful for guiding users through a multi-page flow (e.g., from a dashboard to a settings page), if you're navigating to a page that isn't clearly explained, users might get disoriented and bounce.
  • Tedious autofill fields (ironically): While autofill is supposed to reduce friction, if you're autofilling a field that's already populated, or that the user expects to fill manually, it can feel jarring. Or worse, if the autofill fails due to a bad selector, the user is just stuck.
  • Steps Requiring External Knowledge: If a step assumes the user knows an internal process or needs to fetch information from another system, that's a huge potential bail point. You're asking them to context-switch.

One thing I've noticed many times is that people tend to assume their users will 'just know' what to do. They won't. If you don't explicitly guide them, they'll guess, get it wrong, and leave. It’s better to over-explain a small interaction than to undersupply context for a big one.

Taking Action: Fixing Your Tour's Leaks

Knowing where users drop off is only half the battle. Here's how to iterate and improve based on your analytics:

1. Refine Element Selectors

If the drop is on a tooltip or clickwait, the first thing to check is the element selector itself. Did the UI change? Is it too generic? Beacon's Chrome Extension makes this easy: open your tour, edit the step, and use the visual picker to re-select the element and get a stable CSS selector. Sometimes, a simple ID is replaced by a class that changes with every deployment. The visual picker helps you find robust alternatives.

2. Simplify Step Content

Are your tooltips information-dense? Try cutting the copy in half. Use bullet points instead of paragraphs. Get straight to the point. If you need to provide more context, consider linking to a knowledge base article (Beacon supports integrating documents!) or adding an optional video step after the primary interaction is complete.

3. Break Down Complex Actions

If a single step asks the user to fill out a long form or perform multiple clicks, break it into smaller, more digestible pieces. For example, instead of one clickwait on a 'Save' button after filling a 10-field form, use an autofill for the crucial fields, then a tooltip to explain the remaining fields, and then the clickwait.

4. Add 'Pre-emptive' Guidance

Sometimes, the problem isn't the step itself, but what comes before it. If a user drops off at a step requiring them to find a menu item, maybe you need an autofill to collapse an unrelated section, or a navigate step to bring them to the right page first. Or, a simple spotlight step to draw their eye to the relevant part of the screen before the tooltip appears.

5. Consider Tour Length

No one wants to spend 20 minutes on a product tour. If your drop-offs are consistent throughout a very long tour, consider breaking it into multiple, shorter tours. You can then string these together as a 'course' in Beacon, allowing users to complete them sequentially.

6. A/B Test Your Changes

Once you've made a change, don't just assume it worked. Duplicate your tour, implement your fix in the duplicate, and run both versions simultaneously (perhaps target different user segments if you can). Beacon's analytics will help you compare performance side-by-side and confirm if your adjustments improved completion rates.

Regularly reviewing your tour analytics isn't just a good practice; it's essential for building effective product tours that truly onboard users. It's an iterative process, but the clarity Beacon provides means you're never flying blind.

Ready to find your tour's sticking points and fix them? Build your first tour for free and see the analytics in action at https://dobeacon.com/signup.

Try DoBeacon free

Add guided tours to any website in under 5 minutes. No annual contract, no per-MAU pricing.

Get started free →