The Tracking Script

After you sign up for Luigi’s Box, you will receive a unique tracking script. This script activates Luigi’s Box services, including Analytics, Autocomplete, Search, Product Listing, and Recommender.

Example:

<script async src="https://scripts.luigisbox.tech/LBX-123.js"></script>

Note

This script is required unless you are performing a full server-side integration via the API.

Domain specificity

Each tracking script is unique to a specific domain. Do not use the same script across different domains. Doing so will merge data from multiple sites into a single view, making analysis difficult. If you manage multiple domains, please contact us for separate tracking scripts.

Installation

Option 1: Direct HTML injection (recommended)

Locate your website’s main layout or header file. This file is typically responsible for the global header across all pages (e.g., header.php, theme.liquid, or head.phtml).

Paste the script tag anywhere between the opening <head> and closing </head> tags.

Example:

<!DOCTYPE html>
<html>
  <head>
    <script async src="https://scripts.luigisbox.tech/LBX-123.js"></script>
  </head>
  <body></body>
</html>

Tip

If you are using Magento or IdoSell, browse our Platform Integrations to find the specific setup guide for your store.

Option 2: Google Tag Manager (GTM)

If you cannot modify the HTML directly, you may use Google Tag Manager.

You can refer to this step-by-step guide for GTM integration.

Caution

We strictly recommend Option 1 instead. Using GTM has two major downsides:

1. Adblockers: Many adblockers block GTM entirely. If you load Luigi’s Box via GTM, our services will not load for users with adblockers enabled.
2. Performance: Loading via GTM introduces latency, which may cause advanced features (such as Fixit rules) to execute more slowly.

Switching trackers on locale change (single-page apps)

The master script may only be initialized once per page load. Loading a second tracking script — for example a different LBX-<tracker>.js for another language or currency — while the first one is already active is a no-op: the additional script detects that Luigi’s Box is already running and refuses to re-initialize. The originally loaded tracker stays active and keeps collecting data.

This matters for single-page applications (SPAs) where the user can switch locale without a full page reload. If each locale has its own tracking script, a client-side locale switch will not swap the active tracker, and events for the new locale will continue to be attributed to the previously loaded tracker.

Caution

There is no supported way to re-initialize or replace the tracker at runtime.

To make sure each locale is tracked with the correct tracking script, trigger a full page reload when the user changes locale (for example window.location.reload() or a normal navigation to the localized URL). After the reload, include only the tracking script that matches the newly selected locale.

If your locales share a single tracking script, no reload is required — the locale can be sent as part of the tracked data instead. Contact us if you are unsure which setup applies to your account.

Content Security Policy (CSP)

If your website enforces a Content Security Policy, add the following rules to allow Luigi’s Box services to communicate with your site:

CSP Directive	Required Values
connect-src	https://api.luigisbox.tech https://live.luigisbox.tech https://app.luigisbox.tech
script-src	https://scripts.luigisbox.tech https://cdn.luigisbox.tech
style-src	https://cdn.luigisbox.tech