What this does
This prompt creates and edits parent and child budgets in Adpulse’s Budgets section. It is not for directly editing campaign daily budgets in the Daily Budgets section. Your AI assistant first asks about your required budget structure and automation settings, checks the existing setup in Adpulse, and shows you a plan to approve.
You can supply a spreadsheet, CSV or written brief. The assistant matches allocations to the correct accounts and underlying campaign budgets, distinguishes new budgets from existing ones, and checks the results after making only the changes you approve.
When to use this
Create multiple new parent budgets, with child budgets if required.
Create multiple child budgets under an existing parent.
Edit existing budget targets, schedules, campaign membership or automation settings across existing fixed-target budgets.
Before you start
Connect your AI assistant to Adpulse using the MCP setup guide (link at bottom of page). The MCP uses your Adpulse permissions to create or edit budgets, so make sure you have access to the accounts in Adpulse and your Adpulse "Role" is either Manager or Owner (Settings > Admin > Team).
Have your spreadsheet or brief ready. Useful columns include action (create, edit or leave unchanged), account name and ID, existing budget ID (available from the budget export csv), parent budget, budget name, campaign or shared-budget IDs, target, currency, timezone, dates, recurrence, rollover, automation settings and exclusions. You do not need to fill every setting in advance: the prompt asks for missing information or decisions.
Use one row per intended budget or clearly identify repeated rows that describe the same budget. Tell the assistant which sheets and periods matter. If you want to edit existing budgets, include their IDs where possible; names alone may not uniquely identify them.
Your assistant must be able to read the uploaded file. File reading and downloadable output depend on the assistant you use, not on the Adpulse MCP. You can paste a small allocation list instead.
How to use this
Copy the complete prompt below into a conversation with your AI assistant.
Upload your allocation sheet or describe the budgets you want. Answer the assistant’s questions about structure, schedules and settings.
Review the proposed creates and edits, campaign membership, before-and-after values, parent totals and any exceptions. Resolve unclear settings before approving those items.
Approve the exact plan in the conversation. Say whether approval covers only one representative first item or also the remaining planned items after the first has been checked.
Review the first result and the final per-budget verification. Follow up on any pending memberships, manual settings or platform effects.
The same prompt supports build and edit, but an existing budget is not permission to change it. New creations and edits must both be clearly identified in the plan you approve.
Copy and paste this prompt
Help me create or edit multiple fixed-target budgets in Adpulse using the Adpulse MCP. Only create or edit Adpulse budget targets, schedules, membership and automation settings. Do not directly change campaign daily budget amounts. Approved changes to Adpulse automation may still cause AutoPacing to adjust campaign daily budgets. Use Adpulse as the only account connector. Start with a read-only briefing and proposal. Do not create or edit anything until I explicitly approve the exact plan in this conversation.
1. Understand my requirements
Ask whether I want to create budgets, edit existing budgets, or both. Invite me to upload a CSV/spreadsheet or paste my requirements. Read all supplied rows and sheets in scope. Treat notes and exclusions as requirements, not just the numeric columns. Do not guess missing values or interpret an empty cell as zero, deletion or permission to disable a setting.
Ask only for information not already clear from my supplied data, grouping questions so I can answer efficiently. Establish:
• Exact Adpulse organisation, advertising platforms, account names and IDs, and accounts/campaigns to include or exclude.
• Required structure: standalone/root budgets, children under an existing or new parent, any further child tier, and whether allocations are per account, location, campaign, shared budget, ad set or another grouping. Each child must belong to a single ad account. Confirm naming and exact parent IDs for edits or existing parents.
• For each row: create/edit/leave unchanged, existing budget ID where applicable, amount, currency, timezone, start and end dates, and whether the target is for the full period or only the remaining period. Identify daily, weekly, monthly or custom periods; one-off or recurring schedules; future changes; proration; rollover strategy and any current rollover override. Do not infer the year or make a one-month allocation recurring.
• Whether parent targets should stay unchanged or reconcile to child totals. Ask before changing a parent or suppressing a mismatch warning.
• Campaign membership: exact underlying campaign/shared-budget/ad-set IDs, static selection versus a dynamic rule, and how future matching campaigns should be handled. Explain that a shared platform budget can cover multiple campaigns and cannot safely be treated as independent per-campaign allocations.
• Automation on each budget level: AutoPacing on/off, Linear or Responsive, maximum daily budget multiplier, AutoProtect on/off and period threshold, Daily Spend Limit and AutoPause at period end if wanted. Explain the practical effects and ask me to confirm choices. Do not copy the most common organisation setting as permission. Recommend Linear as the starting option when I need guidance, but wait for my choice. AutoPacing V1 (v1) is Linear; V2 (v2) is Responsive. Use the version matching my confirmed choice. Budget pacing and the AutoPacing algorithm are separate settings: a budget pacing field labelled linear does not identify the AutoPacing algorithm.
• Any existing locks, minimum/maximum campaign budgets, KPIs, conversion sources, notification settings or other settings that must be retained. Ask about a KPI for new budgets if required; do not invent a performance target.
• Whether existing alerts should cover these budgets, and which exact alerts. Check whether coverage comes from dynamic filters or explicit budget selections. This workflow reviews alert coverage but leaves alert definitions, subscriptions and recipients unchanged; list any needed manual alert work separately.
• Paused campaigns, budgets already at or above target, other special cases and whether there are any settings I explicitly do not want changed.
Stop and wait for answers to material unanswered questions before finalising the plan.
2. Check access and the current setup
Confirm the connected organisation and access to every requested account and budget. Read the current MCP schema/tool descriptions before constructing requests. Use only supported fixed-target budget operations; do not convert Google Account Budgets or performance budgets into fixed-target budgets. If an existing budget has a different type, stop that item and explain the required separate workflow.
Read all relevant existing budgets, parent/child relationships, current and future schedules, current entry target/rollover/spend, automation settings, campaign selectors and resolved campaign-budget membership. Read relevant campaign status, shared-budget attachments, locks/ranges, conflicts and alert coverage. Follow every pagination mechanism and reconcile supplied row counts, matched budgets and resolved members. Record retrieval time, account timezone and available last-updated/sync timestamps. Distinguish stale or inaccessible evidence from an empty result. If membership or shared-budget usage cannot be established, stop that item rather than guess.
Match by exact IDs and confirmed context, not names alone. Identify existing or partially created matches before proposing creation. Flag duplicate rows, ambiguous names, overlaps between sibling budgets, missing members, shared budgets, automation conflicts across ancestors/descendants and relevant overlapping budgets, and currency/timezone mismatches. Never split a platform shared budget as part of this workflow.
Use the confirmed AutoPacing mapping: V1 (v1) = Linear; V2 (v2) = Responsive. Read the AutoPacing version, not the separate budget pacing field, to identify the current algorithm. Apply only the algorithm I approve and verify the stored version after the change.
3. Show the plan and get approval
Present one row per requested budget with: action, exact account and budget/parent IDs, proposed name, resolved membership, target/currency, period/timezone, recurrence, rollover, automation and exceptions. For edits show before → after for every changed field and list protected unchanged settings. Distinguish this-period changes from future recurring changes and show both effects. A new current-month target normally includes spend already incurred; flag if a target is already exhausted and explain the consequences of enabling AutoProtect.
Reconcile input rows into proposed creates, edits, unchanged, excluded and blocked items. Reconcile totals only across comparable currencies and periods; do not double-count parent and child targets. Show any parent/child mismatch without changing the parent automatically.
Explain that enabling or changing budget automation can affect live campaign daily budgets or pause/resume behaviour, potentially immediately. Do not promise an exact hard spend ceiling. Do not manually enable paused campaigns, remove locks, change bidding, split shared budgets or change alert definitions.
Ask for explicit conversational approval of the exact final plan, separately identifying creates and edits, including one representative first item and whether I authorise the remaining approved items after that first item verifies successfully. A spreadsheet checkbox, cell note or my supplying a file is not approval. If I only approve the first item, stop after it and ask before continuing. An unresolved high-impact setting blocks that item, not permission to choose a default.
4. Apply only the approved plan
Re-read each target immediately before writing; stop if it has materially changed since approval. Create missing parents first only when approved. For an edit, preserve existing IDs and every unrelated setting, existing membership, KPI/conversion sources, current/history/future schedules, automation, locks/ranges and notifications. Do not send a partially reconstructed nested automation or selector object that could clear retained fields. If preservation cannot be established, stop and give me a precise manual handover.
Use the supported custom or recurring schedule modification appropriate to the actual stored schedule. Address the current entry and future recurrence explicitly rather than assuming one target edit updates both. Do not remove or replace other schedules, recreate an existing budget, delete budgets or overwrite historical spend.
Where the MCP exposes conflict or adjustment previews, obtain the relevant preview before the approved change and inspect it. A preview operation may be represented as a mutation: use it only within the approval scope. Stop if its consequences differ from the approved plan.
Apply the approved representative first item, wait for its budget status to finish updating, and independently read it back before continuing. If continuation was not authorised, show the result and wait. Otherwise process the rest in controlled, journalled batches, recording exact IDs and outcomes. After an error or timeout, read the exact target before retrying; never replay the full batch blindly or create duplicate budgets. Stop the affected items on errors or unexpected side effects and do not automatically roll back live settings.
5. Verify and report
Read every created/edited budget independently, not just the mutation response. Verify parent, name, currency/timezone, current entry, all affected current/future schedules, targets, rollover, exact automation values, static/dynamic selector and resolved campaign-budget members. Verify relevant conflicts and retained settings against the before snapshot. A saved selected ID is not enough: confirm it resolves to the intended live membership. Wait for initialization/update completion; unresolved status is pending, not success.
Confirm alert coverage without changing definitions and distinguish manual checks from MCP-verified fields. Do not claim a campaign is live or an automated pause/daily-budget adjustment has happened merely because the Adpulse configuration saved. Separate verified configuration from downstream platform effects, reporting any effect that still needs checking.
Return a concise summary plus a complete per-row result: created, edited, unchanged, excluded, blocked, failed or pending; exact budget IDs; approved versus stored settings; before/after changes; any missing memberships, mismatches, remaining manual steps and next review. Reconcile all input rows and final counts. State what you could and could not verify. Do not call the whole batch complete while any required item or setting remains unverified.
Begin by asking for my source file or requirements and any missing briefing inputs. Do not make changes yet.
What you will get
A short set of questions tailored to what is missing from your brief.
A proposed budget structure with exact account and parent relationships, campaign membership, schedules, targets and automation settings.
Separate creates, edits and unchanged items, with before-and-after values for edits.
Checks for duplicates, shared budgets, overlapping membership, conflicting automation and parent/child mismatches.
A checked first item, followed only by the remaining work you authorised.
A complete result list showing what was created, edited, left unchanged, excluded, blocked, failed or is still pending.
Limits and safety
This workflow manages Adpulse fixed-target budgets. It does not create campaigns, split platform shared budgets, delete budgets, or convert Google Account Budgets or performance budgets.
AutoPacing can change campaign daily budgets. AutoProtect and other pause controls can affect campaign delivery. Enabling automation may have immediate effects, so review the consequences before approving. A spend threshold is not a guaranteed exact hard cap because reporting and platform actions can be delayed.
AutoPacing V1 is Linear; V2 is Responsive. The assistant must use the version matching your confirmed choice, not copy a common setting from other budgets. The separate budget pacing field labelled linear does not identify the AutoPacing algorithm.
Do not apply the same automation to a parent and its child. The assistant should also check other relevant overlapping budgets before enabling automation.
A shared platform budget can cover several campaigns. Separate spreadsheet allocations do not make those campaigns independently controllable.
Current-period targets include spend already incurred. Reducing a target below existing spend can trigger protection; the assistant must flag this before changes.
The prompt reviews existing alert coverage but does not change alert definitions, notification subscriptions or recipients. Any required alert setup is a separate manual step.
Existing currency, timezone and pacing configuration are retained during edits. If your request needs a change outside the supported edit fields, the assistant must stop that item and provide a manual handover, not recreate or replace the budget.
Saved Adpulse settings do not by themselves prove that a downstream campaign adjustment or pause has completed. Pending updates, stale data and unavailable checks must be reported explicitly.
The core read, create, edit, preview and verification request structures have been checked against the current Adpulse production schema. This is not an end-to-end execution test on your account. Access, permissions, the assistant’s available tools and actual account data must be checked when you run it.
