# Generate campaign projects

After a campaign has a brief and assets, create projects from the path that matches your goal. Use template recommendations when you want speed, blank projects when you want control, and clone when you want to adapt a proven format.

When using the template cart, add several promising templates, compare them in the cart or queue, remove weak fits, then tweak ingredients before generation. This lets you generate a coordinated batch of ads instead of opening one template at a time.

Campaign assets can become ingredients inside a project. For example, a product image can become `@Product`, a screen recording can become `@Broll_Demo`, and the CTA from the brief can become `@CTA`. Keeping these ingredients consistent makes it easier to create variations later.

Use a clear naming convention for generated projects. A useful format is `Campaign - Hook Angle - Actor - CTA - v01`. This makes campaign review and batch export much easier.

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

<figure><img src="/files/9i52rub5M26jKRIb2W2R" alt=""><figcaption></figcaption></figure>

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


---

# Agent Instructions: 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:

```
GET https://docs.avastudio.com/campaigns/generate-campaign-projects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.