Embedding and White-Labeling for ISVs

The goal of embedded analytics is that your customers experience reporting as a native part of your product — not as a third-party tool they've been handed off to. How well a platform achieves that depends on two things: how it embeds into your application technically, and how completely it removes the vendor's brand and presence from the experience.

Both of these have significant variation across platforms. "White-label" in particular is a term vendors use loosely — it can mean anything from "your logo is visible" to "we are completely invisible." This chapter covers what each actually means and what to verify.

The Two Embedding Patterns

iframe Embedding

The platform renders its UI inside an HTML iframe in your application. Your application passes an authenticated session token to the iframe; the platform shows that user's tenant data, applies the configured branding, and enforces the permission model. From your customer's perspective, they're looking at a frame within your UI that renders charts, dashboards, and reports.

iframe embedding is the fastest integration path and the most widely supported. The tradeoff is UI control: the iframe renders its own DOM, which means deep integration with your application's layout — matching pixel-perfect to your design system, sharing state with your application's navigation — requires more effort than what a basic embed provides.

For most ISVs, iframe embedding is sufficient and the right place to start. The analytics section of your product is usually a distinct area — a Reports tab, an Analytics page — where tight design integration matters less than in a UI component embedded inline with your core application features.

API-Driven Embedding

Your application calls the analytics platform's API to fetch data, generate reports, or trigger exports — then renders the results using your own frontend components. This gives you complete UI control: the analytics data appears inside your design system, styled exactly as you want, with no iframe boundary.

The tradeoff is development time and maintenance. Every visualization type you want to render requires custom frontend code. Changes to the analytics data model or API may require updates to your frontend components. API-driven embedding is the right choice when you need analytics tightly integrated with your application's existing UI — displaying a chart inline within a workflow screen, for example, rather than on a dedicated reports page.

Most ISV teams use iframe embedding as the primary integration and add API calls for specific high-value use cases where they need tighter control. Starting with iframes and expanding with API calls over time is a reasonable approach.

What "White-Label" Actually Means

Ask five vendors if they support white-label and all five will say yes. What they mean varies enormously:

Logo replacement only. Your logo appears instead of the vendor's. The vendor's color scheme, typography, and UI patterns are unchanged. Your customers are looking at a clearly third-party UI with your logo grafted onto it. This is branding, not white-labeling.

Color and logo theming. You can configure a primary color and upload a logo. The resulting UI looks like your brand at a glance, but a developer inspecting the DOM or the network requests can identify the underlying platform. Adequate for most B2B ISV use cases where customers aren't actively trying to identify the vendor stack.

Full white-label. The vendor's name, logo, and identifying information is completely absent. CSS is fully customizable. Network requests don't reveal the vendor. The embedded UI is indistinguishable from a custom-built application by visual inspection. This is what "white-label" means in the strictest sense.

Per-tenant branding. Each customer gets their own logo and color configuration — Customer A's analytics show Customer A's branding; Customer B's show Customer B's. This is the ISV requirement that most platforms handle poorly, because it requires a configuration layer that maps tenant identity to a branding policy at render time. It's different from a single white-label configuration that applies globally.

For ISVs, per-tenant branding is the specific requirement that matters — not just a single white-label configuration. Confirm whether the platform supports it, how it's configured, and whether there are limits on the number of branding policies you can create.

What Your Customers Can and Can't See

Even with full white-labeling, there are signals a technically curious customer could use to identify the underlying platform — browser developer tools, network request headers, JavaScript bundle names. For most B2B SaaS use cases, this doesn't matter: customers aren't inspecting your tech stack, and even if they did, using a third-party analytics platform is normal and expected.

Where it matters is contractual: some enterprise customer agreements include restrictions on third-party software embedded in the product. If this is a real concern for your customer base, review the vendor's OEM license terms carefully — specifically whether they permit you to embed the platform in a product you resell without disclosing the underlying vendor to end users.

Yurbi's OEM license is included in every plan and explicitly permits embedding in products you sell to customers. There's no separate OEM agreement required, no additional fee, no restriction on how many products you embed it in (one product per plan; additional products get a meaningful discount).

The Scheduled Export Branding Gap

One white-labeling failure point that's easy to miss: scheduled reports delivered by email. Many platforms white-label the in-product UI but send scheduled exports via email from a vendor-branded address with a vendor-branded template. Your customer's Monday morning report arrives from noreply@vendorname.com with a vendor logo in the header.

Confirm that email delivery for scheduled exports is configurable — sender address, email template, and headers — before you consider white-labeling complete. This is the white-label gap customers notice most directly because it arrives in their inbox.