Userbase

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Last active is the column that predicts churn, and it is the one nobody maintains by hand.

Plan sits next to activity, so the expensive silence is distinguishable from the free one.

Joined and last active together show whether somebody ever activated, which is a different problem from lapsing.

Feeds Segments, so "dormant ninety days" becomes a group that stays current rather than a query someone reruns.

How it works

1
Accounts appear when somebody signs up; nothing is imported.
2
Last active is written on genuine activity rather than on a page load.
3
Joined against last active distinguishes somebody who never activated from somebody who lapsed — different problems, different fixes.
4
Feeds Segments, so dormant ninety days becomes a group that stays current.

Best for

Comparing many records across many fields.

Not the right choice for

A phone. A table is the first thing that stops working narrow.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Userrequired	email	The account identifier, normally the address they signed up with.
Planrequired	text	What they pay for. Sits next to activity so expensive silence is distinguishable.
Joinedrequired	date	When the account was created, which is how never-activated is told from lapsed.
Last activerequired	date	The last real session. Written by the system, never edited, which is why it stays true.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Activity means what the product counts as activity, which is a decision this module does not make for you.
One row per account, so a shared login looks like one person.
No engagement scoring or churn prediction — it shows the dates and leaves the judgement.
It holds personal data, and deletion is the owner obligation.

Before it works

What you have to provide, if anything.

Nothing, if accounts already exist.
Decide what counts as active before relying on the column. A page load is not a session.

In practice

A subscription product with about two thousand accounts.

“Who is about to leave?”

What was said to the agent

What the agent built

The userbase sorted by last active, with plan alongside.

What changed

Forty-eight accounts inactive past ninety days, nineteen of them paying. The paying nineteen got a personal email; eleven replied.

Better with

These do a different job on the same data. An agent can have all of them.

SegmentsLive

You address different kinds of customer differently and the definitions need to stay current as behaviour changes.

FeedbackLive

Comments arrive continuously through several channels and currently vanish into inboxes and messages.

KPI pageLive

A few numbers genuinely drive decisions and they need to be visible without anyone running a report.

Who uses this page

SaaS support team

Answers from your real documentation, and escalates the rest with context attached.

Customer success team

Catches the questions that become churn, and tells you which accounts are quietly stuck.

Subscription box or DTC brand

Handles skips, swaps and “where is it” — the three messages that fill your inbox.

Utility or telecom provider

Takes meter readings and fault reports at the hour people actually notice them.

Questions

What data does the Userbase page use?

It reads person records the agent has collected. End-users of the agent + captured data. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a table the wrong choice?

A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.