FAQ
Which advertising platforms does Revenue Proven support?
Revenue Proven is purpose-built for LinkedIn Ads, using LinkedIn's Marketing API to pull company-level engagement data across multiple lookback windows for attribution.
Revenue Proven is purpose-built for LinkedIn Ads. It connects to one or more LinkedIn Ads accounts via OAuth and uses the LinkedIn Marketing API to pull campaign data and company-level engagement metrics.
What LinkedIn data Revenue Proven uses
- Campaign Search API to discover all campaigns for the connected ad account
- Ad Analytics API with company-level pivot to find which organizations engaged with your ads
- Organization Lookup API to resolve organization IDs to company names and websites
- LinkedIn Ad Library (for Competitor Intelligence, requires r_ad_library scope approval)
- LinkedIn Media Planning API for forecast integration in the Media Planning tool
- LinkedIn Ads API for Ads Manager status mutations and Ads Composer draft publishing
Attribution lookback windows
Revenue Proven runs attribution across five lookback windows simultaneously: 7, 30, 60, 90, and 180 days. This means a company that saw your ad up to 180 days ago can still be attributed to an influenced deal, which is important for B2B sales cycles that extend over many months.
Other ad platforms
Revenue Proven does not currently support Google Ads, Meta, or other ad platforms. LinkedIn-first attribution is the core product focus. If multi-platform support is important to you, note this as a feature request through the contact form.
Current help workflow
This answer was refreshed against the current Revenue Proven product and its exact /dashboard/connections route. It is written for the Shawn Brown demo workspace, whose pages contain real connected-system data in some areas and seeded examples in others.

Use this screenshot as the route-specific visual reference for “Which advertising platforms does Revenue Proven support?”. Labels, plan gates, roles, asynchronous loading, permissions, and available controls can vary with the signed-in workspace.
When troubleshooting, first confirm the active workspace, selected account, connections, date range and entitlement. Treat Save, Send, Sync, Publish, Resume, Reconnect and Delete controls as state-changing actions, and consult the current route before relying on older screenshots or navigation instructions.

