Every feature built around
operator accountability.
BidGuard does not automate your ads. It sits between operators and ad spend, catching anomalies, requiring approvals, and keeping every action auditable before anything touches a live account.
01 · guardrails
Budget guardrails
Four deterministic guards run from evidence, not guesses. Each one evaluates a specific signal and proposes an action — with an evidence packet — before anything touches the account.
CPA Guard — cost-per-action threshold breach
ROAS Guard — return-on-ad-spend degradation
Pacing Guard — overspend velocity detection
Circuit Breaker — emergency kill switch
Active guardrails
3 armedCPA Guard
Brand Keywords$42.10 / $38.00 target
Pacing Guard
Performance Max112% of daily budget
ROAS Guard
Meta Retargeting1.8x / 3.0x target
02 · connections
Platform connections
Google Ads and Meta Ads stay separate. Each connection has its own OAuth state, account discovery, sync health, and workspace assignment. No platform bleeds into another.
Google Ads OAuth with account discovery
Meta Ads OAuth with account discovery
Sync freshness gate — stale data fails closed
Reauth detection without silent fallback
Connected platforms
Google Ads
connectedMeta Ads
connectedSlack alerts
planned03 · buckets
Bucket posture board
Group ad accounts by strategy intent. Buckets are the unit of control — each has a guardrail set, a readiness posture, and an assigned account. The posture board shows all Buckets in one view.
Group campaigns by strategic intent
See risk and cap posture across all accounts
Rule attachment at the Bucket level
Cross-Bucket view for agency operators
Bucket posture
4 buckets · 2 platformsBrand Keywords
Google Ads · 2 rules
Performance Max
Google Ads · 1 rule
Meta Retargeting
Meta Ads · 3 rules
Cold Audiences
Meta Ads · 0 rules
04 · approvals
Approval queue
Every proposed action needs explicit approval. Evidence packets show exactly what triggered the proposal, what data was used, and what will happen if approved. Nothing runs autonomously.
Evidence packet with every proposal
Approve, reject, or request more data
Approval history tied to audit events
Sandbox dry-run before live execution
Pending approvals
1 pendingPause Campaign: Brand Keywords
CPA Guard · Google Ads
05 · audit
Immutable audit ledger
Connector changes, rule edits, approvals, action applications, and reverts all write a permanent audit event. Every incident can be traced back to a specific state, time, and actor.
All connector changes recorded
Rule edits and approval decisions logged
Action evidence preserved in each event
Revert actions write their own audit entry
Audit log
livePaused Brand Keywords — CPA Guard
operator · 09:41CPA Guard proposal approved
operator · 09:40CPA Guard threshold exceeded
system · 09:38Google Ads sync — 14 entities
system · 09:35Google Ads OAuth refreshed
operator · 09:2006 · alerts
In-app alert inbox
Spend anomalies, readiness blocks, and rule evaluations route to the alert inbox. Each alert carries retry state, delivery metadata, and links back to the source event.
Spend anomaly detection
Readiness block notifications
Rule evaluation summaries
Delivery retry with error tracking
Alert inbox
2 unreadCPA threshold exceeded
Brand Keywords · Google Ads
Sync health degraded
Meta Ads · last sync 4h ago
Action applied and audited
Pause approved · Campaign paused
ready to connect
Six feature areas, one operator cockpit.
Connect your Google Ads and Meta Ads accounts, prove readiness, and let BidGuard watch for the anomalies you care about.
Guardrails
Connections
Buckets
Approvals
Audit ledger
Alerts