How do we balance the varying latencies of public regulatory data (like FCC broadband maps) and subscription data (like Dun & Bradstreet) within our real-time customer data spine to drive hyper-local, context-aware Next-Best-Actions without introducing performance bottlenecks? Have you found any lifts for api feeds vs doing batch?
Use a hybrid data integration approach in Pega Customer Decision Hub (CDH) to reduce latency and improve Next-Best-Action performance. Load slow-changing regulatory data, such as FCC broadband maps, through scheduled batch processing. Use APIs to refresh frequently changing Dun & Bradstreet data. Store the information in Pega Data Sets so decision strategies can access it quickly without waiting for external API responses. Configure caching, refresh schedules, and API timeouts to prevent performance bottlenecks. Monitor decision response times and Next-Best-Action conversion rates to measure performance improvements and business value