Contents
White-label client reporting means your client sees nothing but you: the report lives on your domain, uses your fonts, colors, logo and footer, arrives from your email address, and never names the tool behind it unless you want it to. The other half of the standard has nothing to do with looks: an automated refresh must never overwrite a number one of your people typed by hand.
What should the white-label checklist cover?
Your clients judge you by the report. Anything that gives away the tool behind it costs you a little credibility, and a stale or wrong number costs you a lot. Most agencies check the logo and call it done, but the vendor shows through in a dozen other places, and clients notice every one of them.
| Item | What to check |
|---|---|
| Custom domain | Reports load at reports.youragency.com, not a vendor subdomain; the certificate is valid on your domain |
| Fonts | Your headline and body faces load from the theme, with the fallbacks set; nothing falls back to the vendor's default |
| Palette | Chart series, headings and links use your brand colors, and the palette passes contrast on charts |
| Logo and favicon | Your logo in the header and your favicon in the tab; no vendor mark anywhere on the page |
| Footer | Your company name, address and contact, with no vendor line unless you added one |
| Email identity | Sent from your verified address with your name, your header image and links to your domain |
| Client portal | Same domain, same theme, same logo as the report, covering invoices and statements too |
| Platform branding | Hidden by default; shown only if you choose to show it |
| Manual values | A number a person typed is never overwritten by an automated refresh |
| Change log | Every automated update is logged next to the value it changed |
Why is contrast part of branding?
Because a palette that fails contrast on a chart is a report your client cannot read. Brand guidelines get written for a homepage hero, where pale teal on white looks calm and expensive. Put that same teal on a line chart with four series and it vanishes. Check the palette against WCAG when you set the theme, not when a client tells you they cannot see anything.
| Element | Minimum contrast ratio | Common failure |
|---|---|---|
| Body text | 4.5:1 | Mid-gray secondary text on white |
| Large headings | 3:1 | Light brand color used as a heading color |
| Chart lines and bars | 3:1 against the background | Pastel brand tints on a white chart area |
| Adjacent chart series | Distinguishable without color | Two brand blues next to each other |
Same story with fonts. A display face that looks great on your homepage can be unreadable in a data table. Pick a body font for reports separately from your headline font and let the theme carry both. If you only have one typeface, at least pick a weight and size for tables that reads at a glance, and test it on a normal laptop rather than the designer's monitor.
Why is the email part of the report?
Your client meets the report in their inbox before they ever open it. If the email turns up from a vendor address with a vendor header image, the white label is already broken and no chart is going to fix it. Send from your own verified address, with your header, and make the link land on your domain.
Scheduling matters more than it sounds. A report that lands on the first working day of every month, with nobody having to remember to send it, is what makes you look organized instead of merely busy. Set the cadence per client: your weekly paid media account and your quarterly PR account should not be on the same schedule.
| Delivery setting | Recommendation |
|---|---|
| Sender | Agency's verified address, account manager's name |
| Subject line | Client name, period, agency name; no vendor name |
| Schedule | First working day of the period for monthly retainers; per client otherwise |
| Link target | Report on the agency's domain, with the client portal one click away |
| Attachment | PDF with the same theme, if the client asks for one |
What must never change on refresh?
Automated refreshes are the whole point of a reporting tool, but they come with one hard rule: anything a person typed is final. A corrected traffic figure, a reach estimate you agreed with the client, a coverage piece added from a screenshot — none of that gets overwritten by tonight's fetch. Treat manual entries as untouchable and log every automated change next to them.
The reason is simple: manual values usually exist because the automated source was wrong. Analytics double-counted a week, your account manager fixed it, the client signed off on the corrected number. If the next fetch puts the double count back, your client is looking at a report that contradicts the one they approved, and you are the one explaining why your numbers moved overnight.
The practical rules:
- A manual value shows who entered it and when, visible to your team and optionally to the client.
- An automated refresh skips manual cells and records that it skipped them.
- Reverting to the automated value is a deliberate action by a person, not a side effect of a refresh.
- The change log sits next to the metric, so a question about a number can be answered from the report itself.
This is the part of white labeling that has nothing to do with looks and everything to do with trust. A client who catches one number changing quietly will stop believing the rest of the report, and your domain in the address bar will not save you.
How do you know the white label is complete?
Send yourself the report exactly as a client gets it, to a personal inbox, and open it on your phone. Look at the sender, the subject, the header image, the link, the page that loads, the favicon, the footer and the portal behind it. If anything in that chain names the vendor, you are not finished.
Verbial serves reports and the client portal on your own domain, sends from your verified address, and never overwrites a value your team entered by hand. To run this checklist against your own reports, start free.
Questions
Does white labeling include the client portal?
It should. The portal is where your client sees invoices, statements and payments as well as reports, so if it carries a different brand from the report itself, you have done half the job.
What happens to a manually entered metric when the report refreshes?
Nothing at all. A value a person typed is final until a person changes it. The refresh should skip that cell, log that it skipped it, and show the manual value along with who entered it and when.
Is a custom domain enough to make a report white label?
No. The domain is one line on a list that also covers fonts, palette, logo, favicon, footer, the sending address and header, the client portal, and the total absence of vendor branding. A report on reports.youragency.com that arrives from a vendor's email address is not white label.