Documentation

Example questions about your analytics

Here are examples for each kind of question. Ask in your own words, and use the names you see in your dashboard, such as the name of a feature, a page or a funnel.

What an answer looks like

Asked “Which features are used less than a month ago?”, a typical answer reads like this:

Compared with the four weeks before (Aug 5 to Sep 1), three features were used less in the last four weeks (Sep 2 to 29): “Export report” 412 times instead of 698 (−41%), “Share link” 1,208 instead of 1,356 (−11%) and “Saved filters” 38 instead of 52. The last one rests on too few uses to call it a trend. Today is left out because the day isn’t over yet.

Every percentage comes with its counts, and both periods are named. When a change rests on a handful of uses, your assistant says so.

Getting good answers

• Say the period when it matters: “in September”, “since 1 September”, “last week”. Without one, the assistant uses the last 28 complete days. Days follow your project’s timezone, and today is left out until it is over.
• Ask for a comparison: “compared with the month before” turns a number into a change.
• Use the names from your dashboard. If you are unsure what something is called, ask first: “Which features and funnels do we have?”
• Keep going. Follow-up questions work: “Break that down by week”, “On which page does that happen?”, “Show me the numbers behind that.”
• Ask it to check itself when an answer surprises you: “Is that enough data to be sure?”

The product review

Not sure what to ask? Start a product review. Your assistant goes through the same steps every time:

1. It compares the overall numbers with the previous period.
2. It names the features with the biggest change, and any feature that stopped being used.
3. It finds the weakest step of every funnel and says whether it got better or worse.
4. It lists the clicks people make most that no feature counts yet.
5. It says where a number rests on too little data to mean anything.
6. It ends with two or three concrete things to look at next.

In Claude Code, type /privatrak:product_review, or /privatrak:product_review 2026-09-01 2026-09-28 for a period of your choice. In other assistants, ask for a product review of your Privatrak project.

What your assistant sees

• The numbers you see in the dashboard: page views, clicks, features, click problems, funnels and the paths visitors take through your site.
• No individual people. Privatrak doesn’t know who your visitors are, so your assistant answers about groups, never about one person.
• Visitors per day. Privatrak counts a visitor once per day. Over a month, the same person can be counted on several days.
• Funnels from the day they exist. A funnel counts from the day it is created, so a new funnel has no numbers for earlier days.
• What your site sends. Plans or revenue appear only if your site sends them with an event or as a trait.
• The text people click. Your assistant reads the text of buttons and links. If a button shows a person’s name, that name is part of what it reads.

Act on an answer

If you chose Read and write when you connected your assistant, it can act on what it found. Ask, for example:

• “Create a funnel for that journey.”
• “Add a chart for export use to the dashboard.”
• “I fixed the cart button. Mark that click problem as resolved.”