#22a -- Impression Discrepancy 53% (Cavai 369,900 vs DV360 241,754)

Priority: High Status: In Progress Category: Delivery Raised by: Min Hein Kyaw, 22 May 2026

Problem

Cavai reports significantly more impressions than DV360 for the same campaign. The original #22 issue was a general discrepancy concern; this sub-item is a specific, high-magnitude case on a Cavai-built creative.

Kevin's Assessment (Discord)

For example when looking at this creative: https://my.cavai.com/creatives/52060-53141-54872-93399/build#design Our primary analytics which is known to double count impressions in mobile, reports about 2.4m impressions Analytics built specially for Humology reports about 1.4m impressions About week ago Humology reported about 1m impression on their side

So analytics built for them isn't too far off. Also including the fact, that creative has been live for quite some time after Humology sent their numbers and now me comparing ours

I think resolution for this is, that they should use the analytics we made for them

Data from Solmux Discrepancy Report

Creative: https://my.cavai.com/creatives/0-53141-54872-93399/build#design Date range: 2026-06-03 to 2026-06-22 (20 days)

Metric	DV360	Cavai
Impressions	944,389	2,110,215
Invalid Impressions (DV360)	53,722	--
Clicks	357	558

• Cavai counts 2.23x more impressions than DV360
• Discrepancy: 55.2%
• Even excluding DV360 invalid impressions (890,667 valid), discrepancy is 57.8%

However, Kevin notes the Bunny Analytics (built specifically for Humology) reports ~1.4m -- much closer to Humology's ~1m than the primary analytics' 2.4m. The Bunny Analytics layer was built to fix exactly this kind of mobile double-counting.

Cavai Feasibility Assessment

Can we fix this from our side? Partially -- and may already be "fixed" in the right analytics layer.

Kevin's key insight: Cavai's primary analytics is known to double-count on mobile. The bespoke Bunny Analytics layer (#24) was built to address this and reports numbers much closer to DV360.

Root cause analysis:

1. Cavai counts at CDN edge (earliest point) -- inherently higher than DSP counts
2. Primary analytics double-counts on mobile -- a known issue
3. Bunny Analytics (#24) corrects for this and is much closer to DV360 numbers
4. The remaining gap (1.4m vs 1m) can be explained by timing differences (creative still live after Humology pulled their numbers)

Resolution path: Humology should use the Bunny Analytics layer for their reporting, not the primary Cavai analytics. This is Kevin's recommendation.

Open Questions

1. Is Humology already using Bunny Analytics, or are they looking at primary analytics?
2. Can we make Bunny Analytics the default/only analytics shown for Humology workspace?
3. Is the remaining 40% gap (1.4m Bunny vs 1m DV360) still too large?

Next Steps

1. Confirm Humology is using Bunny Analytics (not primary)
2. If gap is still too large, Kevin needs to investigate further with the specific creative
3. Consider surfacing only Bunny Analytics for Humology in the reporting dashboard

Additional Data

• Min Hein (10 Jun) shared additional report and creative link with Haakon
• Checked invalid impressions -- confirmed they are minimal on Cavai side
• VCR/CTR comparison report also available (8 Jun 2026) with per-creative data

Bunny Analytics Technical Details

• Backend endpoints: GET /analytics/bunny/hourly-summary/:creative_id and GET /analytics/bunny/metrics/:creative_id
• Implementation: Direct Parquet queries via DuckDB in Application-Backend/start/routes/analytics.ts
• Hive-partitioned path: ${BUNNY_LOGS_PATH}/hourly_summary/*/*/*/*.parquet
• Impressions = COUNT(*) sessions -- different counting methodology from primary analytics
• Supports companion creatives via getCompanionCreativeIds() (extracted from VAST companion URLs)
• Full docs: Cavai-Documentation/src/DocumentationTexts/analytics/backend-analytics.md

Related Items

• #22 (general impression discrepancy)
• #24 (bespoke Bunny Analytics layer)
• #23 (low VCR -- related to counting methodology)
• Reporting Dashboard (should surface Bunny Analytics data)