Recipe World

Start optimizing your advertising in minutes with premade recipes.
Ad Type:
1 Order Targets
Target
Find poor-performing targets and pause them to eliminate wasted ad spend.
Frequency: Once per day
Trigger:
(over the last 60 days (orders = 1 and clicks > 1000 and acos > 100%)) and (over the lifetime orders = 1)
Action: Set state to paused
5.0(123)
Download
86 downloads
Q4 0 Impression
Target
Increase bids on targets that historically have had low acos orders, but have had no impressions recently.
Frequency: Manually
Trigger:
(over the last 5 days orders > 0 and acos < 40%) and (over the last 2 days impressions = 0)
Action: Increase bid by 0 05
5.0(123)
Download
77 downloads
Recipe 004: 0 Orders | Pause Targets
Target
Pause targets that are getting clicks but no orders.
Frequency: Once per day
Trigger:
/* ==== 0 Orders - Pause Keywords ==== This recipe is used to pause targets that are getting clicks but no orders. ==== Trigger ==== */ (over the lifetime // Date range selection orders = 0 // Order threshold and clicks > 30 // Click threshold and state = effectively enabled // State setting /* ==== Options ==== Remove starting "//" to enable option */ // and campaign name does not contain "lottery" // Keyword exclusion. Use this to exclude campaigns using keywords in your campaign name // and ad group name contains "close match" // Keyword inclusion. Use this to only include ad groups that contain specific keywords in your ad group name. ) /* === End Trigger=== */ /* ==== Action ==== Change Bid: Set State - Paused Daily Frequency */
Action: Set state to paused
5.0(123)
Download
6 downloads
Recipe 002: 0 Impressions | Targets
Target
Increase impressions on targets that aren't getting any impressions.
Frequency: Once per day
Trigger:
/* ==== Increase Impressions - Targets ==== This recipe is designed to increase impressions on targets that aren't getting any impressions. ==== Trigger ==== */ ( over the last 4 days // Date range selection impressions = 0 // Impression threshold and state = effectively enabled // State setting /* ==== Options ==== Remove starting "//" to enable option */ // and bid < $1.00 // Max bid setting. Adjust this to set the maximum bid this Recipe will increase to. // and campaign name does not contain "lottery" // Keyword exclusion. Use this to exclude campaigns using keywords in your campaign name // and ad group name contains "exact match" // Keyword inclusion. Use this to only include ad groups that contain specific keywords in your ad group name. // and campaign start date > 60 days ago // Set campaign start date exclusion. ) // and (over the last 90 days impressions > 0) // Only enables Recipe for keywords with past impressions /* === End Trigger=== */ /* ==== Action ==== Change Bid: Increase (%) *Weighted Bid Rounding Strategy Recommended Daily Frequency - Conservative: 2% - Moderate 4% - Aggressive 6% Weekly Frequency - Conservative: 15% - Moderate 25% - Aggressive 35% */
Action: Increase bid by 2
5.0(123)
Download
6 downloads
Getting Started: Recipes 101
Campaign
Learn what Recipes are, and how to use its powerful features. Recipes give you a powerful way to automatically perform actions (such as pausing a campaign, increasing bids, or lowering budgets) based upon certain criteria.
Frequency: After every data sync
Trigger:
/* Recipes --- Recipes give you a powerful way to automatically perform actions (such as pausing a campaign, increasing bids, or lowering budgets) based upon certain criteria. See our Recipes help article for the most up-to-date Recipe information: https://help.merchjar.com/blog/recipes Recipes are comprised of 4 components: - Source - Trigger - Action - Frequency */ /* Source --- Recipe sources are found in the "Look for" section when building a Recipe, and determines what will be evaluated by the Recipe trigger,and where actions will be applied. Each source has different actions that can be applied. Recipe triggers and actions can be applied to the following sources: - Campaigns - Ad Groups - Keywords - Targets // Campaign Sources Campaign source triggers look at the campaign level data and actions are applied at the campaign level. Campaign actions include: - Set State - Change Daily Budget // Ad Group Sources Ad group object triggers look at the ad group level data and actions are applied at the ad group level. Ad group actions include: - Set State - Change Default Bid // Keyword Sources Keyword source triggers look at the keyword level data and actions are applied at the keyword level. Keyword sources include any manual campaign keywords: - Exact match - Phrase match - Broad match Keyword actions include: - Set State - Change Bid // Target Sources Target source triggers look at the target level data and actions are applied at the target level. Target sources include any product and category targeting in manual targeting campaigns: - Product targeting - Category targeting And any targeting groups in automatic targeting campaigns: - Close match - Loose match - Substitutes - Compliments Target actions include: - Set State - Change Bid /* Triggers --- This section here is the trigger, which allows you to specify the exact criteria that your ads need to hit before you perform an action. Triggers are where the real power lies in Recipes, giving you complex and precise control over your automated actions. Triggers are composed of 3 parts: - Clauses - Expressions - Statements */ /* Clauses --- Clauses are the most granular part of Recipe triggers. These are composed of three parts: - A metric (such as sales, acos, or clicks) - An operator (such as >, <, or =) - A value (such as $10, or 20%) Combined - the metric, operator, and value make up a clause. A few examples of different clauses: sales > $10 acos < 20% clicks = 100 */ /* Expressions --- Expressions are made up with a time window and one or more clauses. The time window allows you to specify the time period you want to use when generating your metrics. The time window can be either: over the lifetime over the last X days where X is any number of days from 1 to 180. When using the "over the lifetime" time window, Merch Jar will use all of the data available in your account. When using the "over the last X days" time window, Merch Jar will only use the number of days specified to generate your metrics. A few example expressions: over the lifetime sales = $0 over the last 30 days acos > 50% The clauses in an expression can be grouped using boolean logic for more advanced functionality. A simple example of this would be: over the lifetime sales = $0 and spend > $50 over the last 45 days acos > 50% and spend > $50 Expressions also support nested boolean logic, allowing for even more advanced triggers. over the lifetime (sales = $0 and spend > $50) or (sales < $10 and spend > $200) over the last 15 days (sales = $0 or acos > $50) and (spend > $20) /* /* Statements Expressions can be grouped together using boolean logic to create a statement. This allows for more advanced functionality, such as comparing multiple time periods. A few examples: (over the lifetime orders = 0) and (over the last 30 days spend > $10) (over the lifetime (orders < 10 and acos > 50%) */ /* Comments Comments allow you to add notation to Recipe triggers that is not read by the trigger. Comments can either be inline or a block comment. */ // This is an inline comment. Type "//" to start a comment. Anything after "//" will not be read by the trigger. over the last 30 days clicks > 30 // Anything before "//" on a line will still be read by the trigger. /* This is a block comment Use block comments to comment on multiple lines of text. Start a block comment with "forward-slash asterisk" and end a block comment with "asterisk forward-slash" Anything between the start and end of block comment will not be read by the trigger*/ /* Constructing a Clause Clauses are composed of three parts: - A metric (such as sales, acos, or clicks) - An operator (such as >, <, or =) - A value (such as $10, or 20%) Combined - the metric, operator, and value make up a clause. A few examples of different clauses: sales > $10 acos < 20% clicks = 100 // Metrics Metrics are split into three categories - numeric, string based, and special. Numeric metrics have some sort of number attached to them, while string-based metrics are dealing with text of some sort. Special metrics have their own set of rules. // Numeric Metrics roi acos clicks impressions orders sales roas ctr cvr spend bid budget pages read estimated royalties // String Metrics campaign name ad group name // Special Metrics state (will only accept "enabled", "effectively enabled", "running", "active", "paused", or "archived" for values) // Operators --- // Numeric Operators: > >= < <= = != // String Operators: = != contains does not contain starts with ends with // State Operators: = != // Values --- // Numeric Values Numeric values can be any number, with decimal places. Currency symbols and percentage signs are support, so you can enter "$20.00" or "15.67%". Commas are not currently supported. // String Values String values can be any string, but it has to be wrapped in double quotes ("like this!"). */
Action: Set state to paused
5.0(123)
Download
6 downloads
Recipe 001: 0 Impressions | Keywords
Keyword
Increase impressions on keywords that aren't getting any impressions.
Frequency: Once per day
Trigger:
/* ==== Increase Impressions - Keywords ==== This recipe is designed to increase impressions on keywords that aren't getting any impressions. ==== Trigger ==== */ ( over the last 4 days // Date range selection impressions = 0 // Impression threshold and state = effectively enabled // State setting /* ==== Options ==== Remove starting "//" to enable option */ // and bid < $1.00 // Max bid setting. Adjust this to set the maximum bid this Recipe will increase to. // and campaign name does not contain "lottery" // Keyword exclusion. Use this to exclude campaigns using keywords in your campaign name // and ad group name contains "exact match" // Keyword inclusion. Use this to only include ad groups that contain specific keywords in your ad group name. // and campaign start date > 60 days ago // Set campaign start date exclusion. ) // and (over the last 90 days impressions > 0) // Only enables Recipe for keywords with past impressions /* === End Trigger=== */ /* ==== Action ==== Change Bid: Increase (%) *Weighted Bid Rounding Strategy Recommended Daily Frequency - Conservative: 2% - Moderate 4% - Aggressive 6% Weekly Frequency - Conservative: 15% - Moderate 25% - Aggressive 35% */
Action: Increase bid by 2
5.0(123)
Download
6 downloads
Viewing 7-12 of 13