> 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/tools/audit/prebuilt-alert-list/pmax-campaigns/asset-alerts.md). # Asset alerts Alert names: Disapproved Performance Max assets, Performance Max assets that are automatically generated, and Performance Max assets with spelling issues Adalysis will alert you if an asset in your Performance Max campaign is: * Disapproved\ This means you can review and fix policy violations. * Automatically generated\ Replace automatically generated assets with fresh content to protect performance. * Has spelling issues\ Easily correct any errors for better quality assets. You'll see the alerts on your **Audit alerts** screen. Click on them for more details. #### Fixing asset issues * **Spelling issues:** use the **ignore** option if the spelling is correct, or the **edit** option to correct the asset text. * **Missing text assets:** in the asset count grid, click a **Headlines**, **Long headlines** or **Descriptions** count of 0 to add the first asset of that type. > Image and video assets can't be added or edited in Adalysis. Please update them in Google Ads. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.adalysis.com/tools/audit/prebuilt-alert-list/pmax-campaigns/asset-alerts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.