Docs
Dashboard

Integrations

Connect Google Tag Manager, Google Analytics 4, Meta Pixel, and custom scripts to your site.

The Integrations tab in your site dashboard allows you to connect third-party analytics, tracking codes, and custom widgets without editing your site files.

[!NOTE] Changes made to integrations take effect immediately on your next site publish.


Analytics & Tracking

Google Tag Manager (GTM)

Google Tag Manager is a tag management system that lets you deploy tags without modifying site code.

  1. Toggle the Google Tag Manager switch to the active position.
  2. Enter your Container ID (e.g., GTM-XXXXXXX).
  3. Click Save Changes.

[!TIP] If you load Google Analytics 4 or Meta Pixel via a GTM container, you should keep the individual GA4/Meta Pixel cards in this dashboard disabled to avoid duplicate tracking.

Google Analytics 4 (GA4)

Connect GA4 directly to track traffic, events, and engagement:

  1. Toggle the Google Analytics 4 switch to the active position.
  2. Enter your Measurement ID (e.g., G-XXXXXXXXXX).
  3. Click Save Changes.

Meta Pixel

Track ad conversions and build advertising audiences:

  1. Toggle the Meta Pixel switch to the active position.
  2. Enter your Pixel ID.

    [!IMPORTANT] The Pixel ID must be exactly a 15–16 digit number. If your entry doesn't match this pattern, the system will highlight the input in red and prevent saving.

  3. Click Save Changes.

Custom Scripts

Custom scripts allow you to inject HTML <script> tags, stylesheets, or external scripts.

[!WARNING] Only paste code from sources you trust. Custom scripts run directly on your visitors' devices and can access site data.

Quotas & Plan Locks

  • Plan Restriction: Custom scripts require a plan that includes the Custom Scripts feature. If locked, a warning banner will appear. Any previously saved scripts will be preserved but kept inactive until you upgrade.
  • Quota Limits: The header displays a quota badge (e.g., 3 / 5). If you reach your plan's limit, the Add script button will be disabled, and a notice will prompt you to upgrade.

Script Locations

  • Header scripts: Injected inside the <head> tag. Runs early before the page renders. Ideal for style overrides, anti-flicker snippets, or a third-party cookie consent manager. Set these to Necessary so they load without waiting for the consent bar.
  • Footer scripts: Injected right before the closing </body> tag. Runs after the page markup loads. Ideal for live chat widgets, non-critical trackers, and helper embeds.

Adding & Managing Scripts

  1. Under the Header or Footer section, click Add script.
  2. Enter an optional name (for your internal reference).
  3. Paste the complete script markup (including <script>...</script> tags) into the code box.
  4. To remove a script, click the Trash icon next to it.
  5. Click Save Changes at the top of the panel. Any script inputs left completely empty will automatically be filtered out and removed upon saving.

The consent bar is on by default. When your site has at least one script that isn't strictly necessary, the published site shows a cookie bar with Reject all, Customize, and Accept all buttons, plus a small cookie icon in the bottom corner that reopens the choices after the visitor has accepted or rejected. The choice is remembered for 180 days, and scripts in a category don't load at all until the visitor allows it.

  • Necessary: always loads and needs no bar.
  • Analytics: Google Analytics 4, Microsoft Clarity, PostHog, Hotjar, and other app embeds.
  • Marketing: Google Tag Manager (a container can load ads), Meta Pixel, and the Mailchimp site script.
  • Functional: Zendesk chat.

Each custom script has a Consent category select. New scripts default to Analytics, and existing scripts without a category are treated as Analytics, except that existing style, link, meta, and structured-data-only entries were set to Necessary automatically. Mark a script Necessary to load it without waiting for consent.

The banner itself is a Cookie consent section in the editor. Click Design banner on the Visitor consent card to open the editor, then pick a design and position and set its wording, policy links, buttons and reopen icon. Every site starts with the Classic bottom banner. Publish the site to put banner changes live.

The card's switch turns the bar off. With it off, no bar appears and every script loads for every visitor straight away, whatever its category, so asking for consent is up to you.

If the QookieQloud app is set up on the site, its banner replaces this bar and every script waits for the visitor's choice there instead.

[!NOTE] Google Reviews, Calendly, and form reCAPTCHA are not controlled by the cookie bar.