> 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/onboarding/getting-started/account-organization/change-history.md).

# Change history

To see your account changes, go to **Settings** > **Change history** in the bottom-left menu:

<figure><img src="/files/XANn9Jh6LNG9u9e2rSdu" alt="" width="270"><figcaption></figcaption></figure>

On the **Local change history** tab, you can find changes made directly in Adalysis:

<figure><img src="/files/spQs4QRLcqaMr2TGDf2t" alt="" width="480"><figcaption></figcaption></figure>

**Google Ads change history** shows changes made in Google Ads.

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

To see your **Microsoft Ads change history**, first switch platforms in the top-right menu.

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

{% hint style="info" %}
You can choose whether Google Ads changes appear under your admin user or individual team member. [Find out more.](/onboarding/getting-started/core-account-settings/team-members.md)
{% endhint %}


---

# 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/onboarding/getting-started/account-organization/change-history.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.