You’ve had Pendo running for a couple of months now, and someone on the leadership team just asked if it’s actually paying off. You pull up the dashboard, see some numbers moving, and realize you don’t actually know what “working” is supposed to look like at this stage. That’s normal. Most teams can tell you how to install Pendo. Almost nobody tells you what Pendo adoption success looks like at day 30, 60 or 90, and what a bad sign looks like before it becomes a bigger problem.
Adoption success isn’t “people logged in.” It’s a small, specific set of numbers moving in the right direction on a schedule you set ahead of time, the way a doctor checks weight and blood pressure at specific visits instead of guessing how you’re doing from the hallway. (If you’re reading this at day 45 wondering if you’re already behind, you’re not. Keep reading.)
Here’s the shape of it, broken into the three checkpoints that matter.
At 30 days you’re not measuring success yet. You’re measuring whether the thing is even alive. Look for:
If none of that is true, you don’t have an adoption problem yet, you have an installation problem. The most common day 30 mistake is grading a system that hasn’t actually launched anything. I’ve watched teams panic about low usage numbers when the guide they were counting on was still sitting in draft.
Self-check: has anything you built actually gone live to a real segment of users, or is it still waiting on a sign-off?
By day 60 the pilot group isn’t the whole story anymore. You want to see usage move past the first team that asked for it. Watch for:
That last one is the real signal. Nobody asks a follow-up question about a tool nobody’s using. If usage is flat and only the original three people ever log in, the tool is working exactly as installed and exactly as adopted, which is to say, not very much (a distinction that saves a lot of arguments in status meetings).
Self-check: if you took away the original champion for two weeks, would anyone else notice the tool was still running?
Ninety days is when you can finally talk about adoption instead of activity. This is the checkpoint that answers the leadership team’s actual question. Look at:
I used to tell clients that a busy dashboard at 90 days meant the rollout worked. It didn’t always. I was reading return visits as new interest for the better part of a year before I caught the difference. The fix was simple once I saw it: track unique returning users, not total events.
Adoption isn’t a launch event, it’s a number you check on a schedule.
Self-check: could you pull your day 90 numbers right now, without asking someone else to run the report for you?
Failure rarely looks dramatic. It looks like flat lines. At day 30, nothing has gone live. At day 60, only the original team is using it and nobody outside has asked a question. At day 90, usage is a graph that spikes once during training and never moves again. None of these show up as an alert. They show up as silence, and silence is the actual warning sign, not a bad number.
If your rollout stalled somewhere in the setup itself, Inheriting Pendo? Here’s How to Get It Working walks through what to fix first when you’ve taken over an account that never got off the ground.
None of these milestones happen by accident. They happen because someone is checking on a schedule, the workflows point at something people already do, and the guides get built small enough to actually launch. Pendo Consultants for B2B SaaS Teams work through exactly this cadence with teams who inherited a half-built instance.
For the mechanics of building the guides themselves, Pendo’s own documentation on defining guide settings is worth reading before day 30, and their guide to Pendo for customer success is useful once you’re past day 60 and looking at retention questions.
If the numbers stall because people never started, read our guide to getting the team to use Pendo before you grade the rollout.
If the account itself is still half built, start with the Pendo admin setup plan and come back to these checkpoints once the basics are live.
Flat usage past day 60 with no new segment engaging is the clearest sign. A single spike during training week that never repeats is the second.
There’s no universal percentage, but returning weekly usage from more than the original pilot team, with at least one documented decision made from the data, is the bar that separates “installed” from “adopted.”
Yes. Day 30 is a baseline check, not a scorecard. If something real is live and a real segment has seen it once, you’re on schedule.
Try this one thing this week: pull your day 30, 60 or 90 numbers, whichever checkpoint you’re closest to, and check one figure, the percentage of your target segment that’s seen a live guide more than once. That single number tells you more than the whole dashboard.
Book a strategy call and we map your first 90 days with you.