Hawkings
The growth analyst built into the dashboard. It reads your live Fictura data, answers in plain English, and proposes changes it is never allowed to make itself.
Hawkings is the assistant in the dashboard: press Ask Hawkings in the header of any page. It answers questions about your app using your actual event data rather than general advice, and it opens as a panel that pushes the page aside instead of covering it, so the numbers you are asking about stay on screen.
It knows which screen you are on. Asking "can I call a winner yet?" on Experiments and on Paywalls are different questions, and Hawkings reads the room before it reads the data.
What it can see
Hawkings calls the same read APIs the dashboard does, scoped to the app selected in the header:
| It can read | Which answers |
|---|---|
| Headline metrics and the conversion funnel | Where users stop, and how much each step costs you |
| Events and your tracking plan | Whether something important is going unmeasured |
| Cohorts by billing outcome | What converters did that cancellers didn't |
| Paywalls and onboarding flows, with which is live | What to test, and against what |
| Experiment results | Whether a test has actually resolved |
| Spend, campaigns and ROAS from paid ads | Which campaigns pay for themselves |
| App Store Connect subscription products | Whether a paywall references a product that exists |
| Search Console numbers and what changed in them | How people find your website on Google |
| Store numbers from Appfigures, and revenue split by store and country | Downloads, ratings and reviews. App Store against Google Play |
| Issues | What is crashing, and for how many people |
| What you have imported | Whether your history has come over, and how far back it goes |
| App identity: bundle ID, Team ID, Android package and fingerprints, store addresses, website | Whether your links can open the app and reach the right store |
| These docs, including the dashboard map | How a feature works, and where anything is in the dashboard |
What it can and cannot change
Hawkings mostly reads. It can do a few setup tasks when you ask it to in chat, such as saving your app identity fields, opening a form to connect a data source, starting an import, or making a creator link. It cannot ship a paywall, start an experiment, pause a campaign, or change a budget. When the data argues for a change it drafts a proposal and sends you to the page where you confirm it. The assistant that can move your revenue is deliberately never one sentence away from doing it.
Finding your way
Ask Hawkings where something is, like "where do I put my bundle ID?" or "how do I connect Postiz?". It searches these docs and the dashboard map, then tells you the page and the steps.
When it cannot confirm that something exists, it says so. It points you to the Help page instead of guessing.
If you keep asking for the same thing and its answers are not helping, it offers to hand the conversation to a person. That opens a ticket with the conversation attached, and the team replies on the Help page.
Getting a good answer
Hawkings is built to refuse to guess, and that shapes how to ask:
- It will tell you the sample is too small. Below roughly 100 users in a funnel step it says so rather than reading noise as signal. That is the correct answer, not a failure.
- It separates measurement from estimate. Industry ranges are marked as rough figures; your numbers are never presented as anything but your numbers.
- It distinguishes attributed from blended. On revenue questions, campaign-attributed metrics and blended totals are reported separately, and unattributed revenue is called out rather than quietly folded into a campaign.
- Ask for the decision, not the dashboard. "What's the single highest-impact thing to fix?" gets further than "show me my metrics", because the numbers are already on the screen behind it.
Starting over
⋮ → New chat clears the thread and starts a fresh one. ⋮ → History reopens an old one. Conversations are kept per app and per person, so your threads are yours. A teammate on the same app does not see them.
Attach an image, PDF, CSV, or Markdown file with + and Hawkings will read it alongside your live data. See Attaching files for what it accepts and what happens to what you upload.
What it remembers
Hawkings keeps short notes between conversations. Notes about your product, like your domain or a decision you made, are shared with everyone on that app. Notes about you, like how you want to be talked to, follow you into every app. Tell it to forget something and it removes the note.
The full-page workspace
The chat icon at the top of the sidebar swaps the sidebar for your conversations and gives Hawkings the whole screen. Each thread has a ⋮ menu to pin, mark unread, rename or delete it. Below the box you can pick how hard it thinks under Effort (High is the default), dictate your question, or take a screenshot from the + menu.
What it runs on
Hawkings needs your own Anthropic key in Setup → AI, unless your app's plan includes AI.
Answers can be wrong
Hawkings generates its answers from your event data, and generated answers can be mistaken, particularly on small samples or unusual instrumentation. Treat it as a fast analyst with access to your numbers, not as an auditor. Anything it proposes is worth the same sanity check you would give a colleague's suggestion.
Template → preview → store
How a paywall goes from a template key to a live surface to money — and where each piece of truth lives along the way.
Attaching files
Give Hawkings an image, PDF, CSV, or Markdown file to read alongside your live data — what it accepts, what it does with it, and what it deliberately never keeps.