Hide powered-by branding and apply your logo and company name on consent banners and preference centers.
White label spans two product surfaces: White Label Banner (remove CookieShift powered-by on the live banner) from Essential upward, and Full white label (org defaults + product presentation) on Business / Agency / Enterprise.
Overview
White label applies to visitor-facing consent surfaces only (banner, preference center, CMP embed). Dashboard chrome, login, email, and PDF/HTML reports remain CookieShift-branded until a future enterprise release.
| Plan | Custom CSS & logo | White Label Banner (hideBranding) | Full white label (org defaults) |
|---|---|---|---|
| Free | No | No | No |
| Essential | Yes | Yes (customBranding) | No |
| Pro | Yes | Yes (customBranding) | No |
| Business | Yes | Yes | Yes (whiteLabel) |
| Agency | Yes | Yes | Yes (whiteLabel) |
| Enterprise | Yes | Yes | Yes (whiteLabel) |
Organization-level defaults (set by platform admin) merge into each property when enabled and your plan includes full white label.
Why it matters
Essential and Pro teams can match brand colors and remove the CookieShift powered-by line. Agencies and Business workspaces can also apply org-wide logo/name defaults. Branding is enforced at save time and read time so downgraded plans cannot keep hidden branding via stale config.
Setup
Per-property branding (recommended)
- Confirm your workspace is on Essential or higher for White Label Banner (Billing).
- Open Settings → White Label (
/settings/white-label) or Consent Setup → Appearance. - Set Company name and Logo URL (HTTPS or embedded data URL from Consent Setup upload).
- Enable Hide CookieShift branding to remove the powered-by line.
- Save and verify the iframe preview (uses production
banner.js). - Hard-refresh your live site and open the preference center to confirm.
Consent Setup overlap
You can also set logo and company name under Consent Setup → Appearance. The Hide CookieShift branding toggle is available when your plan includes customBranding (Essential+) or whiteLabel (Business+). Prefer White Label for org-wide defaults on Business / Agency / Enterprise.
Organization defaults (Business / Agency / Enterprise)
Platform administrators can set org-level white label (brandName, logoUrl, primaryColor, hideCookieshiftBranding) in the admin control plane. When enabled:
- Empty site logo/name fields inherit org values on the live embed.
- Site-specific values always override org defaults.
- Org hide-branding applies when the site has not enabled hide locally.
Entitlement requirements
| Feature | Entitlement key | Plans |
|---|---|---|
| Custom CSS & logo | customBranding | Essential+ |
| White Label Banner (hide powered-by) | customBranding or whiteLabel | Essential+ |
| Org default merge | whiteLabel + org whiteLabel.enabled | Business, Agency, Enterprise |
If you save hide-branding without entitlement, the server strips the flag and returns a notice. Public config API responses re-check entitlement on every read so a downgrade cannot leave powered-by hidden.
Examples
| Scenario | Steps |
|---|---|
| Agency client site | Org WL enabled → client property with empty logo → live banner shows org logo and name |
| Single enterprise property | White Label page → logo + hide branding → Save → verify cmp.js on production |
| Essential brand match | Consent Setup → upload logo → enable hide branding → Save |
| Mixed org + site | Org hides powered-by; one property sets its own company name → site name wins, powered-by stays hidden when entitled |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Powered-by still visible | Plan lacks customBranding / whiteLabel, or hide flag stripped | Upgrade to Essential+; re-save branding |
| Logo missing on live site | Empty URL or blocked asset | Use HTTPS URL or Consent Setup upload; check CSP |
| Preview differs from live site | Cache or wrong property | Hard refresh; confirm header property matches embed siteId |
| Org logo not appearing | Org WL disabled, plan lacks whiteLabel, or site overrides set | Upgrade to Business+; enable org WL; clear site logo to inherit |
| Toggle disabled in Consent Setup | Not entitled | Upgrade to Essential+ for hide branding |
| Dashboard still says CookieShift | Expected — dashboard WL is Phase 3 | Only embed surfaces are white-labeled today |
Does white label change my embed snippet?
No. The same cmp.js / banner.js snippet loads config by siteId. Branding is applied from the server payload.
Are reports and emails white-labeled?
Not in the current release. Scheduled PDFs, scan exports, and transactional email remain CookieShift-branded. See Reports for export behavior.
Best practices
- Use White Label / Consent Setup for hide-powered-by on Essential+; use Business+ for org-wide defaults.
- Test on mobile preview and a private browser window after every publish.
- Document which properties inherit org defaults vs custom site branding for agency clients.
- After plan changes, open White Label and re-save once to clear user-facing notices.
Related
- Consent Setup — banner appearance and content
- Billing — plan entitlements