> For the complete documentation index, see [llms.txt](https://docs.ppcstorm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ppcstorm.com/automations/automation-engines/automation-recipes.md).

# Automation Recipes

Recipes allow you to build a templated set of rules to apply to your campaigns. This helps you add rules in bulk, and create consistency across certain goals you'd like to achieve.

E.g. If you are looking to create a 'Recipe' for launching new products - your recipe could include something along the lines of the below (bare in mind all product launches are different, so feel free to edit the values suggested here to better-fit your case).

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

{% hint style="info" %}
Make sure to build out the individual rules you'd like to add to the recipes before this step!
{% endhint %}

GOAL: Launch new product aggressively - as many new sales as possible in the first few weeks.

Automation Rules:\
\- **ACOS OPTIMIZER:** 100% ACOS *(allow for higher ACOS during launch)* | 7 Day look-back *(shorter time-frame as not much data to work with during launch)* | Daily edits *(editing bids daily to align with new data coming in)* | Max Change per day 20% (*more aggressive than normal to pivot quickly when needed)* | Min bid *(set this to something quite high to avoid dropping too low and losing impressions)* | Max Bid *(set this as high as you can, but still ensure this is set to stop automations pushing beyond comfort level).*\
\
\- SEARCH TERM ZAPPER: Daily checks | 8 clicks threshold (lower than normal, to negate quickly during launch) | 30 day lookback | Negate at ad group\
\
\- KEYWORD COAXER: Daily Checks | <50 impressions | 30 day lookback | Increase by 0.10c | Max Bid *(whatever the max bid is for your use case for the automation to increase it to over time).*\
\
\- WASTED SPEND OPTIMIZER: Daily checks | 12 clicks threshold (lower than normal, to pause quickly during launch) | 30 day lookback \
\
\- SEARCH TERM SCOUT: Daily checks | <100% ACOS (higher than normal to get more opportunities for more keywords to make sales) | at least 1 sale (lower than normal, to get more keyword opportunities)| \
\
The above recipe is a simple one, that helps you find winners and losers quickly without needing to manually dig through the data every day- and adjusts the bids on all live targets that pushes this launch towards 100% ACOS sales for more sales volume!

<br>


---

# 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.ppcstorm.com/automations/automation-engines/automation-recipes.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.