Schedule your weekly ad reports and checks
Have the report ready before the meeting. For scheduled account changes, set the targets and limits first, then check what ran, what failed, and what was skipped.
On this page
First, choose what to schedule
Most of a marketer’s recurring work runs on a fixed schedule. Monday mornings you pull last week’s performance, every morning you check pacing and CPA anomalies, and on Fridays you shortlist the campaigns and creatives you’ll tune up next week.
Neuro’s scheduled jobs mean you don’t have to ask for the same thing in chat over and over. At the time you set, the AI pulls from your ad accounts against your reporting criteria, emails you the results, and—in Ad Operations Mode—can even push changes within the conditions you’ve saved.
| Good candidates for scheduling | Example | What to define first |
|---|---|---|
| Weekly performance report | Get Google Ads, Meta Ads, and GA4 performance emailed to you every Monday at 9 a.m. | Comparison period, key metrics, recipients, report format |
| Daily anomaly check | Every morning, surface campaigns with off-trend daily CPA, ROAS, or pacing | Anomaly thresholds, campaigns to exclude, items for a human to review |
| Ad Operations Mode actions | When conditions are met, push budget, bid, and campaign status changes | What to change, maximum change range, conditions under which nothing should run |
Keep analysis and operations separate
Scheduled jobs come in two modes: analysis mode and Ad Operations Mode. Analysis mode is for reading and interpreting results—pulling performance, diagnosing what drove it, drafting reports, running anomaly checks. Ad Operations Mode goes further, taking actions that touch your live ad accounts, like creating, editing, or pausing campaigns.
| Question | Analysis mode | Ad Operations Mode |
|---|---|---|
| What you hand off | Performance summaries, root-cause analysis, report drafts, anomaly checks | Operational actions like budget adjustments, bid changes, and campaign status changes |
| Must-have prompt details | Date range, data source, comparison basis, reporting order | What to change, max change range, exclusion conditions, how to report failures |
| What to look for in the email | Key takeaways, campaigns to watch, items for human review | Changes pushed, items skipped, items that failed |
| Recommended starting point | Recurring reports and checks | Recurring operations with clear conditions and limits |
Once Ad Operations Mode is on, changes can run at the scheduled time based on the instructions and conditions you saved. Don’t expect a chat-style flow where you approve every step. Before you save, a human needs to review what gets changed, the budget and bid limits, and the conditions under which nothing should run.
Spell out the execution scope in the prompt
A scheduled run cannot rely on someone being there to clarify the request. Define its targets and exclusions before saving. The thresholds below are illustrative, not recommended defaults; adjust them for conversion lag, target CPA, and budget.
Decide what the result email needs to tell you
- Whether this run succeeded or failed
- Which date range and metric rules it used
- Which campaigns need attention, and why
- In Ad Operations Mode, which changes were actually pushed and which were skipped
- Where to download any generated files
- What a human needs to check next
Neuro scheduled jobs email you on both success and failure. Success emails include the results and links to any generated files; failure emails include the reason it failed plus any partial output. To keep your team from asking the same questions later, lead with the bottom line and the review items at the top of the email.
Failures must be easy to fix
Promising to eliminate every failure in automation is a risky claim. Ad platform connections expire, permissions change, and external APIs sometimes reject only some of your changes. What matters is that failures don’t slip by silently—they get logged in a way a human can read and fix fast.
| Failure scenario | Marketer’s pain point | What to check in scheduled jobs |
|---|---|---|
| Ad account connection expired | No report shows up, or some platforms are missing | Look for connection issues in the failure email and execution log |
| Some operations changes failed | Some campaigns changed, others didn’t | Confirm success and failure items are clearly separated |
| Missing output | The job finished but there’s little to review | Check whether a drafted email report or partial output was saved to the log |
| Usage or plan limits | The job is enabled but runs get skipped | Check why this run didn’t execute |
In Ad Operations Mode especially, retrying isn’t always the right move—the same budget change could get applied twice. A second attempt may be fine in analysis mode, but in Ad Operations Mode it’s often safer to stop and log the failure.
Execution logs are where your team checks in
What matters in the scheduled-job list isn’t just whether each one is on or off. You need to see when it last ran, whether that run succeeded or failed, whether an email went out, and whether any files were generated.
- What the job name and prompt were
- Whether it ran in analysis mode or Ad Operations Mode
- Start time, end time, and total run time
- Success, failure, and email-delivery status
- Whether there were generated files or partial output
Related posts
Before AI changes your ad budget
How to review AI proposals for budget and bid changes, including approval settings and scheduled execution in Neuro.
How to ask AI when your ROAS numbers don’t match
Why attributed revenue can exceed actual sales, which dates and conversion definitions to align, and how to ask Neuro to investigate a ROAS discrepancy.
Five areas to check in an AI-assisted ad account review
Review goals, campaign structure, budget, conversion quality, and creative while separating verified findings from causes that need more evidence.
When AI groups campaigns incorrectly: check names and UTMs
Find campaigns whose names leave product groups or audiences unclear, then use settings, UTMs, and a mapping table to classify them.
Before you connect an ad account to Neuro
A guide to Neuro account connections, workspace access, default approvals and automatic execution, and AI API data policies.