A recurring theme inside Feature Gap signals for Data Platforms. Explore real examples and the stored reasons behind this classification.
APIs enable connections with many external or in-house systems for comprehensive workflows.
Themes group similar “reasons” across many signals so you can quickly spot what’s consistently driving launches, positioning shifts, conversion angles, or pain points in this space.
Real examples with the stored reasons/explanations.
Gist: Celigo is valued for being easy for new users to learn and for reducing manual time spent on ERP integrations. The main drawback is difficulty configuring image transfers to ERPs.
Signal reason: The user notes a specific capability gap around sending images to ERPs.
Gist: Celigo is viewed as easy to learn with responsive support and a solid set of out-of-box integrations. Users also note scaling limits, inconsistent flow design, and more coding for custom workflows.
Signal reason: The user notes custom flows need more coding and some integrations are hard to follow.
Gist: The user values the product’s different interfaces and charts for understanding client context. Main frustrations are limited sample sizes, a one-year data cap, and difficulty connecting social accounts.
Signal reason: The user highlights missing or inadequate capabilities around deeper history and social account connections.
Gist: Celigo is valued for its large connector library and automation across business systems. The main drawback is difficulty handling complex cross-system workflows, conditional logic, and data transformations.
Signal reason: The user says workflows spanning multiple systems, conditional logic, and transformations are difficult.
Gist: Celigo is valued for broad connection-building and an intuitive UI, but users report inconsistent performance, slow integrations, and support that offers temporary fixes instead of durable solutions.
Signal reason: The comment highlights limitations in the integration process and inadequate support resolution.