> 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/paused-campaigns-workaround.md).

# Paused campaigns workaround

Paused campaigns are not included in any of the Adalysis audits or analysis. You can, however, follow the below steps to include them if needed.  

Assigning an Adalysis-specific label to those campaigns keeps them enabled only within Adalysis (while they remain paused in Google Ads).

{% hint style="info" %}
You'll need to first create a label called **AdalysisKeepEnabled** (case-sensitive) from the **Manage** > **Labels** screen.
{% endhint %}

### **Scenario 1 — Campaign is paused after it was linked to Adalysis**

1. Enable the campaign **within Adalysis** and assign the label **AdalysisKeepEnabled** to it.
2. Pause the campaign **in Google Ads**.

### **Scenario 2 — Paused campaign isn't yet linked to Adalysis**

1. Enable the campaign in **Google Ads.**
2. Switch to the **Campaigns screen** in Adalysis and click **Link missing campaigns.**  The campaign should now appear in Adalysis.
3. Assign the label **AdalysisKeepEnabled** to the campaign. .
4. Pause the campaign in **Google Ads**.

{% hint style="success" %}
The campaign will now only be enabled within Adalysis, without affecting its status in Google Ads. It will now be included in the Adalysis audit and analysis.
{% 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/paused-campaigns-workaround.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.