Bulk Operations
Operations
Apply consistent changes across many campaigns without manual editing.
Overview
Bulk operations let you apply a single, consistent change across many campaigns, ad groups, keywords or extensions in one coordinated pass — without opening each item and editing it by hand. Instead of repeating the same adjustment dozens of times, you describe the intent once ("pause every campaign below 1.2% CTR", "raise tablet bid modifiers by 10% across the brand portfolio") and OpenAds identifies the affected entities, drafts the exact set of edits, and holds them for your review before anything touches the live account.
The outcome is a scoped, auditable change set: a clear list of every campaign or item that will be modified, the before-and-after value for each, and a single approval gate that executes them together. You gain the speed of automation and the safety of human sign-off, so large-scale housekeeping — budget resets, naming clean-ups, seasonal pauses, targeting alignment — happens in minutes rather than an afternoon of manual clicks.
When to use it
Reach for bulk operations whenever the same change needs to land across a group of campaigns and doing it individually would be slow or error-prone.
Applying a portfolio-wide budget change, for example lifting every performing campaign to ₹5,000 per day.
Pausing or enabling a cohort — seasonal campaigns, an underperforming region, or a retired product line.
Standardising bid strategies, device modifiers or targeting settings across similar campaigns.
Adding shared negative keywords or extensions to many campaigns at once.
Enforcing naming conventions or labels before a reporting cycle.
Example prompts
"Pause every campaign with CTR below 1% over the last 30 days."
"Set the daily budget to ₹4,000 for all campaigns labelled 'Core'."
"Increase daily budgets by 15% on every campaign with ROAS above 4."
"Add the shared negative keyword list 'brand-exclusions' to all search campaigns."
"Enable all campaigns in the 'Diwali' group and cap each at ₹8,000 per day."
"Apply +20% mobile bid adjustment across the South India regional campaigns."
"Rename campaigns matching 'Test_' to the 'Retired-2026' label and pause them."
What OpenAds prepares vs what you approve
OpenAds handles the analysis — matching your scope to real entities and reading their current settings — and the proposal — drafting the precise set of edits with old and new values shown for every item. Nothing is written to the ad platform at this stage. The approval is entirely yours: you inspect the change set, adjust the selection, and give explicit sign-off. Only then does OpenAds move to execution, applying the approved edits as a single batch and reporting the result. Analysis and proposal are automated and reversible; approval and execution stay firmly under human control, so a broad change can never run silently.
What to look at
Signal Why it matters What to check Match count Confirms the scope caught the right cohort Does the number of affected items match your expectation? Excluded items Reveals entities the filter skipped Any campaign that should have been included but wasn't Old vs new value Shows the exact impact per item Unexpectedly large jumps or drops in budget or bid Total budget delta Summarises the spend impact of the batch Aggregate daily spend change against your limit Validation warnings Flags edits the platform may reject Status conflicts, minimum-budget or policy issues Execution report Verifies the change actually landed Succeeded, failed and skipped counts post-approval
Common pitfalls & best practices
Scope too broadly. Test a filter on a small cohort first, then widen it once the match count looks right.
Blend absolute and percentage changes. A flat ₹5,000 budget and a +15% lift behave very differently across campaigns — keep each batch to one type of change.
Skip the excluded list. Always read what OpenAds left out; a mistyped label or threshold often hides there.
Ignore the aggregate impact. Check the total budget delta before approving so a portfolio-wide lift doesn't blow the daily cap.
Batch unrelated changes together. Group edits by intent so the audit trail stays clear and easy to reverse if needed.
The workflow, step by step
Define the scope. Tell OpenAds which campaigns are in play — by label, name pattern, performance threshold or an explicit list — so the change targets exactly the right cohort.
Pull the current state. OpenAds analyses the matched entities and reports their present values, giving you a baseline before any edit is proposed.
Describe the change. State the adjustment in plain language, whether that is an absolute value, a percentage shift or a status change.
Review the proposed change set. OpenAds returns a line-by-line preview showing each affected item with its old and new value, plus any items it deliberately excluded and why.
Refine the selection. Add or remove items, tighten a threshold, or split the batch if some entities need different treatment.
Approve execution. Give a single approval and OpenAds applies the whole set together, keeping the changes consistent and atomic.
Confirm the result. OpenAds reports which edits succeeded, flags any that failed validation, and records the change for your audit trail.
Run this workflow through your AI assistant.