> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/product.md).

# product

- [Product updates](https://docs.adalysis.com/product/product-updates.md): Find out what's new in Adalysis
- [Q3 2026](https://docs.adalysis.com/product/product-updates/q3-2026.md): Product updates in July – September 2026
- [Q2 2026](https://docs.adalysis.com/product/product-updates/q2-2026.md): Product updates in April – June 2026
- [Q1 2026](https://docs.adalysis.com/product/product-updates/q1-2026.md): Product updates in January – March 2026
- [Q4 2025](https://docs.adalysis.com/product/product-updates/q4-2025.md): Product updates in October - December 2025
- [Q3 2025](https://docs.adalysis.com/product/product-updates/q3-2025.md): Product updates in July - September 2025
- [Q2 2025](https://docs.adalysis.com/product/product-updates/q2-2025.md): Product updates in April - June 2025
- [Q1 2025](https://docs.adalysis.com/product/product-updates/q1-2025.md): Product updates in January - March 2025
- [Q4 2024](https://docs.adalysis.com/product/product-updates/q4-2024.md): Product updates from Q4 2024
- [Q3 2024](https://docs.adalysis.com/product/product-updates/q3-2024.md): Product updates from Q3 2024
- [Q2 2024](https://docs.adalysis.com/product/product-updates/q2-2024.md): Product updates from Q2 2024
- [Q1 2024](https://docs.adalysis.com/product/product-updates/q1-2024.md): Product updates from Q4 2024
- [Unveiling the new Adalysis interface](https://docs.adalysis.com/product/product-updates/unveiling-the-new-adalysis-interface.md): An improved navigation and new knowledgebase platform
- [Inside Adalysis](https://docs.adalysis.com/product/inside-adalysis.md): Weekly quick wins and tips
- [How to avoid performance blind spots](https://docs.adalysis.com/product/inside-adalysis/how-to-avoid-performance-blind-spots.md)
- [See how other PPC teams work](https://docs.adalysis.com/product/inside-adalysis/see-how-other-ppc-teams-work.md): The account setup many teams swear by
- [Ditch your budget trackers for good](https://docs.adalysis.com/product/inside-adalysis/ditch-your-budget-trackers-for-good.md): Get started with automated budget pacing
- [Better search term alerts: all signal, no noise](https://docs.adalysis.com/product/inside-adalysis/better-search-term-alerts-all-signal-no-noise.md): Get more relevant alerts by customizing your audit settings
- [The fastest way to catch performance issues](https://docs.adalysis.com/product/inside-adalysis/the-fastest-way-to-catch-performance-issues.md): Copy and adapt five popular performance monitors templates
- [Ad testing checklist](https://docs.adalysis.com/product/inside-adalysis/ad-testing-checklist.md): Practical ways to improve ad experiments and identify winning ads
- [Pricing](https://docs.adalysis.com/product/pricing.md): Adalysis pricing
- [Demo](https://docs.adalysis.com/product/demo.md): View or arrange a platform demo
- [FAQ](https://docs.adalysis.com/product/faq.md): Frequently asked questions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adalysis.com/product.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.