Issue Summary:
Some users experience discrepancies and confusion when using LeadConduit’s Reports to reconcile lead performance with the Flow Dashboard. Differences arise from the way transactions are tracked (e.g., submission-based vs. feedback receipt–based) and from multifaceted lead events such as add-ons and integrations. This guide explains how to troubleshoot report discrepancies, verify flow configuration, and understand the underlying billing events.
Impact:
Inaccurate reporting can affect billing accuracy, cost forecasting, and revenue reconciliation. Account managers, finance teams, and technical administrators may see unexpected high or low transaction counts or feedback figures that do not match their operational expectations.
Common Errors, Causes, and Fixes
| Symptom | Root Cause | Description | Quick Fix |
|---|---|---|---|
| Mismatched transaction counts | Different time-base used for Dashboard vs. Reports | Dashboard counts are tied to the lead submission date, while Reports count events (e.g., feedback) based on receipt date. | Confirm and use a consistent time frame (submission vs. feedback) when comparing metrics. |
| Unexpected high transaction count | Multiple add-on/integration events triggered for single lead | High‑quality leads can trigger several sub‑events (source event, multiple add‑ons, integration steps, feedback) causing a cumulative higher billed transaction. | Review your flow design and adjust rule thresholds or filter conditions to prevent unintended duplicate events. |
| Missing or delayed feedback entries in Reports | Lead filtering or feedback delay | Filtering steps may stop a lead early or feedback may be recorded later than the submission date, causing reporting mismatches. | Check and adjust filter/acceptance criteria; allow an appropriate delay before analyzing recent data. |
| HTTP errors affecting feedback reporting | Recipient system server errors | HTTP 5xx or timeout errors can block the successful posting of feedback events, resulting in fewer recorded transactions. | Investigate error logs for recurring HTTP 5xx/timeout responses and adjust retry settings accordingly. |
Step‑by‑Step Troubleshooting
Step 1 – Verify Flow and Source Configuration
- Open your LeadConduit flow and switch to the Sources step to confirm that each lead source is configured with the correct acceptance criteria, filter rules, and pricing guidelines.
- Ensure that every intended billable action is included in the flow—this includes source events, add-on events, integration steps, and feedback events.
- Verify that no filters or step criteria are inadvertently blocking billable events, and check that any external service integrations (such as TrustedForm or SuppressionList) are correctly applied.
- Confirm that the transaction definitions in your flow (including ping events for RTB) align with your billing and reporting requirements.
Expected Result:
Your flow should clearly display a comprehensive sequence where each billable step is correctly configured. Both the Dashboard and the Report views will then accurately reflect all intended lead events.
Step 2 – Compare Report Data with Transaction Logs
- Navigate to the Reports section in LeadConduit and open a report that details transaction counts, feedback figures, and pricing metrics.
- Verify that the report’s time frame settings match your intended analysis—note whether it groups data by lead submission date or feedback receipt date.
- Cross-reference the report data with the detailed Event Logs from the Flow Dashboard to identify any timing or filtering differences.
- Identify discrepancies such as missing feedback events or extra add-on events, and determine if these are due to delays (e.g., conversion feedback arriving weeks after submission) or configuration issues.
- Adjust reporting filters or extend the time window as necessary to capture delayed feedback and ensure proper comparison between views.
Expected Result:
The compiled report should mirror the breakdown of all lead events visible in the Event Logs. Any differences should be explainable by the reporting time reference—submission versus feedback receipt—and adjustments should harmonize the reported data.
Error Codes & Meanings (If Applicable)
| Error Code | Meaning | Typical Fix |
|---|---|---|
| [ERR_5XX] | HTTP 5xx error response on a feedback sent event | Verify recipient API connectivity, review server logs for repeated errors, and adjust network or retry settings. |
| [ERR_TIMEOUT] | Request timed out during an integration or feedback event | Increase timeout duration for affected integrations or feedback submission; ensure the recipient’s API is responsive. |
FAQ
What causes discrepancies between Dashboard and Report metrics in LeadConduit?
The Dashboard reports on lead performance based on submission dates, while Reports track feedback events by the date they are received. This can lead to differences—especially when conversions or returns occur well after a lead’s submission.
How can I resolve unexpected high or low transaction counts?
Verify your flow’s configuration to ensure no unintended filters or duplicate add-on events are in place. Compare the timing of feedback events between the Dashboard and Reports, and adjust reporting windows if necessary.
Why are HTTP error responses affecting my feedback data?
HTTP 5xx and timeout errors can prevent feedback events from being recorded. Check connectivity between LeadConduit and the recipient system, and increase retry or timeout settings as needed.
How is a transaction defined in LeadConduit?
A transaction is a billable event that occurs when a lead is processed by a source, add-on, integration, feedback event, or ping event. Each of these events is charged based on your pricing rules and ultimately appears in your billing reports.
Which view should I use for financial reporting—Dashboard or Reports?
Use the Dashboard for tracking overall lead performance based on submission dates, and use Reports to analyze feedback events and revenue recognition based on when those events occur.
Glossary
| Term | Definition |
|---|---|
| Source Event | The initial receipt and processing of a lead, including evaluation against acceptance criteria and pricing rules. |
| Add-On Event | A billable event triggered by an external data enhancement or verification integration, such as TrustedForm or Telesign. |
| Integration Step | A flow step that sends lead data to an external system (e.g., CRM, call center) and is billed if executed successfully. |
| Feedback Received Event | An event created when a recipient sends feedback (conversion or return) to LeadConduit, which can impact billing and performance metrics. |
| Feedback Sent Event | An event generated when LeadConduit forwards recipient feedback back to a source, typically excluding events with HTTP errors. |
| Ping Event | A Real-Time Bidding (RTB) event where a ping submission is sent from a source; these are invoiced separately from other events. |
| Transaction | A billable unit representing a single lead event (source, add-on, integration, feedback, or ping) charged against your account. |
- flow-sources-rules.png100 KB
Comments
0 comments
Please sign in to leave a comment.