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

# Investigate a performance change

> Use Diagnostic and Analytics to examine a change before choosing an action.

Start with an observed change, such as higher CPL or fewer leads, and confirm the same account, reporting period, attribution, and result definition before diagnosing it. A plausible explanation needs evidence before it becomes a decision.

## Run a diagnostic

1. Open **Intelligence → Diagnose → Diagnostic** for the selected account.
2. Under **What did you notice?**, choose a suggested question or describe the change in the text field, then select **Run diagnostic**. Selecting a suggested question starts its diagnostic immediately.
3. Let the analysis finish. Read the explanation alongside its evidence and competing theories; verify the relevant entities and dates against the original report.
4. Separate measured facts from inferred reasons. Choose a next investigation or a narrowly scoped change rather than treating the diagnosis as proof of causation.

If the page shows a plan gate, inspect **Settings → Billing** for your workspace's access. If it fails or lacks evidence, check [data freshness](/intelligence/freshness), reconnect when necessary, and rerun after data is available. Running a diagnostic does not itself change ad delivery.

## Inspect Analytics

Open **Diagnose → Analytics** for **Audit & Analytics**. Choose its reporting window and review **Overview**, **Budget**, **Creative**, **Audience**, and **Copy**. Scores summarize the available evidence; they do not guarantee future results.

For example, compare a budget concern with current budgets and the confirmed change history, then inspect whether the reporting window includes the change. For a creative concern, check the actual assets, audience, and sample size. Use [manual delivery](/meta-ads/delivery) or [budget review](/meta-ads/budgets) when you have decided on an action.


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