My Revenue Proven numbers don't match LinkedIn Campaign Manager
Impressions, clicks, or spend figures in Revenue Proven look different from what LinkedIn Campaign Manager shows for the same period. Attribution windows, currency conversion, and data aggregation explain most discrepancies.
You compare a campaign's impressions or spend in Revenue Proven against LinkedIn Campaign Manager and find the numbers are different. The gap is sometimes small, sometimes 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. Some differences arise from how LinkedIn attributes member activity to companies, how Revenue Proven deduplicates companies across lookback windows, currency conversion timing, and the fact that Revenue Proven shows data within specific lookback windows (7 to 180 days) rather than arbitrary date ranges.
How to fix it
- Match the date range in Revenue Proven to the same range in LinkedIn Campaign Manager. Revenue Proven uses preset lookback windows (7, 30, 60, 90, 180 days from today), so an exact calendar date match in LinkedIn may show slightly different totals.
- Understand that company-level engagement data is aggregated across all members of a company, and LinkedIn applies privacy thresholds that suppress small companies. This can cause the company-level total to be lower than the raw campaign total.
- For spend figures, Revenue Proven shows costs in both local currency and USD. Check your currency settings under Settings to ensure you are comparing the same currency.
- Remember that Revenue Proven deduplicate companies seen across multiple campaigns and date windows. A company that engaged with three campaigns is counted once in the company table.
- Accept a small variance as inherent to the two different data views. Revenue Proven is optimized for account-level attribution insight, not for replacing native LinkedIn 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.