Monitoring Performance and Quality Assurance This step confirms that recommendations are accurate, events are flowing, and quality is stable before and after go-live. Preparation Recommendations live in at least one placement. Tracking events implemented and flowing. Access to monitoring dashboards and logs. Main stakeholder Customer analytics or QA owner. Results Event coverage verified against the agreed scope. API error rates and latency baselines established. Initial quality review completed and sign-off recorded. Use the Integration Monitoring Dashboard The dashboard shows three core panels: Activity to compare Froomle traffic with your internal analytics. API errors to ensure all requests are correctly formatted and error-free. QA warnings to detect missing events or broken flows. Treat major or critical QA warnings as blockers for go-live. If more than 5% of API calls contain errors, the integration is not ready for launch. QA warnings are refreshed daily. They are disabled by default for development environments and should only be enabled once you have a full staging integration. Some warnings only surface after go-live, so plan capacity in the days after launch to address any issues that appear under real traffic. Validate event quality Verify that user interactions—such as impressions and clicks—are successfully tracked and attributed to the correct recommendation modules. Check that event volume aligns with your expected traffic and that no major validation errors are flagged. For detailed event specifications, see Tracking events. Track performance metrics Review KPIs in time slices per placement and channel. See Performance & Metrics for metric definitions and attribution guidance.