Global Settings
The Global Single Type controls site-wide configuration that applies to every page on the website. You can find it in the Backoffice under Content Manager > Global.
This includes branding, navigation, cookie consent, analytics, and script injection.
Tracking & Consent
These fields control how third-party tracking and consent management are loaded on the website. They are not locale-specific — the same values apply across all languages.
Cookiebot ID (cookiebotId)
The Domain Group ID from your Cookiebot account. When filled in, a cookie consent banner will be shown to visitors before any tracking scripts are loaded.
- Obtain this ID from the Cookiebot dashboard under Domain Groups.
- The banner appearance and categories are configured directly in Cookiebot — no changes to the website are needed.
- Leave empty to disable the consent banner (not recommended for live environments).
The Cookiebot banner will only work correctly on the domain registered in the Cookiebot account. Ensure the production domain is added to the domain group before going live.
Google Tag Manager ID (gtmId)
The Container ID from your Google Tag Manager account (format: GTM-XXXXXXX). When filled in, GTM will be loaded after the user gives consent in the Cookiebot banner.
- All analytics, marketing, and tracking scripts (Google Analytics, Meta Pixel, HubSpot tracking, etc.) should be managed through GTM tags — not added directly to the website.
- GTM will not load until the visitor accepts cookies. Returning visitors who have already given consent will load GTM immediately on page load.
GTM is the single point of control for all Google-related and marketing tracking. Configure your tags, triggers, and variables inside the GTM interface rather than adding scripts directly to the site.
HubSpot Portal ID (hubspotPortalId)
The Portal ID from your HubSpot account. Required for the Request a Quote form to function correctly.
- This does not load the HubSpot tracking script — tracking is handled by GTM.
- Only affects form submission functionality.
Script Injection
These fields allow the marketing team to inject custom code globally across the website without requiring code changes. They are not locale-specific.
These fields accept raw HTML, JavaScript, and CSS. Only authorised team members with Strapi admin access should edit these fields.
Header Scripts (headerScripts)
Raw HTML or <script> tags to be injected into the <head> of every page. Use this for:
- Third-party tracking pixels that require early loading
- Consent-related scripts
- Custom meta tags or preload hints
Example:
<script src="https://example.com/some-tracking.js"></script>
Footer Scripts (footerScripts)
Raw HTML or <script> tags to be injected before the closing </body> tag on every page. Use this for:
- Chat widgets (e.g. HubSpot chat, Intercom)
- Scripts that should load after the page content
- Any third-party embeds that don't need to be in the head
Example:
<script>
window.intercomSettings = { app_id: "YOUR_APP_ID" };
</script>
<script src="https://widget.intercom.io/widget/YOUR_APP_ID"></script>
Custom CSS (customCSS)
Raw CSS applied globally to every page. Use this for:
- Minor style overrides that don't require a code deployment
- Brand adjustments or temporary visual fixes
Example:
.some-element {
display: none;
}
Custom CSS is intended for small, temporary adjustments. For permanent style changes, coordinate with the development team so they can be properly integrated into the codebase.
Other Global Fields
| Field | Description |
|---|---|
siteName | The site name used in browser tabs and SEO metadata |
siteDescription | The default meta description |
favicon | The site favicon |
lightLogo / darkLogo | Logos used in the header and footer |
newsletterFormGUID | HubSpot form GUID for the newsletter form |
requestAQuoteFormGUID | HubSpot form GUID for the Request a Quote form |
Header | Navigation and header configuration |
Footer | Footer links and content |
suggestedActions | Global suggested action buttons shown across the site |