My Revenue Proven numbers don't match LinkedIn Campaign Manager
Impressions, clicks, or spend figures in Revenue Proven look different from LinkedIn Campaign Manager for the same period. Company-level data aggregation, LinkedIn privacy thresholds, and different date window definitions explain most discrepancies.
You compare a campaign's impressions or spend in Revenue Proven against LinkedIn Campaign Manager and the numbers differ. The gap is sometimes small, occasionally significant.
Why this happens
Revenue Proven pulls engagement data at the company level using the MEMBER_COMPANY pivot of the LinkedIn Ad Analytics API. This is a different aggregation path from the campaign-level totals shown in LinkedIn Campaign Manager. LinkedIn applies privacy thresholds that suppress data for small companies, which can make company-level totals lower than raw campaign totals. Revenue Proven also deduplicates companies seen across multiple campaigns and date windows, and reports data within fixed preset lookback windows rather than arbitrary calendar date ranges.
How to fix it
- Align date ranges as closely as possible. Revenue Proven uses preset lookback windows of 7, 30, 60, 90, and 180 days from today, so an exact calendar date match in LinkedIn may produce slightly different totals.
- Expect company-level engagement totals to be lower than raw campaign totals. LinkedIn's privacy thresholds suppress data for companies below a minimum audience size, and that suppression is not visible in Campaign Manager's aggregate view.
- For spend figures, verify you are comparing the same currency. Revenue Proven shows costs in both local currency and USD. Check your currency setting under Settings if figures differ by a consistent multiplier.
- Understand that Revenue Proven deduplicates companies that engaged across multiple campaigns. A company that interacted with three campaigns is counted once in the company table, not three times.
- Accept a small variance as inherent to the two data views. Revenue Proven is optimized for account-level attribution, not for replacing LinkedIn's native campaign reporting.
Still stuck?
If the discrepancy is large (more than 20 percent) or you suspect a data quality issue, contact support with the campaign name, date range, and both figures. We can trace the specific API response to explain the gap.