> 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/tellius-5.6/getting-started/faqs/embedding-faqs.md). # Embedding FAQs Explore embedding FAQs to understand embedding methods, security measures, and best practices for integrating analytics into your app. #### **What type of embedding should I choose?** Based on your requirement - if you want to show a static dashboard (revenue, leads captured etc.) that is common to all users, then you can go with the static token method. For user-specific/interactive charts, dynamic token method can be used. Also, consider the following criteria before choosing an embedding method: * The data consumers of the app (specific to a team/user or common audience) * The technical expertise of the team (ability to build customized UI, generating unique jwt etc.) * The estimated time of completion (few hours or few months) * The level of customization required (no customization or inputs-only or full level of control) #### **Can we do multiple types of embedding in a single application?** Yes, multiple types of embedding can be deployed in a single application. Each iFrame component can be configured separately. #### **What are the security measures taken on embedding?** Tellius can be configured to allow embedding only from same/listed origins and restrict cross-origin requests. The tokens also comes with an expiration. --- # 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/tellius-5.6/getting-started/faqs/embedding-faqs.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.