> ## Documentation Index
> Fetch the complete documentation index at: https://user-guides.demand-genius.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Performance tracking
> The Performance columns in the Library: traffic, influenced MQLs, SQLs and closed-won revenue per page, what feeds them, the time-window and pipeline controls, and how influence is decided.
Performance tracking answers "what pieces of content are influencing pipeline?", and helps you make sure your content audit doesn't risk removing pages that drive traffic. It lives inside the Content Intelligence Library as a column group, so the same grid that tells you how well a page is written also tells you how it is performing against the metrics your leadership care about. Sort by any of those columns and you have your answer to which pages are doing the work.
The intent is influence measurement, not credit allocation. A page counts as influencing a deal when someone from that account read it in the run-up to the stage change. The output tells you which content to prioritise, not whether a piece directly caused a sale - we're not a full blown attribution solution!
## What you need
1. The tracking script on every page of your site. It records the page views. See [Website and tracking script](/integrations/cms-integration).
2. A CRM connection, with pipelines and a closed-won stage configured, so the platform knows who became a contact and which deals they were part of. See [Connect HubSpot](/integrations/hubspot) or [Connect Salesforce](/integrations/salesforce).
3. Performance enabled on your workspace by Demand-Genius. Until then the columns show an **Off** chip.
## The Performance columns
Open **Library** under Content Intelligence. The **Performance** group sits to the right of the KPI groups. Collapsed, it shows one summary column; expand it for the four columns.
| Column | What it counts |
| ------------------------- | ------------------------------------------------------------------------------- |
| **Traffic Total** | Page views recorded by the tracking script in the selected time window |
| **Influenced MQL** | Contacts who became an MQL after viewing this page |
| **Influenced SQL** | Deals that reached SQL where someone on the account had viewed this page |
| **Influenced Closed Won** | Closed-won deals, as revenue, where someone on the account had viewed this page |
### Reading it
* **Sort** by Influenced Closed Won to rank pages by revenue touched; by Traffic Total to see reach; by both to find high-traffic pages that never reach pipeline, and low-traffic pages that do.
* **Filter** by any tag column first to answer a narrower question: which content type, topic or funnel stage influences SQLs, for example. Smart Column tags work the same way.
* **Export CSV** to total the columns or chart them elsewhere.
### Controls above the grid
* **Traffic window** sets the period the Traffic Total column counts: **1 day**, **7 days**, **30 days** or **All history**. It defaults to 30 days and applies to traffic only.
* **Pipeline** appears when you have more than one CRM pipeline configured. **All pipelines** sums the Influenced columns across every pipeline; choosing one shows that pipeline's contribution alone.
* **Computed** shows when the Influenced values were last calculated. They are as of that time, not live.
## How influence is decided
The rules live in **Settings > Attribution**. They decide how far back a page view counts and what a deal needs before a page is credited with influencing it.
| Section | Setting | What it does |
| -------------- | ---------------------------------- | -------------------------------------------------------------- |
| **SQL** | Automatically include MQLs | Content that influenced the MQL also counts towards the SQL |
| **SQL** | Attribution window | How far back before the stage change page views count |
| **Closed Won** | Automatically include SQLs | Content that influenced the SQL also counts towards closed won |
| **Closed Won** | Number of content interactions | Minimum page views before a page counts |
| **Closed Won** | Require interaction at every stage | Only count content seen at MQL, SQL and closed won |
| **Closed Won** | Number of stakeholders engaged | Minimum distinct people from the account who viewed content |
Save applies the definitions from the next recompute. **Reset** discards unsaved changes.
## When the numbers update
* CRM data syncs once a day. A deal that changed stage today appears tomorrow.
* Influenced values are precomputed nightly over a fixed rolling 30-day window, and again after a crawl. The **Computed** stamp tells you which run you are looking at.
* Traffic Total is precomputed per window, so switching the Traffic window is instant.
## What the empty states mean
| What you see | What it means | What to do |
| ------------------------------------------------------------------------ | ---------------------------------------------------------------------------- | ------------------------------ |
| **Off** chip | Performance is not enabled for the workspace | Ask Demand-Genius to enable it |
| Dash, or **Not yet computed. Values appear after the next nightly run.** | Enabled, but the first calculation has not run | Wait for the overnight run |
| **0** | A real zero: the page was viewed by nobody who later converted in the window | Nothing to fix |
## Troubleshooting
* **Everything is zero.** Check Settings > Website shows the domain as **Verified**, the CRM shows **Connected**, and at least one pipeline has a closed-won stage set.
* **Closed Won is empty for one pipeline.** Its closed-won stage is **Not set** in the CRM configuration. Deals from that pipeline are excluded until you set one.
* **Numbers changed after adding a pipeline.** Expected. With **All pipelines** selected the Influenced columns sum across every configured pipeline.
* **Traffic looks low.** Check the Traffic window; the default is 30 days. Then check the script is in a site-wide footer, not a single page template.
* **Salesforce figures look incomplete.** Salesforce runs through the shared sync path and parity with HubSpot has not been verified end to end. Tell Demand-Genius what you see.
Earlier versions of the platform had a separate Performance dashboard with Attribution and Journey views. It has been retired. The data and the setup are the same; the Library columns are now the only view.