
Getting Started
Troubleshooting: Why Isn’t My Deal Showing Up?
Common reasons a CRM deal might not appear in your RevenueProven attribution data.
Troubleshooting: Why Isn’t My Deal Showing Up? is part of the authenticated Revenue Proven workspace. Use Measure > Attribution filters, CRM domain cleanup and Workspace > Connections sync status. There is no separate Unmatched Companies or Missing Domains report. The page is documented against the current production interface rather than a mockup or an obsolete navigation path.
What this guide covers
Attribution combines matched LinkedIn company engagement with CRM accounts and opportunities to calculate influenced pipeline and closed-won revenue. The controls and values shown depend on the signed-in workspace, its connected providers, plan entitlements, member role, and any data already synchronized or seeded for demonstration.
Use this article to understand the page’s purpose, where its data comes from, and the safest next action. Revenue Proven separates read-only analysis from explicit mutations so that opening a page never implies that an external write has occurred.
Current product workflow
Attribution combines matched LinkedIn company engagement with CRM accounts and opportunities to calculate influenced pipeline and closed-won revenue. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Set the engagement lookback, account, CRM provider and deal filters, then use Company Insights for account-level drill-down. Model thresholds and currency are workspace settings. Interface labels and availability follow the current plan, role, connection, and workspace context.
Shawn’s attribution data is real synchronized test-system data. Figures are not customer benchmarks, and lookback filters describe engagement context rather than every CRM event date. Confirm the active workspace and understand whether a control reads data, changes local configuration, or calls an external system before using it.
Data, access, and permissions
Shawn’s attribution data is real synchronized test-system data. Figures are not customer benchmarks, and lookback filters describe engagement context rather than every CRM event date. Real synchronized values can change after a scheduled sync, while seeded demo rows are deterministic examples and must not be presented as customer benchmarks.
Feature availability is enforced on the server. A button may be hidden or disabled when the workspace lacks the required plan, add-on, OAuth scope, account role, owner permission, or rollout flag. Team membership never bypasses owner-only write guards.
Operational guidance
Before changing anything, verify the active workspace, selected account, date range, provider filters, and saved configuration. If a screen looks incomplete, allow asynchronous charts and grids to finish loading and check Workspace > Connections for sync health.
Use read-only preview, filter, export, and drill-down controls freely. Treat controls labelled Save, Submit, Apply, Resume, Sync, Send, Publish, Delete, Reconnect, or Regenerate as state-changing actions and confirm their effect before continuing.

