Data Coverage Checklist Before Reporting

Attribution numbers lose credibility the moment a stakeholder spots a missing deal or a company that should appear but does not. Running this checklist before sharing any report confirms your data coverage is solid and your numbers are defensible.

This checklist applies to all plan tiers. Items that reference features available only on Growth and above are noted individually.

The five-point checklist

In the left sidebar, open Connections (under the Workspace group) and confirm all active ad accounts are connected and selected.
Verify won-stage mapping is correct for every CRM pipeline.
Check that a recent sync has completed successfully.
Select the lookback window that matches the question you are answering.
Make sure the date range is explicit in any report or export you share.

Sync status panel showing pipeline phases and progress — The Connections page shows each data source's sync status and last-synced time.

Each checkpoint explained

Ad accounts: in the left sidebar, open Connections (under the Workspace group) and confirm every LinkedIn Ad Account your team currently spends on is selected. Attribution for any unselected account is missing from the report.
Won-stage mapping: for HubSpot, confirm each pipeline maps to the correct won stage. The default is Closed Won, but renewal and expansion pipelines may use a different stage. For Salesforce, confirm the won stage matches the stage your team calls Closed Won. Mis-mapped stages are the most common cause of incorrect influenced revenue figures.
Sync recency: check the sync status panel on the dashboard or the Connections page for a recent completion timestamp. A stale timestamp means the dashboard is showing data from hours or days ago.
Lookback window: a 7-day window answers what attributed in the last week, not what pipeline marketing influenced this quarter. Pick the window that matches the time horizon of the claim you are making.
Date range in the report: always include the exact date range in the report title or header. "Last 30 days" without a fixed range becomes meaningless when the report is opened a week later.

Best practices

Run this checklist before every external report, not just the first one. Ad accounts get added, CRM pipeline stages get renamed, and syncs occasionally lag. These five checks catch all of it.
Build the checklist into your reporting template so whoever prepares the report runs through it as a standard step.
If you share reports regularly, review sync health and won-stage mapping weekly so gaps do not surface during a live presentation.
Include the exact lookback window and sync completion date in every shared report header so readers understand the boundaries of the data.

Common mistakes

Sharing a report without checking the last sync timestamp. Data that is 48 hours stale can misrepresent a fast-moving quarter.
Using a 30-day lookback to answer a last-quarter question. Match the window to the question, not to the most recent data.
Omitting the date range from a shared export. Influenced pipeline is meaningless without a time boundary. Always include the specific period in the report title or header.
Forgetting to check won-stage mapping after a CRM admin renames or reorganizes pipeline stages. A renamed won stage breaks attribution for that pipeline silently.
Citing companies with a lower-confidence match indicator without reviewing them first. Lower-confidence name-based matches are usually correct but worth confirming before including in a leadership report.

FAQ

How do I know if a sync has completed recently?

The dashboard home and the Connections page both show the last sync completion timestamp. If the timestamp is older than 25 hours, a daily sync may have been delayed. You can trigger a manual sync from Connections at any time.

What does a lower-confidence match indicator mean?

A lower-confidence match indicator means Revenue Proven matched the LinkedIn company to a CRM account using company name or fuzzy matching rather than a direct domain match. These matches are usually correct but worth a spot-check before citing them in an external report.

My report covers a calendar quarter but no single lookback window aligns to it. What should I do?

Revenue Proven's lookback windows are rolling, not calendar-aligned. For a precise quarterly report, use a 90-day window that covers the quarter and note the exact start and end dates in your report methodology.

What is won-stage mapping and where do I configure it?

Won-stage mapping tells Revenue Proven which deal stage in your CRM represents a closed sale. It is configured on the Connections page, under your Salesforce connection's Won Stages settings. If your CRM has multiple pipelines with different won stages, you can set a mapping for each pipeline individually.

Troubleshooting

Pipeline value shows zero across all accounts: check that your won-stage mapping is correctly configured on the Connections page, under your Salesforce connection's Won Stages settings, and that your CRM connection is still Active.
A large company you know is in your pipeline does not appear: confirm the company engaged with one of your LinkedIn campaigns during the selected lookback window. No engagement in the window means no attribution record.
Matched company count looks too low: verify all active ad accounts are selected on the Connections page and that your CRM has company records for the accounts you would expect to see.
The last sync timestamp is more than 24 hours ago: trigger a manual sync from Connections. If the sync fails, check that both LinkedIn Ads and your CRM connections show Active status.

For more on how attribution matching works, explore the Attribution section of the docs. To understand lookback windows and how to pick the right one, see "Reading the Attribution Dashboard." For sync troubleshooting, see "Run Your First Attribution Sync."