The Journey Dashboard provides complete visibility into the health and performance of Journey integrations. It allows administrators to monitor API activity, identify potential issues, and review detailed execution logs to ensure leads are successfully reaching the system.
By providing real-time insight into integration activity, the dashboard helps reduce troubleshooting time and ensures that lead submissions do not go unnoticed.
Why This Feature Matters
When leads are submitted through websites, widgets, landing pages, or third-party integrations, it is important to verify that the information reaches the system successfully.
Without visibility into API activity, failed submissions, missing information, or configuration issues may remain undetected, potentially resulting in lost leads or incomplete customer data.
The Journey Dashboard helps you:
Monitor integration health in one centralized location.
Detect issues before they impact lead generation.
Identify incomplete submissions and warning messages.
Troubleshoot failed submissions quickly.
Improve data accuracy.
Prioritize journeys that require immediate attention.
Accessing the Journey Dashboard
To access the dashboard:
Navigate to My Journeys.
Select Dashboard.
The dashboard displays API activity and Journey performance for the previous 30 days.
Dashboard Metrics
The dashboard provides several key metrics that help monitor integration health.
Calls – Last 30 Days
Displays the total number of API calls processed during the past 30 days.
Success Rate
Shows the percentage of successfully processed submissions.
Failed Today
Displays the number of failed calls that occurred during the current day.
Last Lead Received
Indicates the most recent API call received by the selected Journey.
Understanding Integration Statuses
Each API submission receives one of three statuses.
Success
A Success status indicates that:
The lead was submitted successfully.
The contact was created or updated.
All required information was processed correctly.
Partial
A Partial status means the submission was processed successfully, but one or more warnings were detected.
Examples include:
Duplicate phone numbers.
Missing subgroup assignments.
Invalid subgroup values.
Non-critical validation issues.
Although the contact may still be created, reviewing these warnings is recommended.
Failed
A Failed status indicates that the system could not process the submission.
Common reasons include:
Missing required information.
Invalid field mappings.
Configuration issues.
Integration errors.
Failed submissions should be investigated to ensure leads are not lost.
Call Composition
The Call Composition section provides a visual breakdown of all API activity during the last 30 days.
This allows administrators to quickly identify:
Successful submissions.
Partial submissions.
Failed submissions.
Reviewing these trends can help detect recurring issues and improve overall integration performance.
Journeys Requiring Attention
The Journeys – Attention First section prioritizes journeys that contain warnings or failures.
Journeys with Partial or Failed executions appear first, allowing administrators to quickly identify integrations that require review.
This helps teams focus their attention on potential issues before they affect lead processing.
Reviewing Execution Logs
Selecting a Journey opens the Execution Logs page.
Execution Logs provide detailed information about each API submission, including:
Contact information.
Submission results.
Execution date and time.
Processing status.
Details
By clicking the View Details, you would see detailed event information.
Available filters include:
Status.
Date range.
Search criteria.
These filters make it easier to locate specific submissions.
Warning Messages
Partial submissions generate warning messages that explain what information requires attention.
These warnings help identify opportunities to improve data quality while confirming that the contact was still created successfully.
Best Practices
For optimal integration performance:
Review the Journey Dashboard regularly.
Monitor Partial and Failed statuses.
Investigate warning messages promptly.
Verify subgroup configurations.
Review field mappings after making integration changes.
Monitor high-volume lead sources closely.
Regular monitoring helps ensure that lead submissions continue to process successfully.