> ## 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.

# Explore trends and change history

> Compare forecasts, observed patterns, activity, and shareable snapshots in the right context.

Use **Intelligence** to answer a specific performance question while preserving account and date context. Forecasts, benchmarks, activity records, and snapshots answer different questions.

## Trends: Forecast and Market

Open **Trends → Forecast** to inspect available fatigue and CPL projections. Check their evidence, confidence, and freshness before planning a creative replacement or budget review. A projection is an estimate, not a promised outcome or an automatic ad change.

Open **Trends → Market** to compare available market benchmarks. Check that the comparison fits your objective and reporting context. A benchmark is context for investigation; it does not establish the reason your account changed. Missing results can mean insufficient coverage, not zero performance.

## History: Activity and Snapshots

Use **History → Activity** to inspect recorded changes and their associated entities. Confirm whether a record describes a proposed action or a completed change before explaining its effect. Performance after a change alone does not prove the change caused it.

Use **History → Snapshots** to revisit saved report snapshots. Open one to check its account and dates, or use **Copy link** to share it. Anyone with a report link can view it without AutoAdy sign-in. **Delete snapshot** stops that snapshot's shareable link from working; check with recipients first. See [client reports](/workspace/reports) for creating and delivering reports.

## Explore a question

Open **Explore** to choose a metric and reporting period, compare its chart and campaign ranking, and inspect available **Deep Analytics** sections such as **Performance by Day & Hour**, **Audience × Creative Heatmap**, **Asset Performance (cross-campaign)**, and **Tracking Health**.

Keep comparisons consistent: dates, timezone, attribution, metric definition, and account currency must agree. Do not add totals across incompatible money currencies. If a chart is empty or stale, follow [freshness and missing data](/intelligence/freshness) before drawing a conclusion.


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