Allow “Active Date Range” as a Trigger Condition
K
K
When creating an automation, have the option to enter a “date range” as a trigger condition for an automation.
For example, if an automation has an “active date range” of 10/1 to 12/31 (Oct 1 to Dec 31) then it would only be active and running during those calendar dates. Otherwise, the automation is switched off until the next date cycle. If this trigger is left blank, then by default the automation is active every day.
This would allow a user to create an automation that follow seasonal trends or events. This trigger condition would be very beneficial for Q4 trends where many expect a boost in metrics (such as orders, clicks, impressions, etc) where their current automation isn’t set up for. Therefore, they are forced to manually turn off or edit the current automation and create a new one altogether. Thus defeating the “automation” part.
Additionally it would allow a user to create special automations for specific events such as Prime Day or Black Friday. Usually these dates are announced ahead of time so you could prepare early without needing to manually turn on/off other automations.
Currently, I’m sure you could work around this by assigning very specific priority values and trigger conditions, but even so, it would still have a chance for an unwanted automation to execute. It would be easiest if automations can be active and inactive during a given date range.
I hope I was able to convey the request properly but please feel free to ask for more details. If others agree or have ideas to improve on this, please comment!
S
Scale Insights
Thank you for posting, K ! I have a few more questions for you:
- What specific seasonal trends or events do you foresee using the 'active date range' trigger for, and how frequently do these occur?
- Are there any specific metrics or outcomes you would like to track or achieve by using the 'active date range' trigger?
- How do you currently manage automations for seasonal trends or events, and what challenges do you face with the current setup?
K
K
Scale Insights
- Most of my products for example, actually have lower sales during Q4. It is an outdoor product with a boost during the spring and summer months. With the "active date range" trigger, I could create specific bidding rules for each quarter/month that is based on my historical data trends.
A quick and rough example, not related to my data:
Q1...
Active Date Range: Jan 1 - Mar 31
Performance Criteria: ACOS >= 40%, Clicks >=10, etc
Days to Analyze: 30 days (maybe this value should probably be within the active date range too?)
Action: Target ACOS 30%, max bid increase/decrease 10%
Q2-Q3 (Historically high sales date range)...
Active Date Range: Apr 1 - Sept 30
Performance Criteria: ACOS >= 50%, Clicks >=15, etc
Days to Analyze: 30 days (maybe this value should probably be within the active date range too?)
Action: Target ACOS 40%, max bid increase/decrease 25%
Q4 (historically low sales date range)...
Active Date Range: Oct 1 - Dec 31
Performance Criteria: ACOS >= 30%, Clicks >=5, etc
Days to Analyze: 30 days (maybe this value should probably be within the active date range too?)
Action: Target ACOS 20%, max bid increase/decrease 5%
It would be a headache to manage seasonal automations using rule priority values and would interfere with strategies that use advanced rule stacks with different "days to analyze". You also run the risk for an unwanted automation to trigger due to outlier performance if bidding rules are active all at once.
- Overall, it would be nice to have finer control over which automation rules are active without having to manually turn on/off or edit existing rules. Again, this is especially helpful for seasonal products, and/or those with strong historical data.
- Currently, I manually turn off or edit existing automation during date ranges with lower expected sales. If I don't take manual action, then we experience terrible off-season performance because our automations are taking action on performance meant for the peak-season, and vice-versa. I'd like my automations to be automated throughout the year and believe an "active date range" would solve this.