All Help Articles

FAQ

How does Revenue Proven attribute LinkedIn ads to revenue?

Revenue Proven links LinkedIn ad engagement at the company level to CRM deals, revealing which campaigns touched accounts that later became pipeline or closed revenue.

2 min read

Revenue Proven uses company-level ad engagement data from the LinkedIn Ad Analytics API, combined with your CRM deal data, to calculate which campaigns influenced each account before they appeared in your pipeline or closed as revenue. The attribution is based on a match between the LinkedIn organization that engaged with your ads and the company record in your CRM.

The matching process

After each sync, Revenue Proven runs a three-phase matching algorithm. First it tries an exact domain match between the LinkedIn organization website and the CRM company domain. If that fails, it attempts a URL-normalized match that strips subdomains and trailing paths. Finally, for companies still unmatched, it applies a fuzzy name-similarity algorithm capped at your top 5,000 unmatched accounts to avoid false positives.

  • Phase 1: Exact domain match (highest confidence)
  • Phase 2: Normalized URL match (strips www, paths, ports)
  • Phase 3: Bigram fuzzy name similarity (lowest confidence, user-configurable threshold)

What counts as influence

A campaign is considered to have influenced an account when at least one engagement (impression, click, or other paid interaction) from that account appeared within any of the five lookback windows: 7, 30, 60, 90, or 180 days before the deal was created or closed. You can adjust which lookback windows matter for your sales cycle length in the attribution settings.

What Revenue Proven does not do

Revenue Proven does not write back to LinkedIn or your CRM. All attribution is computed inside Revenue Proven and surfaced on your dashboard. No contact-level LinkedIn data is ever stored. Engagement signals are company-level only, which is the data LinkedIn provides through the standard Marketing Developer Platform.

Current help workflow

This answer was refreshed against the current Revenue Proven product and its exact /dashboard/attribution 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.

Current product screen relevant to faq-how-attribution-works
Current product screen relevant to faq-how-attribution-works. Captured from /dashboard/attribution.

Use this screenshot as the route-specific visual reference for “How does Revenue Proven attribute LinkedIn ads to revenue?”. 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.