Embedding
Embedding is available on Premium and Enterprise plans (opens in a new tab).
Cube supports iframe embedding for dashboards and analytics chat. Two authentication methods are available:
-
Private Embedding – Users authenticate directly with Cube to access embedded content. Users must have Cube accounts and will be prompted to sign in when accessing embedded iframes.
-
Signed Embedding – Authentication is handled programmatically using JWT tokens generated by your application. Users authenticate through your application and do not require Cube accounts.
Additionally, you can use the Cube Core REST API directly for headless embedded analytics.
Types of Embedding
Private Embedding
Private embedding is ideal for internal use cases where users already have Cube accounts. This is perfect for embedding dashboards and analytics into internal tools such as:
- Notion pages for team collaboration
- Salesforce or other CRM systems
- Internal wikis and documentation
- Company intranets and portals
Users will authenticate with their existing Cube credentials when accessing embedded content.
Learn more about Private Embedding →
Signed Embedding
Signed embedding is designed for external, customer-facing analytics. It uses JWT tokens for seamless authentication, making it ideal for:
- Embedding analytics in your SaaS application for customers
- White-label analytics solutions
- Multi-tenant applications where each customer sees their own data
- Public-facing dashboards with controlled access
Users authenticate through your application without needing Cube accounts, providing a seamless experience.