5

The current lack of documentation regarding the specific storage entities for Customer Insights - Journeys interaction data has presented significant challenges for customers. The desired outcome is to have a clear and accessible way to identify and retrieve interaction data beyond platform-imposed limits


Current Limitations:

  • Interaction data entities are not documented, leaving users uncertain about data location and schema.
  • The integration with Microsoft Fabric is beneficial but requires additional setup, technical expertise, and often licenses that may not align with customer budgets.
  • No direct API is available to retrieve all interactions programmatically.


Proposed Enhancements:

  1. Comprehensive Documentation: Clearly identify and document the entities and data structure for Customer Journeys interactions, whether stored in Fabric, Azure, or other services.
  2. Direct Data Access Options: Introduce an API or expand capabilities in the existing platform to allow customers to retrieve interaction data programmatically without dependency on third-party tools.
  3. Simplified Export Tools: Increase export limits or provide built-in options for larger datasets directly from the platform.


Addressing these points will empower customers with better data accessibility, reduce reliance on third-party solutions, and enhance the overall utility of Customer Insights - Journeys.

STATUS DETAILS
Needs Votes