Custom Code lets you install third-party scripts such as live chat widgets, analytics tools, session-recording tools, or other snippets across the white-label application.
Once saved, the code appears across the pages your customers use, which means the platform can feel more like a complete product and less like a generic dashboard.
What custom code is
#Custom Code is an agency-level white-label feature. You control it from the white-label settings, and your customers simply experience the result.
Steps and details
This is useful when you want a chat widget, tracking script, custom font, cookie tool, or another trusted third-party integration to appear across the platform without editing source files.
Where to find it
#Go to Platform -> White-Label -> Configuration, open the Advanced tab, and scroll down to the Custom Code section.
Steps and details
The custom code area appears in the Advanced tab alongside rating-progress gamification, Cloudflare Turnstile, and Custom Menu Links.
The two script fields
#The custom code area gives you two separate fields because not every script should load in the same part of the page.
Steps and details · includes a table
| Field | Where it loads | Best for |
|---|---|---|
| Header Scripts | Inside the page head | Analytics, tag managers, custom fonts, early-loading scripts |
| Body Scripts | At the end of the page body | Chat widgets, feedback tools, and scripts that are not critical to initial render |
Installing a chat widget
#For most chat tools, the right place is the Body Scripts field. Copy the full script snippet from the chat provider and paste it into Body Scripts, then save.
Steps and details
After that, open a customer-facing page and verify that the widget appears where expected.
- Get the full snippet from the chat provider
- Paste it into Body Scripts
- Save changes
- Verify it on a customer-facing page or in a private window
Installing analytics or tracking tools
#Analytics and tag-manager snippets usually belong in Header Scripts because they need to initialize early and capture page activity from the beginning of the load.
Steps and details
This is the normal place for tools like Google Analytics, Google Tag Manager, Meta Pixel, or similar tracking code.
Where your code appears
#Once saved, custom code is injected across the customer-facing side of the white-label application. That includes the logged-in app experience and public pages like forms or login-related screens.
Steps and details
The exact user experience depends on the script itself, but the platform-level placement is broad by design.
- Customer dashboard pages
- Registration pages (header and body scripts) and login pages (header scripts only)
- Hosted report pages, the built-in website, and the help centre
- Reports and similar customer-visible white-label surfaces
How to test it properly
#The safest way to verify custom code is to open a customer-facing page in a private window or log in as a customer rather than relying only on your agency view.
Steps and details
That matters because some white-label scripts are meant for customer-facing surfaces rather than the agency admin experience itself.
Common use cases
#Steps and details · includes a table
| What you want to install | Where it usually goes |
|---|---|
| Live chat widget | Body Scripts |
| Google Analytics | Header Scripts |
| Google Tag Manager | Header Scripts |
| Meta Pixel | Header Scripts |
| Custom fonts | Header Scripts |
| Session recording or behavior tools | Header Scripts |
| Cookie or consent tools | Body Scripts |
| Custom CSS | Header Scripts inside style tags |
What you want to install · Where it usually goes
- Live chat widget
- Body Scripts
- Google Analytics
- Header Scripts
- Google Tag Manager
- Header Scripts
- Meta Pixel
- Header Scripts
- Custom fonts
- Header Scripts
- Session recording or behavior tools
- Header Scripts
- Cookie or consent tools
- Body Scripts
- Custom CSS
- Header Scripts inside style tags
Use it carefully
#Custom Code is powerful, but it can also break things if the script is poor quality or not designed for the environment. Only use snippets from providers you trust and test after every change.
Steps and details
If a script causes trouble, remove it from the relevant field and save again. The change applies immediately across the platform surfaces where it was being injected.