For supply-side publisher teams
Bidhalo vs manual ad-decision review
Compare Bidhalo’s documented, connector-scoped decision review with a manual review process that has no shared event log. Manual practices vary by team and tools.
Bidhalo
A documented, connector-scoped workflow for reviewing ad decisions.
Manual / unlogged review
The specific case where there is no shared event log. Manual processes and retained records vary.
Detailed breakdown
Compare what matters
Scroll horizontally on smaller screens
| Capability | Bidhalo | Manual / unlogged review |
|---|---|---|
| Decision record | ||
| Bid-level decision flowScope this behavior to connectors listed as bid-level. | For connectors listed as bid-level, the documented flow reasons over the BidRequest, returns the clearing price in a full BidResponse round-trip, and writes the agent decision to the audit log before the exchange clears. This does not establish that every action is logged. | In this unlogged-review case, there is no shared event log. Teams depend on whatever notes, exports, or console history their process retains; this does not describe every manual review. |
| Review context | ||
| What the available record supports | The security page describes audit records as append-only, attributable, and replayable, with a SHA-256 comparison against a stored baseline. That supports review; it does not by itself prove cryptographic immutability or certification. The FAQ says bid-level visibility does not establish that every action is tamper-evident or replayable. | Without a shared event log, reconstruction depends on notes, exports, or console history that the team’s tools and process retain. Retention and reconstruction vary by team. |
| Action boundaries and coverage | ||
| Connector depth and action boundary | Coverage depends on the listed depth: protocol-native is a full signal round-trip; audit-stream is a one-way log feed with no live agent action on bid responses; bid-level is a full BidResponse round-trip; reporting-only reflects partner metrics and does not act on bids. Agents may rebalance only when the connector supports it and policy bounds permit; otherwise they can skip and escalate. | Available actions and evidence depend on each team’s tools and process. This comparison makes no claim that all manual reviews are unlogged or retain the same history. |
Evidence reminder
Review the source pages for scope and detail
Connector depth defines what is documented. Suspected security or service incidents can be reported to Bidhalo; the team will acknowledge the report and coordinate investigation, and affected customers are contacted through the agreed channel. The operational page does not publish uptime, support hours, or a response-time SLA.