Budget Change Requests
Review, record, and verify paid-media budget or bid changes with the current execution boundary.
Last reviewed July 13, 2026
The Budget workspace can show campaign entities and record proposed changes to supported budget or bidding fields. It is a planning and audit workflow, not a production ad-platform executor.
What Is Available
- a normalized view of imported campaign entities where source data exists;
- current budget or bid values captured by the integration;
- permission checks before a change request can be recorded;
- a pending change-log entry with before and after values;
- decision context for later review.
The imported hierarchy varies by platform. Always confirm the actual budget-owning entity in the platform before making a change.
What Is Not Available
The current change-request endpoint does not send the edit to Google Ads, Meta, TikTok, or another advertising platform. A request with a pending status means Vendo recorded the proposal. It does not mean the provider accepted or applied it.
Likewise, accepting an optimization recommendation records the decision; it does not execute the recommended budget shift.
Safe Change Procedure
- Open Data → Measurement → Budget.
- Confirm the platform, account, campaign entity, currency, and budget period.
- Review the current value against the platform UI.
- Record the proposed value and reason in Vendo.
- Obtain approval from the budget owner.
- Apply the approved change directly in the advertising platform.
- Reopen the platform and verify the saved value.
- After the next data sync, compare Vendo’s imported value and record the outcome.
For large or high-risk changes, take a timestamped screenshot or export before and after the edit and document a rollback threshold.
Permissions
The connected app must carry the relevant campaign permission before Vendo will record the request:
| Change | Permission family |
|---|---|
| Budget amount | Adjust spend |
| Bid amount, strategy, or target | Adjust bids |
| Active or paused state | Campaign toggle |
These checks prevent an unauthorized request from entering the log. They do not turn the request into an upstream API call.
Troubleshooting
| Symptom | Check |
|---|---|
| Entity is missing | Source connection, last sync, account selection, and provider hierarchy |
| Edit is forbidden | Connected-app campaign permissions |
| Request remains pending | Expected with the current non-executing endpoint |
| Platform value differs | Whether a person applied the approved change upstream and whether Vendo has synced since |