# White Label Limits: What Your Clients Can Still See

> What white label reporting actually covers, which surfaces still show the platform underneath, and how to walk a client's path before they log in.

Author: The DashOps Team  |  Published: 2026-10-12  |  Updated: 2026-10-13  |  Topic: Agency & Client Work

You have set the logo, picked the colours, pointed a custom domain at the dashboard and sent the first login link to a client. Then a small worry arrives late at night: what actually happens when they poke around? Does a "Powered by" line sit at the bottom of some screen you have not looked at? Does an email land from an address that gives the game away? Does hovering over a link reveal a URL that is not yours?

White label is not a single switch. It is a set of surfaces, each of which either carries your brand or does not, and the honest answer for any tool is that some carry it and some do not. This post walks through exactly which is which, so you can decide what to tell your clients rather than finding out from them. If you want the wider picture of how agency-branded reporting works end to end, the [complete guide to white label Facebook Ads reporting](/resources/white-label-facebook-ads-reporting) covers the whole territory. This one stays on the awkward corners.

![image_20261013_223407-httpsdashopsioresourceslooking-established-as-a-sm-httpsdashopsioresourceslogo](https://pub-ae7c0247bc134935855f21b665422e27.r2.dev/posts/1791913077734-79064653c3fb.jpg)

## The surfaces a client actually touches

Start by listing every point of contact, because the gap between "the dashboard is branded" and "the client experience is branded" lives in the surfaces nobody demos.

- The login screen, before they have authenticated
- The browser tab title and favicon
- The URL in the address bar, and the certificate behind the padlock
- The dashboard itself: colours, logo, the footer
- Any email they receive: the sender name, the sender address, the reply-to
- PDF and Excel reports, including the file name they see in their downloads folder
- Public share links you send to someone without a login
- Password reset and invitation emails, which are the easiest to forget
- Error pages, expired links, and the screen shown when something has gone wrong

Those first few are what most tools mean when they say white label. The rest is where the seams show.

## What DashOps rebrands, plainly

Inside the dashboard, your logo replaces ours in the sidebar, your primary and secondary colours flow through buttons, links and charts, and your favicon replaces ours in the browser tab. There is a toggle to hide the default footer credit, so a client can move around without a line at the bottom naming a tool they are not paying for.

PDF and Excel reports carry your logo and your colours on the cover and in the table headers. That matters more than the dashboard for many agencies, because a report gets forwarded to people who never log in at all. The report is often the only artefact a client's own boss ever sees.

On the top plan you get two more things. Your own domain, so the address bar reads as yours rather than as ours, with a certificate issued for your hostname. And your own email sender, so scheduled reports and digests arrive from an address on your domain rather than from a DashOps address. Setting up the domain half is its own small project involving DNS records at your registrar, which is why it has [a dedicated walkthrough](/resources/custom-domain-for-a-client-dashboard).

## What clients can still see, and how to handle it

Now the honest part. Here is what remains visible in a fully branded setup, and what to do about each.

**Meta itself is never hidden.** Your client is looking at Facebook and Instagram advertising data. Campaign names, ad set names, placement names like Facebook Feed and Instagram Reels, and metric names like CPM and ROAS all come from Meta and stay as Meta writes them. That is a feature, not a leak. A client who checks a figure against something they were told elsewhere should find the same figure and the same vocabulary. Renaming Meta's own terms would create a translation problem the first time anyone compared notes.

**The plan you are on decides how far the branding goes.** Logo and colours are one thing, a custom domain and a custom email sender are another. If you are not on the plan that includes the domain and sender, the address bar and the From line will not be yours. This is not a hidden catch, it is the shape of the pricing, and it is worth checking before you promise a client a fully own-brand portal.

**Emails split into two kinds.** Scheduled reports and digests go out from your sender once that is configured. Account emails, the invitation that creates a client's login and the password reset if they lose it, come from the platform. Account mail is the mail you least want landing in spam, and deliverability leans on the reputation of the sending domain, so it is a reasonable thing for a platform to keep on its own. Tell your client that the login invitation comes from the platform and the reports come from you, and the question never gets asked again.

**Share links point at a dashboard.** A public read-only link is a genuine URL that someone opens without logging in. On a custom domain it is your hostname. Without one, it is not. If you use share links with people outside the client's core team, check what the link looks like before you paste it into an email.

**Anything a client is told by someone else.** If your client also has direct access to their own Meta ad account, they can see everything you can see about spend. White label controls presentation, not access. Deciding what a client sees is a separate lever: you assign specific ad accounts to their login, and you can hide spend from them entirely if your arrangement is that they see performance and not cost. That is a settings decision, not a branding one, and it is the one people confuse with white label most often.

## The mismatch that actually causes trouble

The failure mode is almost never a client spotting a logo. It is a client noticing an inconsistency and wondering what else is inconsistent.

A dashboard on your domain that emails from a stranger's address. A branded PDF that arrives attached to an unbranded email. A polished portal whose error page is generic. None of these are secrets being revealed, they are just gaps in a story, and a gap in a story is what makes a careful client start looking harder.

So the practical rule is to make the surfaces agree with each other rather than to chase perfection on any one of them. A tool that is honestly and consistently presented as your reporting stack reads better than a half-disguised one. If you are still weighing whether to disguise the tool at all, the trade-offs are laid out in [white label versus using your own branding](/resources/white-label-vs-your-own-branding).

## Do this before the client logs in

Open a private browsing window and walk the path a client walks, in order.

1. Open the login URL as a stranger would. Look at the address bar, the tab title, the favicon and the certificate.
2. Sign in as a test client user, not as yourself. The Owner view and the Client view are not the same screens.
3. Scroll to the bottom of a few pages and check the footer.
4. Generate a PDF and an Excel report. Look at the cover, the headers and the file name.
5. Send yourself a scheduled report to an address you control, and read the From line, the reply-to and the subject.
6. Trigger a password reset on the test user and read that email too.
7. Create a share link, open it in a different browser, and look at what someone with no login sees.

Anything that surprises you in the email steps will surprise your client too. Fix what you can, and write one plain sentence in your onboarding email about anything you cannot. "Your reports come from us, your login emails come from the platform we build on" pre-empts the awkward question entirely.

Then stop thinking about it. The branding is a one-time setup. What your client actually judges you on is whether the numbers turn up on time, which is a scheduling problem rather than a design one, and one worth [automating properly](/resources/how-to-automate-facebook-ads-reports).

## Frequently asked questions

### Can a client tell which reporting tool an agency uses?

Sometimes, and it depends on which surfaces you have configured. The dashboard, the favicon and the reports can carry your logo and colours, and the default footer credit can be switched off. On the top plan the address bar and the report sender can be yours too. But account emails such as the login invitation and password reset come from the platform, and Meta's own campaign names and metric names never change. A client who looks carefully can usually work out that a tool sits underneath, which is normal.

### Do login and password reset emails come from my own sending address?

Account mail is the mail you least want landing in spam, and deliverability leans on the reputation of the sending domain. An invitation that never arrives means a client who cannot log in at all. Scheduled reports and digests are the mail your clients read regularly and forward internally, so those move to your sender once a custom email domain is configured. Mention the split once during onboarding and it stops being a question.

### Does white label change what data a client can see?

No. White label controls presentation only: the logo, the colours, the domain and the sender. What a client can see is a separate set of controls. You assign specific ad accounts to their login, so they see those and nothing else, and you can hide spend from a client user entirely if your arrangement is that they see performance rather than cost. People often conflate the two. Set the access rules first, then set the branding.

### What does a public share link show someone who has no login?

A read-only snapshot of the dashboard for the ad account and period you pinned when you created the link. It carries your branding the same way the dashboard does. The URL itself is a real address, so it reads as your hostname when you are on a custom domain and as the platform hostname when you are not. Open one in a browser where you are not signed in before you paste it into an email, so you know exactly what the recipient sees.

### Do PDF and Excel reports carry my branding?

Yes. The cover, the table headers and the accent colours pick up your logo and your palette. This matters more than the dashboard for many agencies, because a report gets forwarded to people who never log in, so it is often the only artefact a client's own leadership sees. Generate one and open it before your first client report goes out, and check the file name too, since that is what shows up in their downloads folder.

---

Full page: https://dashops.io/resources/white-label-limits-what-clients-still-see