> ## Documentation Index
> Fetch the complete documentation index at: https://docs.perquery.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Impact tracking

> Record the changes that you make to your site and compare your AI visibility before and after each one.

**Impact Tracking** answers one question: did a change improve your visibility in AI answers? You record each change with the day it went live. Perquery compares the scans before that day with the scans after it.

Open it from the **Growth** group in the menu: **Impact Tracking**.

## How Perquery measures an action

Perquery compares the average of a fixed number of scans before the deploy date with the same number of scans after it. The table shows that number. The scans on the deploy date itself are not on either side.

What Perquery measures depends on the subject of the action:

| Subject | Measured over |
| - | - |
| **Prompt** | That prompt. |
| **Page** | The prompts that have this page as their target page, and the prompts that content analysis matches to this page. When there are none, all prompts of the site. |
| **This site** | All prompts of the site. |
| **Source domain** | All prompts of the site. |

> [!NOTE]
>
> A figure over many prompts moves for many reasons at the same time. Use it as context, not as proof. A prompt action gives the most direct result.

## Record an action

You can record an action from a [growth opportunity](https://docs.perquery.ai/en/act/opportunities.md), or record any change yourself.

> [!WARNING]
>
> Record the action after Perquery has scanned the site at least once. An action without a scan before it has no baseline.

**1. Open the dialog**

Click **Record an action**. The **Record an applied action** dialog opens.

**2. Choose the subject**

In **What the action was about**, select **This site**, **Page**, **Prompt** or **Source domain**.

**3. Give the reference**

For **Prompt**, select the prompt. For **Page**, type a path such as `/pricing` or a full URL in **Reference**. For **Source domain**, type a host name such as `example.com`.

**4. Describe the change**

In **What you did**, describe the change.

**5. Classify the change**

Select the **Action type**. Optionally, select the **Tool used**.

**6. Set the deploy date**

In **Deploy date**, enter the day the change went live, not the day you produced it.

**7. Limit the AI engine**

When the change can affect only one AI engine, select it in **Affects only**. Otherwise keep **Every assistant**.

**8. Save the record**

Click **Record**.

## Summary

The row at the top shows four figures:

| Figure | Meaning |
| - | - |
| **Tracked actions** | The actions recorded on this site. |
| **Positive impact** | The share of measured actions that improved visibility. |
| **Avg. visibility change** | The average change in visibility points, across measured actions. |
| **Awaiting results** | The actions that do not have enough scans on one side yet. |

## Applied actions

The **Applied actions** table shows one row for each record. The columns are **Subject**, **Action**, **Deployed**, **Visibility**, **Rank** and **Trend**.

Each record has one of these outcomes:

| Outcome | Meaning |
| - | - |
| **Positive** | Visibility went up by more than two points. |
| **Neutral** | Visibility changed by two points or less. |
| **Negative** | Visibility went down by more than two points. |
| **Awaiting** | There are not enough scans after the deploy date yet. The row shows the scans collected. |
| **No baseline** | There is no scan before the deploy date, so there is nothing to compare. |

### Filter the table

* Use **Action type** to show one type: **Technical**, **Content** or **Off-page**.
* Use **Outcome** to show one outcome.
* Use **Engine** to show the actions for one AI engine.
* Use the persona filter at the top of the page to measure the actions for one persona.

## Open a record

Click **Open** on a row. The detail shows these items:

* **Before / after visibility:** a chart of the visibility of each scan, with the deploy date marked.
* **Metric comparison:** **Visibility**, **Rank** and **Sentiment** before and after.
* **Applied actions:** the actions of the record.

When the record has an AI engine in **Affects only**, Perquery measures it on that AI engine only.

### Remove a record

Click **Remove this record**, then click **Confirm removal**.

> [!TIP]
>
> Use the export menu on the **Applied actions** table to download the records as CSV or Excel.

## Related pages

> [card] [Growth opportunities](https://docs.perquery.ai/en/act/opportunities.md)
>
> Find the changes that are worth making.

> [card] [Scans and schedule](https://docs.perquery.ai/en/sites/scans-and-schedule.md)
>
> See when Perquery scans your prompts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.