Trigger
Read delivery
Every morning at 8, or when a metric crosses a value.
- Spend
- $1,842
- ROAS
- 1.74
- Frequency
- 2.8
Ad automation
Choose the accounts, schedule and report steps once. Adrails runs the workflow and sends its results to your chosen channel. Templates start switched off. Add automatic pauses only when you choose the rule and its limits.
Product view
Read account signals, open the affected campaign and keep each pause or change attached to the figures behind it.

Product workflow
A workflow reads the accounts, keeps the rows that cross your line, tells the team and pauses what should stop.
Trigger
Every morning at 8, or when a metric crosses a value.
Filter
The team decides what counts as an actionable exception.
Send
The rows and an agent's summary are posted where the team works.
Pause
Checked on the platform first, then paused and logged with its figures.
Illustrative workspace data. Values show the product flow and are not customer results.
Yes. A workflow with a Pause ads step pauses what crosses your threshold, and a Change budget step scales what performs, such as doubling the daily budget of ad sets past a ROAS of 3, within the accounts, the bounds and the limit per run you choose.
Meta Ads and Google Ads, one platform per step, so a workflow can read both. TikTok Ads is coming soon.
No. An agent step in a workflow only reads. Budget changes are prepared by the Media Buyer agent with their evidence and applied from the workspace.
Every hour. A threshold workflow fires at most once a day for each item that crosses the line.
Yes. A report can cover a selected group of accounts, mix Meta Ads and Google Ads and convert totals to the workspace reporting currency, on demand or on a schedule.
No. It reads connected attribution data such as Triple Whale next to the platforms' own figures and keeps the source of each metric.