Feature snapshot
Summary:
Event Streaming is a LeadConduit feature that continuously sends every lead’s event data—inclusive of successfully processed, filtered, and rejected leads—to an external Amazon S3 bucket or Azure Blob Storage container in real time for comprehensive auditing, analysis, and integration with external data platforms.
Key benefits:
- Captures complete event data from every step of a lead’s journey
- Provides a full audit trail for compliance and quality analysis
- Enables historical data analysis and integration with BI or predictive modeling tools
- Facilitates troubleshooting by preserving data even from early rejections
Typical use cases:
- Auditing lead flow performance and identifying rejection reasons
- Feeding comprehensive event data into data warehouses and visualization tools
- Analyzing historical trends to optimize lead processing and improve ROI
How the Event Streaming works
Step‑by‑step instructions
-
Open the flow editor:
Log in to LeadConduit and navigate to the flow you wish to configure. -
Access the Event Streaming menu:
Click the Event Stream icon located in the upper right corner of the flow editor to open the Event Streaming configuration dialog. -
Prepare AWS / Azure resources:
Create an Amazon S3 bucket or Azure Blob Storage container and set up the required permissions by following AWS / Azure guidelines. -
Enter credentials and storage details:
Input your Amazon S3 bucket or Azure Blob Storage container AWS Access Key ID and Secret Access Key authentication details, specify the S3 bucket or Azure container name and a Prefix (folder path) to organize event files, and use the provided toggle to enable Event Streaming. -
Confirm and save configuration:
Click the confirmation box and then save the flow. Once saved, every subsequent lead processed by the flow will have its event data streamed to the designated Amazon S3 bucket or Azure Blob Storage container.
Expected result:
Every lead event, regardless of whether the lead is fully processed or halted early, will be delivered in real time to the specified Amazon S3 bucket or Azure Blob Storage container, ensuring a complete data record is available for review and analysis.
Validation & monitoring (optional)
- Test the setup: Submit a test lead through the configured flow and verify that an event file is generated in your Amazon S3 bucket or Azure Blob Storage container.
- Where to monitor: Check the Amazon S3 bucket or Azure Blob Storage container dashboard for file uploads and review the LeadConduit Events tab to confirm that all expected events have been captured.
Best practices
- Regularly audit your Amazon S3 bucket or Azure Blob Storage container permissions and access policies to ensure secure access to event data.
- Use clear, descriptive prefixes and folder structures in your Amazon S3 bucket or Azure Blob Storage container to organize event files by flow or time period.
- Test Event Streaming with a low volume of leads before enabling it on high-traffic flows.
- Monitor both AWS / Azure and LeadConduit dashboards to detect any discrepancies or delays in event delivery.
- Update and rotate AWS / Azure credentials periodically to maintain security best practices.
Troubleshooting
| Symptom / Error | Likely cause | Resolution |
|---|---|---|
| No event files appearing in S3 or Azure | Event Streaming may be disabled or misconfigured | Revisit the Event Streaming configuration, ensure the toggle is enabled, and verify AWS / Azure credentials |
| Incomplete event data streamed | Lead processing halted early generating partial events | Check flow logs to confirm that even partial events are being generated and streamed correctly |
| Access Denied error when retrieving files | Insufficient or incorrect IAM permissions for the S3 bucket | Update IAM policies according to AWS guidelines to grant proper access to the S3 bucket |
Frequently Asked Questions (FAQ)
What types of lead events are captured by Event Streaming?
Event Streaming captures every event generated during a lead’s journey—including full processing events, early rejections, and filter outcomes—ensuring a comprehensive record is maintained.
Why is event streaming important?
It is important because it allows you to audit and analyze every step of your lead flow in real time, it provides the data needed for compliance and quality control, and it enables seamless integration with external data analysis tools for improved decision-making.
Does enabling Event Streaming affect flow performance?
Event Streaming operates as a background process; while it runs continuously, its impact on flow performance is minimal. However, it is recommended to test with lower volumes initially to ensure system stability.
Do I need advanced AWS / Azure knowledge to set up Event Streaming?
A basic understanding of AWS / Azure —specifically how to create an S3 bucket or a Connection String and configure access permissions— is recommended. Detailed instructions and helpful links within LeadConduit will guide you through the necessary steps.
Glossary
| Term | Definition |
|---|---|
| Event | A recorded snapshot of a lead at a specific step in a flow, detailing submitted data, appended values, timestamps, and outcomes. |
| Event Streaming | The real-time process of transmitting all lead event data from LeadConduit flows to an external Amazon S3 bucket for analysis. |
| S3 Bucket | A scalable storage container provided by Amazon Web Services used to store files and data. |
| IAM | AWS Identity and Access Management, a service that controls user access and permissions to AWS resources. |
| Blob Storage container | A scalable storage container provided by Azure used to store files and data. |
| LeadConduit flow | A defined sequence of steps in LeadConduit used to process and evaluate submitted lead data. |
Comments
0 comments
Please sign in to leave a comment.