> 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/inside-adalysis.md).

# Inside Adalysis

Welcome back to Inside Adalysis, the content series that helps you get more from your subscription. Here's the latest edition:

{% embed url="<https://www.youtube.com/watch?v=MI1YqQzaZz0>" %}

Conversions are down 15% week-over-week, but what happened? This week’s quick win is a faster way to investigate changes in your account performance.

<figure><img src="/files/1b4MDrpZXcwMkvaPsEj2" alt="" width="375"><figcaption></figcaption></figure>

### Step-by-step guide

1. Start on **Performance** > **Overview**. Here you can create graphs with up to four metrics over different time periods to visualize your data.<br>

   <figure><img src="/files/eULySynalF1yL7nSD5rN" alt=""><figcaption></figcaption></figure>

   \
   Click any point in the graph for a before-and-after performance comparison. Or choose **View root cause analysis**.<br>

   <figure><img src="/files/8QjgJEzdtWpGvqgjFGbv" alt="" width="262"><figcaption></figcaption></figure>

2. Open the **Performance Analyzer** to trace where results changed. It starts with search volume, then shows how that flows through to impressions, clicks, and conversions.\
   \
   You can also see the factors that influence each stage.<br>

   <figure><img src="/files/EkKsr7K0GtM8PV8F1Ijh" alt="" width="563"><figcaption></figcaption></figure>

3. Click on the blue icons to drill down into campaigns, ad groups, and keywords.<br>

   <figure><img src="/files/NpKBy7v99WUfabqVVjyX" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
Colour coding: <mark style="color:$success;">Green</mark> = better. <mark style="color:$warning;">Orange</mark> = worse
{% endhint %}

You may find that your drop in conversions is tied to a drop in CTR, caused by lower ad positions.

To reverse the trend, you could improve ad relevance, review your search terms, test ads, or work on your landing page.

This workflow is much faster and more effective than digging through spreadsheets or fiddling with data exports.

{% hint style="info" %}
Download your analysis as a PDF or share straight from the screen.
{% endhint %}

### Catch up on older editions of Inside Adalysis

* [How to avoid performance blind spots](/product/inside-adalysis/how-to-avoid-performance-blind-spots.md)
* [Ad testing checklist](/product/inside-adalysis/ad-testing-checklist.md)
* [See how other PPC teams work](/product/inside-adalysis/see-how-other-ppc-teams-work.md)
* [Ditch your budget trackers for good](/product/inside-adalysis/ditch-your-budget-trackers-for-good.md)
* [Better search term alerts: all signal, no noise](/product/inside-adalysis/better-search-term-alerts-all-signal-no-noise.md)
* [The fastest way to catch performance issues](/product/inside-adalysis/the-fastest-way-to-catch-performance-issues.md)


---

# 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/inside-adalysis.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.