All Docs
a blue background with lines and dots

Attribution

The Customer Journey Account Timeline

The Customer Journey view shows every LinkedIn ad touchpoint and CRM milestone for a single account in chronological order, giving you full visibility into how deals develop and a ready-made proof artifact for sales and leadership.

2 min read

The Customer Journey Account Timeline is part of the authenticated Revenue Proven workspace. Customer Journey is available when the workspace has the required attribution and pixel data. Use Measure > Customer Journey and CSV export; there is no PNG export control. The page is documented against the current production interface rather than a mockup or an obsolete navigation path.

What this guide covers

Customer Journey brings LinkedIn engagement and CRM opportunity milestones together for one matched company. 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

Customer Journey brings LinkedIn engagement and CRM opportunity milestones together for one matched company. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Customer Journey page showing an account timeline, paid performance radar, filters, and CRM context
Customer Journey page showing an account timeline, paid performance radar, filters, and CRM context. Captured from /dashboard/customer-journey.

Select a company, provider and presentation mode, then compare impressions, clicks, engagement, conversions and CRM milestones. The available export is CSV. Interface labels and availability follow the current plan, role, connection, and workspace context.

Shawn’s journey values are real synced test-system data. Missing lead milestones or inconsistent upstream aggregates should be interpreted as source-data limitations. 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 journey values are real synced test-system data. Missing lead milestones or inconsistent upstream aggregates should be interpreted as source-data limitations. 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.