Quick answer
Embedded analytics is the practice of putting reports, dashboards and metrics inside the software people already use — a product, customer portal or internal workflow — instead of sending them to a separate BI tool, with access controlled per user or customer.
What embedded analytics means
Embedded analytics is the practice of putting reports, dashboards and metrics inside the software people already use — a product, a customer portal or an internal workflow — instead of sending them to a separate BI tool. Microsoft's Power BI embedded documentation defines it the same way: embedding reports, dashboards and tiles into websites and applications, in two modes — embed for your organization (internal users) and embed for your customers (external users who never touch the BI tool itself).
A setup counts as embedded analytics when it passes a three-part test:
- The data appears where the work already happens. A client checks campaign results inside your portal, not in a spreadsheet you emailed last Friday.
- Visible scope is controlled per user or customer. Each viewer sees only the rows and modules they are entitled to — not everything the dataset holds.
- Metrics share one definition. "Conversion" means the same calculation in every tenant's view, because it is defined once, centrally.
That test also states the thesis of this page: putting data where users already are is the easy half. The hard half is permissions and metric definitions, not charts. Sharing numbers more widely is a data democratization decision; embedding is how you do it without losing control.
Embedded analytics vs self-service BI vs customer-facing analytics
These three terms overlap, and vendors use them loosely. The distinguishing questions are who looks at the data, where, and who decides what they can see.
| Approach | Who uses it | Where they see it | Who controls access | Typical example |
|---|---|---|---|---|
| Embedded analytics | Internal users or external customers | Inside your product, portal or workflow | The host application, per user or tenant | A usage dashboard inside a SaaS admin panel |
| Self-service BI | Internal analysts and business teams | A separate BI tool they log into | BI admins, by workspace or dataset role | A marketing team exploring campaign data in a BI workspace |
| Customer-facing analytics | Your customers (external) | Inside your product or a shared report | You, scoped per customer account | An agency client portal showing per-client traffic reports |
Two rules keep the terms straight. Customer-facing analytics is a subset of embedded analytics: every customer-facing dashboard is embedded somewhere, but an operations tool with internal metrics is embedded without being customer-facing. Self-service BI describes the opposite direction — instead of bringing data to the user's workflow, it invites internal users into the data tool to explore on their own. If your readers are clients rather than colleagues, you are designing an analytics dashboard for external consumption, and access scoping matters more than chart variety.
Embedding levels: iframe, SDK/API, white-label
"Embedded" covers a wide range of engineering commitments. The three common levels differ less in chart quality than in identity handling and tenant control.
| Level | Integration effort | Identity and authentication | Multi-tenancy | Branding control |
|---|---|---|---|---|
| iframe / embed code | Low: copy an embed code, as in Tableau's Embed Views into Webpages or Power BI secure embed | Viewer needs a license or a signed URL; little per-user context | Weak: one view per link unless you add URL filters | Vendor toolbar and styling remain |
| SDK / API | Medium to high: Power BI app-owns-data, Tableau Embedding API, Looker's embed SDK | Host app authenticates users; SSO, embed tokens, connected apps | Row-level security applied per embedded session | Components can be styled; filters and events exposed |
| White-label | Highest: SDK plus design-system work | Same as SDK, plus full identity integration | Tenant isolation and audit logging expected | Vendor branding removed; the view looks native to your product |
Analyst checklists treat these as thresholds, not options: Constellation Research's ShortList for embedded analytics requires iframe, SDK and API-first embedding, white-label support and multi-tenant deployment, alongside role-based access and row-level security.
Choose with if-then rules:
- If the audience is small and read-only, then an iframe or a hosted share link is enough; do not build an SDK integration you will not maintain.
- If each logged-in user must see only their own rows, then you need SDK/API embedding with row-level security — an iframe alone cannot do it.
- If analytics is part of the product you sell, then plan for white-label and budget ongoing maintenance, not just the initial build.
- If you have no developer capacity, then use your analytics tool's read-only sharing and be honest that it is sharing, not per-user embedding.
Permissions and multi-tenancy: the hard part
The engineering problem behind customer-facing analytics is isolation: customer A must never see customer B's data, even though both look at "the same" dashboard. Two mechanisms cover most designs, as Netguru's embedded analytics guide describes: tenant isolation (a separate project, dataset or schema per customer) and row-level security (RLS) (one dataset, with every query filtered by tenant ID or user identity). Constellation's threshold criteria list both, plus audit logging, as baseline requirements.
Worked example (Sample data). An agency sends monthly traffic reports to 20 clients. Today an account manager exports numbers, pastes screenshots and writes an email per client: 45 minutes each, so 20 × 45 = 900 minutes (15 hours) per month.
Switching to per-client read-only links:
- One-time setup: 10 minutes per client to create the link, pick modules and set a password → 20 × 10 = 200 minutes.
- Monthly upkeep: 5 minutes per client to check scope and password → 20 × 5 = 100 minutes per month.
- Savings: 900 − 100 = 800 minutes ≈ 13.3 hours per month.
- Payback: 200 ÷ 800 = 0.25 months — the setup pays for itself in about a week.
The time math is the easy part. The design work is the access-scope table you fill in before sending anything:
| Audience | What they get | Modules opened | Protection | Visitor list and sessions |
|---|---|---|---|---|
| Clients (×20) | Read-only link to their own project only | Overview, Pages, Sources | Password + 90-day window | Never visible |
| Internal team | Console login | All modules | Account permissions | Visible in the console |
| Public marketing link (optional) | Read-only link, no password | Overview only | 30-day window | Never visible |
Count the decisions: 20 links × 3 open modules = 60 module-level scope decisions, each one a chance to expose something you meant to keep internal. Each link points at exactly one client project, so client A cannot reach client B; the password and the day-window limit shrink the exposure if a link gets forwarded. Finally, define "conversion" once — the same purchase goal in every project — so all 20 reports run the same calculation. That is the thesis in practice: the charts took minutes; the permissions and the metric definition are the actual project.
Common mistakes
- One link for every client. If you send all clients the same dashboard link, then anyone can browse everyone's data. Fix: one project or dataset per client, or RLS that filters every query by tenant.
- Treating the iframe as a security boundary. If you assume "it's embedded, so it's safe," remember links get forwarded. Fix: password-protect, limit the day window, and filter by tenant on the server — hiding a toolbar filters nothing.
- Letting metric definitions drift per tenant. If each client's report computes "conversion" slightly differently, then numbers stop being comparable and trust erodes. Fix: define the goal or metric once, centrally, and reuse it everywhere.
- Confusing a read-only link with an embedding SDK. If your requirement is "each logged-in user sees only their rows," then a shared link cannot deliver it — everyone with the link sees the same scope. Fix: SDK/API embedding with row-level security, or scope down to per-client links and say so.
How TapCub shares analytics today
First, the boundary: TapCub is not an embedded-analytics or white-label BI product. What it offers for sharing is a public read-only link, with no per-login-user, row-level view: everyone with the link (and its password, if set) sees the same scoped data. For the 20-client agency above that is still enough, with one TapCub project per client website:
- Create one read-only link per client project. In each client's project, open the Public sharing tab under Configuration › Settings and generate the link; see share a dashboard. Because the link belongs to that client's project, client A's link cannot show client B's data. Only owners and admins can turn sharing on or off.
- Apply the scope table. Allow the Overview, Pages and Sources modules (Audience and Bots are the other two you could open), add a password and cap the visible window at 90 days. The visitor list and sessions are not shareable at all; they stay in the console for your team.
- Rely on the scope, not on a hidden toolbar. Filters for a module you did not allow are dropped, so a client who edits the link cannot pull a slice that was not shared. The page is read-only and cannot change goals or filter definitions.
- Keep one metric definition. Define the purchase goal the same way in each project under Web analytics › Goals, so the conversion numbers you report to all 20 clients come from one rule.
- Give your own AI agent read-only access, if you use one. On the MCP tab of All-platform analytics › Operations › AI Assistant you copy the endpoint, and the key needs only the Read stats scope; the tools read analytics and do not write events or edit definitions. See connect AI agents with MCP.
Send each client the link and the password through separate channels, and the 800-minutes-a-month saving from the worked example holds. As the thesis says, the charts were never the hard part: the five decisions above are all about who may see what, and which definition they see.
Sources
- Microsoft Learn, What is Power BI embedded analytics? (verified 2026-11-15).
- Tableau Help, Embed Views into Webpages (verified 2026-11-15).
- Google Cloud, Looker embed solution overview (verified 2026-11-15).
- Netguru, Embedded analytics: architecture, integration, and build vs. buy (verified 2026-11-15).
- Constellation Research, Constellation ShortList: Embedded Analytics (published 2026-08-12; direct access blocked by Cloudflare, contents verified via search index on 2026-11-15).
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Experience Specialist
Writes about product experience, practical workflows, and growth, turning complex processes into clear steps for everyday decisions.