Use connected Sales deals, Hub analytics and workspace status
Move between the native deal workspace and Hub reporting while keeping campaign counts, sales metrics and connection status in their proper context.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Hub → Sales → Deals workspace; Reporting → Hub analytics; Data & connections → Connected workspace
PermissionNative Sales CRM access for deals; Hub visibility and relevant resource permissions for Hub reports
Before you begin
Check which native modules are active in this workspace. The Hub connects existing tools; its status page does not provision external ad or social accounts.
Follow these steps
- Open Deals workspace when the Sales CRM integration is available. Switch between its board and list as needed.
- Create or edit a deal through the supported Sales form, respecting required stage fields and approvals when moving it. Use saved views for repeatable authorised filters.
- Open Hub analytics to review accessible resource, activity, enrolment and delivery information. Open the source resource or queue for the supporting detail.
- For campaign-specific outcomes, open the campaign’s Results tab and inspect its current attached assets.
- Use Connected workspace to inspect available native adapters and the separate outbound-email boundary.
Fields and options
- Sales source
- Deals, pipeline stages, approvals and saved views remain owned by Sales CRM.
- Hub metrics
- Counts reflect the accessible Hub data and the report’s scope. SMTP acceptance is not a read, click or sale.
- Connections
- Reports which supported native tools are available; missing modules remain unavailable rather than being silently installed.
Rules and limits
- Hub reports do not provide external ad spend, automatic multi-touch attribution or certified return on investment.
- Campaign budgets are planned values; different currencies must not be added as if they were one amount.
- Social publishing is managed through the separate Social Media Automation module.
Check the result
- Trace one reported count to its source items and confirm the same access scope.
- Check a stage change in the original Sales deal and its recorded history.
If something does not look right
- If Deals workspace is absent, check Sales CRM activation, entitlement and native permissions.
- If counts differ between users, compare ownership, native access and filters before assuming data loss.
Common questions
Can Connected workspace create social developer apps?
No. Configure social apps through the Social module and the provider’s developer console.
Does an accepted email count prove revenue?
No. It means SMTP accepted that message; attribution and revenue need separate evidence.