- Published
- Oct 25, 2026
- Updated
- Oct 30, 2026
- Reading time
- 19 min read
CTV Impression Discrepancies: How to Find the Missing Count
CTV publisher and agency impression counts do not match? Follow a practical investigation of SSAI beacons, reporting scope, invalid traffic, and missing events.

In this guide (13 sections)
Your publisher reports one million CTV impressions. The agency reports 750,000. Both teams check their setup, insist it looks right, and send screenshots of totals that still disagree.
When the purchased device class is disputed, reconcile the app identity with the reported device class and retain the unclassified portion.
The useful question is where the two systems stop counting the same events. This guide gives you a sequence for finding that boundary, a worked reconciliation, and an evidence template you can send to your publisher, agency, ad server, or measurement provider.
The problem is real: in an August 2025 discussion on r/adops, a publisher described agency counts running 20–30% below its own CTV reporting. That is one reported experience, not an industry benchmark. The investigation below uses current technical documentation rather than treating the thread's suggested causes as a diagnosis.
Start here: five checks before changing a tag#
If you need a first action today, work through these checks in order:
- Match the reports. Use the same campaign, placements, creative IDs, reporting interval, time zone, and data maturity.
- Name the event. Ask what actually triggers each system's impression: an ad decision, a segment request, a playback signal, or a received tracking call.
- Compare receipt before filtering. Find out whether the buyer received the event and then excluded it, or never received it at all.
- Find the affected slice. Break the gap down by app, device family, SSAI provider, creative, and hour. Start with the slice losing the most impressions.
- Trace a controlled playback. Follow one authorized test session from ad selection through beacon receipt and final classification.
Do not disable invalid-traffic filtering to make the totals agree. Export the excluded counts and reason codes where available. Agreement produced by removing a quality control does not explain the original difference.
Investigate the gap in CTV impressions.
Align the counting event, delivery path and reporting window before comparing totals.
Discuss video measurementA short inquiry to scope relevant options; no campaign access is needed.
Agree on what an impression proves#
CTV means internet-delivered video viewed on a television. Server-side ad insertion, or SSAI, places advertising into the stream before it reaches the player. A tracking beacon is a request that tells another system an event occurred.
There are several observable steps between selecting an ad and a viewer seeing it. A single dashboard label can conceal those distinctions.
| Record | What it can establish | What it does not establish by itself |
|---|---|---|
| Ad decision or VAST response | A system selected or returned an ad | The player requested, rendered, or completed it |
| Ad present in a stitched manifest | The session was given a playback plan containing the ad | The player reached that part of the stream |
| Ad segment request | A player requested media associated with the ad | Every requested frame appeared on an active screen |
| Tracking endpoint receipt | A measurement system received a particular beacon | The event passed validation or was included in the final report |
| Client playback signal | The integrated player reported a defined playback event | A person watched attentively or the event qualifies under every vendor's policy |
| Filtered impression | The record met that system's counting and filtration rules | Another system used the same rule or measured the same population |
The MRC's August 2021 SSAI and OTT guidance, page 7 applies client-initiation, invalid-traffic filtration, and begin-to-render requirements to CTV video impression measurement. It also calls for disclosure of measurement limitations. A server decision alone should therefore not be described as independent proof that an ad appeared on a TV.
Implementation still matters. AWS MediaTailor documents that its server-side beacons depend on ad segment requests. Loading a manifest alone does not trigger them, but prefetching actual ad segments can trigger them before playback. That describes MediaTailor's behavior; ask other SSAI vendors to document theirs.
Write a one-sentence counting definition for each report. For example: “This total contains accepted impression beacons from these placements, after the listed filters, assigned to this reporting day.” If a partner cannot provide that definition, you have found your first verification gap.
For the broader vocabulary, use our guide to impressions, views, reach, clicks, and conversions.
Step 1: make the two reports comparable#
Save both original exports before making changes. Record the export time and configuration so that a later refresh does not silently replace your starting evidence.
Use a completed reporting interval that both partners consider sufficiently processed. Do not invent a universal waiting period: ask about ingestion delays, late-event treatment, and subsequent filtration adjustments.
| Comparison field | What to confirm |
|---|---|
| Time interval | Exact start and end, including time zone and daylight-saving offset where relevant |
| Time basis | Event time, arrival time, or the platform's documented reporting time |
| Scope | Matching campaign, line item, placement, creative, and inventory environment |
| Metric | Impression versus start, completion, request, or viewable impression |
| Filtration | Gross, received, invalid, deduplicated, or net; request definitions for each |
| Coverage | Whether the buyer's tracker was deployed on every included placement |
| Data maturity | When the report was exported and whether counts can still change |
| Exclusions | Test traffic, slates, unfilled opportunities, unsupported integrations, or house ads |
Google Ad Manager's discrepancy guide starts with matching dates, time zones, and included ads, and excluding unfilled impressions. Those are useful checks before investigating CTV-specific behavior.
Keep the sign and denominator visible:
Publisher-relative shortfall = (Publisher count - Buyer count) / Publisher count
(1,000,000 - 750,000) / 1,000,000 = 25%
Buyer-relative excess = (Publisher count - Buyer count) / Buyer count
(1,000,000 - 750,000) / 750,000 = 33.3%
Both percentages describe the same pair of totals. Agree on one convention before comparing trends. If the buyer count is zero, do not calculate a buyer-relative percentage; report the absolute difference and investigate the missing path.
Step 2: find the slice responsible for the loss#
A campaign average can hide one broken device integration. Build a comparison by dimensions available in both systems, starting with app or inventory source, device family, creative, and time interval. Add SSAI provider, app version, or delivery mode when the records support them.
When the dispute is TV versus phone or tablet delivery, compare the device classifications explicitly. An app name or CTV campaign label does not resolve the hardware category, and unknown classifications should remain in the matched population.
Use an explicit mapping between partner IDs. Two fields called “creative ID” are not necessarily from the same identifier system. Keep an unmapped bucket rather than dropping rows that do not join.
Here is a hypothetical example after the reporting scope has been aligned:
| Device group | Publisher | Buyer | Missing count | Publisher-relative shortfall |
|---|---|---|---|---|
| Group A | 400,000 | 390,000 | 10,000 | 2.5% |
| Group B | 400,000 | 220,000 | 180,000 | 45% |
| Group C | 200,000 | 140,000 | 60,000 | 30% |
| Total | 1,000,000 | 750,000 | 250,000 | 25% |
Group B accounts for 72% of the missing impressions: 180,000 divided by 250,000. Start there. That identifies an investigation priority, not the cause. A common characteristic could be the device, its app version, its SSAI integration, or the supply assigned to it.
Rank slices by missing count as well as percentage. A tiny placement with a 90% shortfall can matter less to the campaign than a large placement with a 15% shortfall. Review both high-loss slices and small samples where percentages are unstable.
Step 3: separate missing beacons from excluded impressions#
Ask the receiving measurement provider for three distinct quantities, where its reporting permits them:
- Impression tracking requests received before validity decisions.
- Records excluded, split by reason and processing stage.
- Accepted impressions included in the report being compared.
If the provider does not expose a raw-receipt count, document that limitation. An accepted-impression total alone cannot distinguish transport loss from downstream filtering.
If received events are removed for screen state or inactivity, separate observed TV-off evidence from inactivity editing. Obtain the signal source, coverage, rule and overlap with other exclusions before assigning the missing count to transport loss or fraud.
This distinction is especially relevant with Campaign Manager 360. Google states that its reported impression and click counts already reflect filtering. A publisher's pre-filter count and an agency's filtered count answer different questions.
Follow the evidence to the next owner:
| Observation | Next investigation |
|---|---|
| Publisher has an event, but no outgoing beacon is logged | Beacon configuration, event trigger, or whether that event required a beacon |
| Sender logs an attempt, but receiver cannot find a receipt | Endpoint mapping, DNS/TLS failures, timeouts, redirects, or delivery logs |
| Receiver has the event, but excludes it | Reason codes, vendor integration requirements, and classification evidence |
| Receiver accepts it, but it is absent from the export | Reporting scope, ID mapping, time assignment, or processing lag |
| The same logical opportunity is counted repeatedly | Duplicate beacon ownership, retries, or identity and deduplication rules |
A successful HTTP response is evidence about transport to an endpoint. It does not prove that the event later became a valid, billable impression. Ask which system produced the response and how its receipt ID connects to the reporting record.
Step 4: inspect the SSAI handoffs#
Create a small ownership map for the affected inventory. Identify who requests the ad, resolves VAST wrappers, substitutes macros, stitches the media, fires each tracking event, and receives each callback. Hybrid integrations need this map just as much as fully server-side ones.
Our SSAI verification guide explains that architecture in more detail. For this investigation, concentrate on the boundary where the first count exists and the second disappears.
Check the final tracking request
Inspect the actual request emitted in an authorized test session, not only the original tag supplied by the agency. Check the final destination, resolved campaign and creative identifiers, relevant macros, timestamp, and the request's sender.
Compare the final VAST response and wrapper chain with the tracking configuration used during playback. Look for URLs lost during wrapper resolution, incorrect substitution, or a configured tracker that was never handed to the component responsible for firing it. The IAB Tech Lab VAST specification is the reference for the ad response and expected player behavior.
Verify the vendor's server-side integration requirements
Do not treat “forward the client IP” as a complete server-side integration recipe. Each receiving vendor can impose additional requirements.
For example, Campaign Manager 360's server-side support documentation describes an onboarded integration with Google-issued certificate authentication, eligible tag types, and a designated server-side endpoint. It also specifies forwarding available client IP and user-agent information through documented mechanisms. Google explicitly notes that URLs within its VAST XML do not need the same server-side-domain rewrite.
Have the integration owner verify the requirements for the exact call type. Changing every URL or adding one header without checking the supported workflow can introduce a second problem. Send only identifiers and privacy signals permitted for the integration; missing data should remain missing rather than being fabricated.
If the receiver flags SSAI traffic as invalid or unknown, separate recognized servers from device-context evidence. Confirm the actual evidence and classification policy instead of treating server recognition as proof of valid playback.
Check retries, duplicate ownership, and caching
Ask whether both the player and the SSAI service fire the same impression tracker. Then check what happens when a player retries a segment, switches bitrate, resumes playback, or restarts a session.
The presence of repeated segment requests does not prove repeated impression counting. MediaTailor documents per-session beacon deduplication, including repeated segment requests associated with retries and bitrate changes. Verify the actual platform behavior before attributing the gap to duplication.
Check cache behavior separately for manifests, media segments, and tracking routes. Media delivery can benefit from caching while session-specific tracking must preserve its intended event semantics. Use logs and vendor configuration guidance to establish whether caching suppressed or repeated a tracking call.
Step 5: investigate privacy and measurement coverage#
Consent can affect serving or measurement, but a 25% gap does not prove consent caused it. Compare otherwise similar, permitted test cases and examine the actual privacy parameters received by each vendor. Determine whether an event was not sent, rejected, measured with limited signals, or excluded from a particular report.
Likewise, distinguish an impression-measurement gap from a viewability-measurement gap. Completing a video and meeting a viewability definition are separate measurements.
Avoid the blanket claim that CTV cannot support viewability. IAB Tech Lab's Open Measurement documentation describes CTV support, including native integrations and expanded Samsung/LG support. Availability still depends on the device, app, SDK, vendor, and implemented signals. An inventory label saying “CTV” is not enough to establish coverage.
Ask for a support matrix for the campaign's actual inventory:
| Question | Evidence to request |
|---|---|
| Does impression tracking work here? | Supported beacon path and a successful test event |
| Does viewability measurement work here? | Applicable integration, measurable population, and limitations |
| Does the report cover the whole campaign? | Deployment coverage by placement and device |
| What happens with restricted signals? | Documented processing and reporting behavior |
An unmeasurable exposure should remain labeled unmeasurable. Do not turn it into either a confirmed view or a confirmed failure without evidence.
For location-specific disputes, use our separate workflow for verifying whether ads ran in the right geography. A location disagreement and an impression-count disagreement may share an integration issue, but they need separate tests.
A worked reconciliation of a 25% gap#
The following numbers are illustrative. They are not AdProof customer results, expected loss rates, or recommended tolerances.
Suppose the publisher's initial count is 1,000,000 and the buyer's accepted count is 750,000. After reviewing exports and event evidence, the teams assign the difference as follows:
| Component of the difference | Impressions | Share of initial publisher count | Evidence required |
|---|---|---|---|
| Duplicate publisher records | 40,000 | 4% | Repeated logical events under an agreed identity rule |
| Events outside the agreed reporting window | 20,000 | 2% | Timestamps and time-zone normalization |
| Placements outside the buyer tracker's deployment scope | 30,000 | 3% | Placement mapping and tag deployment records |
| Required callbacks demonstrably not sent | 60,000 | 6% | Event-to-callback audit in the affected population |
| Received events excluded by buyer filtration | 70,000 | 7% | Receiving-side exclusions and reason codes |
| Still unexplained | 30,000 | 3% | No verified explanation yet |
| Total difference | 250,000 | 25% | Mutually exclusive categories |
After removing duplicates, window differences, and scope differences, the comparable publisher population is 910,000. In this example the buyer received 820,000 before filtering and accepted 750,000 afterward. The remaining 90,000 receipt difference comprises 60,000 demonstrated missing callbacks and 30,000 unresolved events.
The original 25% headline therefore becomes two operational investigations: a confirmed callback problem and an unresolved remainder. The 70,000 filtered records need a reason-code review; their existence does not establish that the filtration was either correct or incorrect.
Count each event in one reconciliation category. Deduplicate first, align window and scope next, and examine receipt and filtration on the remaining population. Otherwise, the same record could be counted as both a duplicate and an invalid impression, making the waterfall appear more complete than it is.
Do not extrapolate a small diagnostic sample into an exact campaign-wide loss without a stated sampling method and uncertainty. If you have only aggregate exports, label a numerical explanation as a hypothesis until event evidence or another defensible check supports it.
Run a controlled test and verify the repair#
Use an authorized QA placement that follows the affected production delivery path. Record its device family, app version, SSAI mode, creative, and privacy state. A desktop VAST preview alone does not reproduce a connected-TV app integration.
For each scenario, inspect the configured event sequence and track the same test opportunity across the sender and receiver:
- Play through a complete ad under normal conditions.
- Exit before the ad begins, then test an exit during the ad.
- Exercise supported resume, restart, and seek behavior.
- Where the test environment permits it, observe a network retry or bitrate switch.
- Compare supported privacy states and device families without changing several variables at once.
Before declaring a fix, establish the expected result with the vendor. For example, a repeated segment fetch should not automatically create an extra logical impression; the applicable session and replay rules must say what counts as a new opportunity.
Retain the before-and-after tag versions, release time, sender logs, receiver confirmation, and accepted/excluded outcomes. Then compare a completed post-change reporting interval using the original scope and denominator. Confirm that reducing the gap did not merely reduce tracking coverage or remove filters.
Test success establishes that the repaired path works in the tested cases. A production reporting comparison is still needed to establish how much campaign-wide loss remains.
If the ad itself fails to load, trace VAST wrapper and media timeouts before treating the symptom as an impression reconciliation issue.
Copy this evidence request to your partners#
This template is a request for diagnostic evidence. It does not assume every vendor exposes event-level data. Ask partners to identify unavailable fields and suggest an equivalent verification method.
Campaign and incident:
- Campaign, placement, and creative IDs, with cross-platform mapping
- Affected app/device family, app version, and SSAI provider
- When the difference started and any corresponding deployment/tag change
Report comparison:
- Exact interval, time zone, export time, and processing status
- Publisher count and its event/filter definition
- Buyer received, excluded, and accepted counts where available
- Signed difference, denominator, and largest affected slices
Delivery evidence:
- Authorized test session reference and event timestamps
- Original tag and final resolved VAST/tracking configuration
- Component responsible for each beacon and its triggering event
- Sender request outcome and receiver receipt/reference
- Filtration reason or reason the event is missing from the report
Resolution:
- Confirmed finding, supporting evidence, and owner
- Proposed change, version, and release time
- Test outcome and post-change reporting comparison
- Remaining unexplained count and next action
Use a secure exchange for diagnostic logs. Remove credentials, signed playback tokens, full consent strings, and unnecessary device or network identifiers from general support documents. Keep only the permitted data needed for the investigation.
Frequently asked questions#
Is a 20–30% CTV impression discrepancy normal?
It is a reason to investigate, not a diagnosis. Google's CM360 discrepancy guidance describes discrepancies up to 20% as normal within its documented context and asks for additional evidence for larger gaps. That is not a universal CTV acceptance threshold or permission to ignore a new loss. Compare the same population, review the applicable agreement, and investigate abrupt or concentrated changes.
Which count should we trust: the publisher or the agency?
Start by identifying the event, scope, and filtration behind each number. The higher total may include duplicates or a broader population. The lower total may reflect legitimate exclusions or missing measurement. Neither direction establishes correctness. Billing decisions also depend on the agreed measurement terms and documented dispute process.
Can SSAI beacons be legitimate if they come from a data center?
Yes, legitimate server-side workflows exist. The important question is whether the sender uses the receiving vendor's supported integration and preserves the required context. A data-center source alone is not sufficient evidence to diagnose the campaign, and whitelisting all server traffic is not a sound repair.
Does a high video completion rate prove the impressions are valid?
No. Completion, impression validity, measurement coverage, and viewability are different dimensions. Investigate how completion events were generated and which population supplied the denominator. A clean-looking completion rate does not explain missing impression receipts.
Can independent measurement resolve the dispute?
It can add useful evidence when its integration covers the affected delivery path and exposes clear counting definitions, exclusions, and limitations. A third total without a traceable methodology can create another disagreement. Ask what the service directly observes and what remains unknown.
Does the same investigation apply to SSAI audio?
The receipt-versus-filtration distinction is useful for audio too. A reader investigating an SSAI audio campaign described a large impression gap even after comparing filtered and raw totals. Start with the actual audio event definition, reporting scope, beacon sender, receiver receipts, and exclusions. Then trace a supported audio test session through that integration. Do not apply CTV screen visibility or video playback criteria to an audio campaign, or assume one platform's server-side requirements apply to another. For the podcast-specific workflow, keep downloads, ad delivery and confirmed plays separate and preserve the provider's counting contract.
Once delivery counts reconcile, compare linear and streaming audience overlap on a common identity basis before evaluating purchase lift.
Put the reports next to the evidence#
The deliverable from an investigation should be a reconciled population, an explained portion of the difference, a named owner for each confirmed fault, and a visible unresolved count. A narrower, evidenced finding is more useful than an assurance that discrepancies happen.
For a broader campaign audit, follow our delivery verification guide. Review AdProof's independent measurement approach and supported measurement workflows, or request a campaign review to discuss the delivery path and evidence your team needs.
Sources and research notes#
For a narrower investigation, use the guides to ad-server impression reconciliation, GAM versus DoubleVerify geo discrepancies, viewability report differences, and missing VAST viewability events. If the received counts agree but accepted counts do not, review invalid-traffic denominators and evidence and pre-bid versus post-bid verification outcomes.
Researched on 25 October 2026. The worked examples, diagnostic tables, and evidence-request template are original illustrative material. The Reddit discussion supplies the user problem; technical claims draw on the primary sources below. Product documentation can change, so verify the requirements for your exact vendor integration before modifying a live path.
- MRC: Server-Side Ad Insertion and OTT Guidance, August 2021, especially measurement guidance on page 7.
- IAB Tech Lab: Digital Video Ad Serving Template and Open Measurement SDK.
- Google: Investigate Ad Manager report discrepancies.
- Google: How Campaign Manager 360 counts impressions and clicks.
- Google: Server-side support in Campaign Manager 360.
- Google: Click and impression counting discrepancies.
- AWS: Server-side tracking timing and caching behavior.
- AWS: MediaTailor server-side tracking features and capabilities.
Investigate the gap in CTV impressions.
Align the counting event, delivery path and reporting window before comparing totals.
Discuss video measurementA short inquiry to scope relevant options; no campaign access is needed.
