How to Set Up Custom Menus

How to Set Up Custom Menus

How to Set Up Custom Menus 

This article explains how to configure Custom Menu Links and Custom Asset Links in your white-label tracking platform, so you can add your own branded links, tools, or embedded pages into your client-facing app.

 

  1. Log in to your reseller admin panel.
  2. In the left-hand navigation menu, click Reseller Settings.
  3. Scroll down to the Custom links section.



Embedding Your Website (Important — CSP Settings)

If you want a custom menu link to open inside the app (embedded in an iframe) rather than opening in a new browser tab, your website must explicitly allow this via its Content-Security-Policy (CSP) headers.

Step 1: Identify your platform domain

This is either:

Step 2: Update your site's CSP header

Add a frame-ancestors directive that permits your platform's domain to embed your page:

Content-Security-Policy: frame-ancestors https://demo.whitelabeltracking.com;

Replace the domain with your actual assigned subdomain if applicable.

Step 3 (Legacy browser support)

If your site needs to support older browsers that don't recognize CSP, also set:

X-Frame-Options: ALLOW-FROM https://demo.whitelabeltracking.com

Note: X-Frame-Options is a legacy header and is ignored by most modern browsers, but it can help with older browser compatibility as a fallback.

⚠️ Important: Match the Protocol Exactly

https:// and http:// are not interchangeable in CSP/X-Frame rules. If your website runs on HTTPS (which is strongly recommended), make sure every reference to your platform's domain in these settings also uses https://. A mismatch will cause the embed to silently fail.



Troubleshooting

My custom link shows a blank page or refuses to connect when embedded:

  • Confirm your site's CSP allows frame-ancestors for the exact platform domain.
  • Double-check the protocol (http vs https) matches on both sides.
  • Some websites block all iframe embedding by default (e.g., via frame-ancestors 'none' or X-Frame-Options: DENY) — you'll need to update this on your own server/CMS settings.