A CRM Analytics consultant at Cloud Kicks wants to create a new dashboard that uses custom GeoJSON to display data; however, they are unable to…

If a consultant at Cloud Kicks needs to use custom GeoJSON files for dashboard visualization and cannot upload the file via the CRM Analytics user interface (UI), the recommended action is to use the API for this purpose. Here’s why this approach is suggested: Functionality Limitation in UI: Currently, the CRM Analytics UI does not support direct uploads of GeoJSON files, which necessitates an alternative method. API Flexibility: The API provides a more flexible route for uploading custom GeoJSON files, allowing consultants to integrate more complex or larger datasets that are not supported through standard UI functionalities. Customization and Control: Using the API also offers greater control over how GeoJSON data is handled, processed, and utilized within CRM Analytics, catering to more advanced customization needs. This method ensures that the consultant can fully utilize CRM Analytics’ capabilities for creating highly customized geographic visualizations, thereby enhancing the analytical value of the dashboards.