# Results and analytics > Read the Results timeline, traffic and revenue, the Proof tab, the weekly Monday brief and the alerts bell in Prefera. Source: https://prefera.si/docs/results Docs index for agents: https://prefera.si/llms.txt Results shows why your numbers moved. It puts every fix you publish on one timeline next to how often AI answers name you, visits from AI assistants and Google clicks. Open it from the sidebar: **Did it work** > **Results**. Results needs a paid plan. Without one, the screen offers **Pick a plan**. ## The Results screen At the top are four tiles for the current month. The tiles are **AI answers naming you**, **Visits from AI assistants**, **Google clicks** and **Authority score**. A tile with nothing to show says why and links to the step that fills it. It never shows a zero in its place. Below the tiles is the timeline, titled **What you shipped, and what moved**. - It has one lane each for AI answers, AI visits and Google clicks. Each lane has its own scale. - AI answers come from your tracking runs. Visits and clicks are weekly totals, Monday to Sunday. - A numbered marker shows the day each fix went live. Click a marker to open that fix in the **Selected fix** panel. - Hover over the timeline to read the numbers for one week. - Use the period switch to pick **3 months**, **6 months** or **16 months**. - If you track more than one engine, use the engine menu to show one engine. The default is **All engines**. A lane that has no data explains what is missing. For example, it asks you to connect Google Analytics or Search Console. The button opens `/app/integrations`. Under the timeline, **Every fix and its outcome** lists each fix with its outcome, the targeted and control questions, and its re-checks. **Open its Proof** goes to that fix's Proof page. If you have visits from AI assistants, **Where AI visits came from** lists the assistants for the last 28 days. ## Traffic and revenue The **Traffic and revenue** card on Results covers the last 28 days. It reads from your own analytics, not from Prefera. It shows visits from AI assistants and visits from Google, with the change against the 28 days before. It adds conversions and revenue when your analytics source reports them. A table below lists each page with its visits and the fixes that touch it. - Connect an analytics tool first. The card links to **Connect an analytics tool** (`/app/integrations#traffic`). See [Analytics](/docs/integrations/analytics) for PostHog, Plausible and DataFast. - Google Analytics (GA4) and Search Console are set up through Google. See [Google Search Console and GA4](/docs/integrations/google). The timeline needs them for AI visits and Google clicks. - Prefera needs at least 56 days of history from a source before it shows a trend. - The card says that a page which rose after a fix may have risen for other reasons. ## The Proof tab Proof is the second tab of Results, and the **Proof** button in the top bar goes there too. It shows each fix measured against control questions you left alone. See [Proof](/docs/concepts/proof) for how the check works. ## The Monday brief The Monday brief is a weekly summary for one brand. Open it from the sidebar: **Manage** > **Monday brief**. ### What it contains The headline and summary come first, then the number of tracking runs the week is built from. These sections follow when they have content: - **Questions won and lost** - **Fix these first** - **Outreach follow-ups** - **Ask Google to index** - **Google and authority** - **Flips confirmed** - **Due for re-check** - **Competitors who took ground** - **Accuracy** Use the arrows on the right to move between weeks. The first brief needs a full Monday to Sunday week of regular tracking runs. Until then the screen shows when the next one is due. ### When it is sent and who gets it The brief is emailed every Monday at 07:00 UTC when it is enabled. It goes to each team member who keeps **Monday brief** on, with email on by default. Client viewers do not get it. A member limited to other brands does not get this brand's brief. To change who gets it, open the alerts page and change the **Monday brief** row under **Alert preferences**. The link on the brief reads **Change who gets it**. ### Email it now Owners and editors see **Email to team** on the brief. It emails that week's brief to everyone who keeps Monday brief on. There are limits on how often you can send it. If the limit is reached, a message tells you to try again later. ## Alerts The bell sits in the top bar of every screen, with a count of unread alerts. It opens **Alerts** (`/app/alerts`). Client viewers do not see this page. - Filter with **All**, **Unread**, **Competitors**, **Fixes**, **Accuracy** and **Runs**. - Click an alert to open the screen it points to. This also marks it read. - Use **Mark all read**, or the tick on one alert to mark it read or unread. ### Alert kinds | Alert | When it fires | | --- | --- | | Competitor takes a question | Two or more questions in one run | | Fix re-check finished | A re-check flipped, stayed within noise or lost ground | | Accuracy issue found | A statement contradicts a fact | | Run errors and retries | An engine did not respond on many answers | | Usage near your allowance | At 80% and 100% of the monthly answer cap | | AI described you negatively | An engine starts describing you critically | | A daily question moved | Daily answers agree for 3 days running | | An agent asks for approval | A connected app or API key waits for you in **Approvals** | | Social posts ready to post | Social autopilot drafted posts from an article that went live | ### Alert preferences In-app alerts are always on. In **Alert preferences**, each row has a toggle for email and one for Slack. The email goes to the address shown under the list. Slack posts to the channel you connected. If you have not connected Slack, the page links to **Integrations**. See [Slack, email and webhooks](/docs/integrations/notifications). Preferences are saved per person.