Charts from real rows
Every DAU line or funnel bar comes from documents the aggregation returned.
Use case
If your app already writes events to MongoDB, you don't need a separate analytics tool to answer most product questions. Ask wuup for active users, funnels or adoption in plain English and get a chart built from the aggregation it ran on your events collection.

Who it's for
Product managers and founders whose app writes events to MongoDB
Sources
The problem today
Ask in plain English. Here is what happens behind each answer, including the query when there is one.
Filters October events, collects distinct userIds per day and counts them.
db.events.aggregate([
{
$match: {
ts: {
$gte: ISODate("2026-10-01T00:00:00Z"),
$lt: ISODate("2026-11-01T00:00:00Z")
}
}
},
{
$group: {
_id: { $dateToString: { format: "%Y-%m-%d", date: "$ts" } },
users: { $addToSet: "$userId" }
}
},
{ $project: { _id: 0, day: "$_id", activeUsers: { $size: "$users" } } },
{ $sort: { day: 1 } }
])Counts unique users at each funnel step and charts them as a funnel.
db.events.aggregate([
{ $match: { event: { $in: ["page_view", "add_to_cart", "purchase"] } } },
{ $group: { _id: "$event", users: { $addToSet: "$userId" } } },
{ $project: { _id: 0, step: "$_id", users: { $size: "$users" } } },
{ $sort: { users: -1 } }
])Groups signup events by the referrer stored in event properties.
db.events.aggregate([
{ $match: { event: "signup" } },
{ $group: { _id: "$properties.referrer", signups: { $sum: 1 } } },
{ $sort: { signups: -1 } }
])Counts distinct sessions per device, then wuup works out the percentages in the answer.
db.events.aggregate([
{ $group: { _id: "$device", sessions: { $addToSet: "$sessionId" } } },
{
$project: { _id: 0, device: "$_id", sessions: { $size: "$sessions" } }
}
])Uses $sortByCount on page for page_view events and returns the top 10.
db.events.aggregate([
{ $match: { event: "page_view" } },
{ $sortByCount: "$page" },
{ $limit: 10 }
])Uses $$NOW for a rolling window and joins to customers for names.
db.events.aggregate([
{
$match: {
$expr: {
$gte: [
"$ts",
{ $dateSubtract: { startDate: "$$NOW", unit: "day", amount: 7 } }
]
}
}
},
{ $group: { _id: "$userId", events: { $sum: 1 } } },
{
$lookup: {
from: "customers",
localField: "_id",
foreignField: "_id",
as: "user"
}
},
{ $project: { _id: 0, name: { $first: "$user.name" }, events: 1 } },
{ $sort: { events: -1 } }
])Connect read-only
Point wuup at the database with your events and users collections.
Ask the product question
"How many users added to cart and then purchased this week?"
Check the pipeline
Open the query used to see exactly how users were counted.
Every DAU line or funnel bar comes from documents the aggregation returned.
Open "queries used" to see how a user or session was counted, and reuse it.
"Active" can mean many things. wuup asks which event counts before it guesses.
No. wuup reads your existing collections and learns their fields. Consistent event names and a timestamp field make answers more reliable.
Aggregations run inside MongoDB, so wuup can summarise large collections; each query returns at most 100 rows to the model, which is plenty for charts and summaries.
For ad-hoc questions on data you already store, often yes. Purpose-built tools still win for session replay and autocapture.