- Published
- Oct 29, 2026
- Updated
- Nov 1, 2026
- Reading time
- 12 min read
Prebid vs GAM: Audit hb_bidder Impressions and Revenue
Reconcile Prebid and GAM bidder reports by separating request keys, delivered line items, overlapping rows, price buckets and partner revenue.

In this guide (10 sections)
Do not treat an hb_bidder report row as proof that this bidder delivered the ad or earned the displayed revenue. Start by checking what the key describes, which orders and line items the report includes, and which metric it counts. Only then compare that population with the partner's delivery and revenue records.
A real publisher question about inflated hb_bidder reports asks whether GAM reports the Prebid key even when another demand source wins. A reply points to report order filtering, and the original poster confirms that suggestion helped. A separate Prebid-versus-GAM dataset question raises price-bucket configuration and unexplained differences.
These are older evergreen originals. They establish the reporting task, not a current incident or an acceptable discrepancy percentage. The useful investigation separates request metadata, selected delivery, report aggregation and partner accounting.
Define the four records you are comparing#
| Record | What it helps establish | What it does not establish alone |
|---|---|---|
| Prebid targeting on a request | Which bid information was sent to GAM | Which demand source ultimately served |
| GAM delivery record | Which selected line item or creative the named metric counts | The partner's finalized payable revenue |
| Key-value report row | Activity grouped under that report's key and scope | A distinct event for every row |
| Partner report or statement | The partner's recorded delivery or revenue on its stated basis | Identical coverage, timing or filters to GAM |
Keep each source's original export. Record the report name, selected metrics and dimensions, filters, dates, timezone, currency and extraction time. Name the inventory and integration versions included. A campaign-wide screenshot containing only “impressions” and “revenue” cannot expose these boundaries.
Define the bidder report population
Record the request keys, included line items and metric before comparing partner totals.
Use the tracking QA checklistOpens a practical guide. No email required.
Step 1: inspect what the request keys actually mean#
Prebid's key-value documentation identifies hb_bidder as the bidder code, hb_pb as the price bucket and hb_adid as the bid's rendering identifier. Top-price and send-all configurations produce different targeting sets; bidder-specific keys can accompany the top-bid keys.
Inspect your actual configuration and an authorized request trace. Do not infer the configuration from a historical setup guide or a partner's display name. Save the ad unit, size, bidder code, key names, values and the request to which they belonged.
A bid selected within Prebid still has to compete in the ad server. The presence of its targeting is therefore not a complete winner record. For a small supported test, compare the request targeting with the line item and creative that actually served. Use approved delivery diagnostics or a test environment; avoid repeatedly refreshing live ads to manufacture a sample. If custom page code instead selects and renders Prebid bids directly without an ad server, freeze the selected bid and trace its identifier into rendering. A later winning-bid query is a different observation from the original decision snapshot.
For publisher-authored content keys, trace effective GAM targeting and candidate eligibility before treating an unexpected selected line item as ignored targeting. A matching predicate can coexist with unrestricted eligible competitors.
On a GPT test page, the Google Publisher Console exposes targeting information, returned line-item and creative IDs, query ID and fetch count. Record those fields for the relevant slot and compare them with the request trace. A returned creative identifier still does not establish viewability or partner payment.
For an unexpected redirect or malicious-ad report, use the publisher incident evidence workflow. Preserve the available creative and query identifiers with the original observation; do not ask a visitor to click a suspicious ad to identify it.
Preserve that distinction on refreshed slots as well. Capture the keys sent on the specific request under investigation rather than a screenshot taken after several later auctions. Your engineering owner should identify the available request, auction and slot references and their scope. Do not join every event on one page to a single convenient bidder label. If those request keys depend on lazy auctions or SRA, trace lazy-auction and GPT request timing for that same slot cycle.
Step 2: restrict the report to the intended delivery#
Create a copy of the original report so the starting comparison remains reproducible. Include the relevant order, line-item and creative identifiers where compatible with the selected report. Separate the verified Prebid delivery population from other demand before comparing bidder totals.
Use stable IDs and the actual configuration inventory. A name containing “Prebid” can omit an older or newly created order; a broad key filter can include records outside the intended delivery population. Document the inclusion list and its effective period.
Google's targeting-key reporting guidance warns that otherwise all keys present on a matching request may be returned. It recommends targeted impression metrics for an order or line item's key-value delivery. That advice does not make every metric containing “targeted” a count of partner-paid impressions.
The current Interactive report metric reference describes Ad server targeted impressions in terms of requests for a targeted key-value pair. Save the exact definition alongside the column. For delivery reconciliation, verify the appropriate delivery metric and compatible dimensions rather than silently substituting a request-oriented measure.
Compare the copied report with and without the intended delivery filter. If the bidder-associated total falls, identify which removed orders or line items account for it. That is a population correction. It does not mean you recovered revenue, removed invalid traffic or fixed the underlying auction.
If the report cannot expose the required combination, keep the limitation explicit and request a supported export. Do not build an apparently precise bidder-payment table from dimensions and metrics that describe different populations.
Step 3: check whether rows overlap#
Even a correctly scoped report can be unsafe to total. Google's double-counting guidance explains that one event can appear under several key-values, placements, targeting elements or yield groups. Adding those rows can count the same delivery more than once.
Keep a compatible control report without the overlapping breakdown. Then compare individual slices with that control; do not assume that summing every displayed bidder-related or targeting row reconstructs the original total. Where permitted and available, request event-level evidence appropriate to the disputed grouping.
A useful overlap test is deliberately small. Choose one authorized sample with a known request and delivered line item. Inspect which rows represent it. If the same event appears in more than one row, describe those rows as overlapping labels, not multiple impressions.
Avoid changing several reporting dimensions at once. Preserve the original output, make one diagnostic change, and record which population or grouping changed. A lower total after a report edit can be correct without proving the earlier collection was duplicated.
Step 4: identify the key-value reporting mode#
The mode matters when a value is missing or unexpectedly zero. Google's current targeting-key documentation distinguishes the legacy Key-values dimension, Custom dimensions and Enhanced key-values. It says Enhanced key-values attributes an impression only to the first value per key in the request; additional values for that same key can show zero even when targeted and served.
Apply that caveat to the exact mode and actual request. It is not a statement that every bidder-specific Prebid key is discarded: distinct keys and multiple values of one key are different configurations.
Also check when the key became reportable and whether the value was defined. Google says reporting does not populate earlier dates before the key was enabled, and custom-dimension availability has its own prerequisites. A new reporting setting should not be presented as historical recovery.
Request the key's configuration and change history from the owner. When comparing periods across a change, label the coverage break. Do not alter the production targeting model merely to make a diagnostic report easier to sum.
Step 5: separate bid price, bucket rate and payable revenue#
Once the delivery population is credible, inspect the monetary basis. Prebid's price-granularity guide explains that bids round down into price buckets, including at configured caps. Rounding affects how the bid competes in the ad server; the bucket is not the partner's payment rate.
Save the original bid value, adjustments your implementation applies, the sent bucket, line-item rate, currency and the partner's stated revenue basis where these are available. Keep unavailable values unknown. A report calculated from configured ad-server rates needs a different label from a partner settlement statement.
Check whether each monetary amount is gross or net of applicable deductions and whether the same fees have already been removed. Preserve report maturity and any documented adjustments. Do not change bid adjustments, floors or granularities solely to force two revenue columns to match.
For a real change, coordinate the Prebid configuration and matching ad-server line items with their owners, then test the intended behavior. A price-cap mismatch can affect competition; it is a separate implementation question from an incorrectly scoped report. There is no universal bucket increment or discrepancy threshold that resolves both.
A hypothetical reconciliation in two stages#
Suppose a hypothetical report examines one bidder label, one inventory group and a completed interval. The controlled evidence identifies:
| Population | Count | Interpretation |
|---|---|---|
| Requests carrying the bidder's relevant top-bid targeting | 1,000 | Request metadata population |
| Matched deliveries from the intended Prebid line items | 600 | Scoped ad-server delivery population |
| Other demand deliveries among those requests | 400 | Not this Prebid bidder's delivered inventory |
| Corresponding partner-reported impressions | 580 | Partner's stated metric and coverage |
For this example, the 600 and 400 are mutually exclusive outcomes covering all 1,000 requests. Real reports require evidence before making that assumption.
Comparing 1,000 key-associated requests with 580 partner impressions creates a numerical difference of 420 across unlike units. Restricting the comparison to the defined delivery population leaves 20: 600 - 580. Relative to GAM's 600, that is approximately 3.33%.
The report correction explains 400 of the initial numerical difference under the constructed assumptions. It does not explain the remaining 20. Investigate event definitions, integration coverage, timing and exclusions; do not automatically classify the remainder as invalid traffic or lost money.
Now consider a separate hypothetical price-only example with 10,000 matched impressions, one currency, no fees or adjustments, and a constant bid of USD 2.73 CPM. Suppose the configured bucket and reporting rate are USD 2.70 CPM:
| Calculation | Illustrative amount |
|---|---|
| Rate-based value: 10,000 / 1,000 × USD 2.70 | USD 27.00 |
| Bid-price-based value: 10,000 / 1,000 × USD 2.73 | USD 27.30 |
| Numerical difference | USD 0.30 |
The same impression population can produce different calculated values. Neither figure establishes a real invoice or payment; actual commercial records determine the applicable settlement. Keep this example separate from the first population problem rather than applying a rounding explanation to missing impressions.
Choose the next action from the failed boundary#
| Finding | Useful next action |
|---|---|
| Bidder key exists on requests served by other demand | Correct the report's delivery scope and label the population change |
| Key-value rows overlap | Retain a non-overlapping control and inspect a supported detailed sample |
| Later values disappear in an Enhanced key-values report | Verify the exact request values and documented reporting mode |
| Counts align but calculated revenue differs | Compare rate, bucket, currency, deductions and settlement basis |
| Matched delivery counts still disagree | Trace the receipt and filtering handoff with each provider |
The ad-server impression discrepancy workflow covers that downstream receipt investigation. For a broader publisher earnings decline, use the traffic-stable revenue diagnostic. For billed amounts and applied corrections, retain the separate invoice reconciliation process.
For AdProof-measured campaigns, export the supported campaign report or permitted event records with explicit dates, timezone and filters. Compare that delivery population with the relevant reports while preserving unmatched scope. The anonymized fashion retail duplicate-counting case illustrates a separate counting-rule review, not Prebid revenue recovery. Request a demo to review the campaign measurement and export workflow; do not assume a direct Prebid connector or auction-level join.
Frequently asked questions#
Does hb_bidder mean that bidder won the final ad-server decision?
The key describes the bid information sent on the request. Verify the actual delivered line item and the report's population before assigning final delivery or revenue to the label.
Can I sum all key-value report rows?
Not when the grouping overlaps. One event may be represented by several rows. Use a compatible control total and the documented breakdown behavior rather than interpreting each row as separate delivery.
Why can a key's second value show zero impressions?
In the documented Enhanced key-values mode, only the first value for that key receives impression attribution. Check that this is the mode you used and that the request actually contained several values for one key.
Should I adjust bids until GAM and partner revenue match?
No general rule supports that change. First align delivery scope and establish each monetary basis. Change auction configuration only for a demonstrated configuration issue, with coordinated line-item setup and a controlled validation.
Research and scope#
Reviewed 29 October 2026. Forum originals are older evergreen questions; their suggested tolerances are not adopted as standards. Technical sources were opened from Prebid and Google. The report-copying sequence is an original diagnostic recommendation; both examples are hypothetical. No partner allegation, customer measurement, guaranteed savings or direct AdProof Prebid integration is claimed.
Define the bidder report population
Record the request keys, included line items and metric before comparing partner totals.
Use the tracking QA checklistOpens a practical guide. No email required.
