> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/insights-discover/understanding-the-types-of-insights.md). # Understanding the types of Insights Explore Key Driver, Trend, and Comparison Insights—understand their differences, use cases, and how each helps uncover patterns, drivers, and performance gaps. The initial step for creating Insights is to select the type of Insight that will best serve your objectives. When choosing an Insight type, you should consider what question you're trying to answer or what decision you need to make. Tellius offers three types of Insights and this guide will help you understand the distinctions between them. * Key Drivers * Trend Insights * Comparison insights {% hint style="info" %} Tellius also has another type of Insight, called [**Discovery Insight**](/insights-discover/discovery-insights.md), which can be triggered only from Search or Vizpad charts. {% endhint %} ### Key Drivers Insights #### What are Key Drivers Insights? Key Drivers Insights identify the main factors that significantly affect your business's performance. It's about understanding which variables or elements have the most significant impact on your results. This could include looking at which features of a product are most appreciated by customers or what marketing channels are yielding the best ROI. #### When to Use Key Drivers Insights Use Key Drivers Insights when you aim to: * Pinpoint critical success factors * Allocate resources effectively * Improve product or service features * Optimize marketing strategies ### Trend Insights #### What are Trend Insights? Trend Insights digs into patterns over time. By analyzing trends, you can understand the trajectory of certain metrics, such as sales, user engagement, or website traffic. This insight can help to pinpoint when changes occur and if they are part of a larger upward or downward trend. It's not just about seeing the change but understanding the timing and movement of those changes. #### When to Use Trend Insights Opt for Trend Insights when you need to: * Track performance over time * Identify seasonal effects or market shifts * Anticipate future movements in key metrics * Understand the longevity and sustainability of your strategies ### Comparison Insights #### What are Comparison Insights? Comparison Insights are about contrasting different subsets of data to find out why variations occur between them. This could involve comparing the performance of two different user cohorts, products, time periods, or any other segmentable aspect of your data. It’s useful for identifying why one group may be performing better than another and for making informed decisions about where to focus your efforts. #### When to Use Comparison Insights Employ Comparison Insights to: * Analyze performance differences between segments. * Understand customer behavior across different cohorts. * Inform product development based on segment-specific feedback. * Tailor marketing efforts to the most responsive audiences. Selecting the appropriate insight type is crucial for effective data analysis. Consider what you want to achieve and choose accordingly: * For impact-focused analysis, use **Key Drivers**. * For temporal pattern recognition, investigate **Trends**. * For segment-based differentiation, explore **Comparisons**.


--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.tellius.com/insights-discover/understanding-the-types-of-insights.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.