> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/list-advertise/google/manage-and-optimize-google-ads/google-shopping-ads/configuring-shopping-ads-campaigns/using-multiple-ad-group-generators-for-shopping-ads.md).

# Using multiple ad group generators for Shopping Ads

With our Shopping Ads v2, you now have the possibility to create multiple Shopping ad group generators. This looks similar as multiple ad groups for Text Ads:

<figure><img src="https://content.gitbook.com/content/F8GepmoSonQRG6RnHOxJ/blobs/weAXxwxbF1ZVTKEtByCH/Shopping_ad_group_%20_EN_1.png" alt=""><figcaption></figcaption></figure>

To add a new Ad Group generator, click on the ‘Add dynamic shopping ad group’ button in this overview.

By default, there will be only one Shopping Ad Group generator in which you can configure your ad groups. In most cases one Shopping Ad Group generator will be enough to set up your ad groups in the way you want. However, you might have a goal or use case for which you need multiple Ad Group generators.

For each Shopping ad group generator you can configure the Settings, Rules and Build. In the Build step you create Product group subdivisions, which is important when using multiple Shopping ad group generators. For a detailed guide on the Shopping Ad group configuration, see [this article](https://channable-test.gitbook.io/channable-test-docs/list-advertise/~/revisions/41I7hnV8leiPulcDgOau/google-shopping/manage-and-optimize-google-ads/google-shopping-ads/configuring-shopping-ads-campaigns/configuring-ad-groups-for-google-shopping-ads).

The following things are good to keep in mind when configuring multiple Shopping ad group generators:

* When you configure the **Ad group name** the same for two different Shopping ad group generators, they will be combined in Google Ads. Therefore, the Product group subdivision **needs to be the same** in this case. Otherwise, it will result in errors.
* If you use different **Ad group names** for different generators, you can use different Product group subdivisions.

### Example

**Different ad group name**

| **Campaign name** | **Ad group generator name** | **Ad group name**      |
| ----------------- | --------------------------- | ---------------------- |
| Campaign 1        | Ad group generator 1        | Brand - \[brand]       |
| Campaign 1        | Ad group generator 2        | \[category] - \[title] |

In this example, the two different ad group generators are generating different ad group names. You can then also create different **Product group subdivisions** for these generators, for example on 'Brand' (level #1) and 'Product ID' (level #2) for Ad group generator 1, and on 'Category' (level #1) and 'Product ID' (level #2) for Ad group generator 2.

For more information on the product group subdivisions, also see [this article](https://channable-test.gitbook.io/channable-test-docs/list-advertise/~/revisions/41I7hnV8leiPulcDgOau/google-shopping/manage-and-optimize-google-ads/google-shopping-ads/configuring-shopping-ads-campaigns/configuring-ad-groups-for-google-shopping-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://helpcenter.channable.com/list-advertise/google/manage-and-optimize-google-ads/google-shopping-ads/configuring-shopping-ads-campaigns/using-multiple-ad-group-generators-for-shopping-ads.md?ask=<question>&goal=<user_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.
