Skip to content
English
More support Sign in
Contact Us
  • There are no suggestions because the search field is empty.

How to Verify the Orbee Script is Loading

Why Verify the Script?

Installing the script is only half the battle. Before we can officially "sign off" on a tagging installation, we have to confirm the browser is successfully communicating with Orbee’s servers. A successful load ensures that activity is being tracked and accurately routed correctly.

Method 1: The Network Check

The fastest way to see if Orbee is "firing" on your page is to check for the global orb object.

  1. Open Developer Tools: Right-click on the page, select Inspect, and click the Network tab.

  2. Filter for Orbee: In the "Filter" or "Search" box, type orb.

  3. Refresh the page (Perform a Hard Reload if results don't appear).

  4. Confirm the Status: Look for the file tms.js?sid=....

Column Success Value Meaning
Status 200 The Orbee's server successfully received the request.
Domain scripts.orb.ee The script is communicating with the correct Orbee endpoint.
Initiator script The browser recognizes the file as executable JavaScript.

Method 2: Verifying the "Asset Chain"

A successful "sign-off" requires more than just the initial loader. Once the tms.js file fires, it should automatically trigger the loading of the Namespace and Bundle files.

What to look for in the Network list:

  • tms.js?sid=... (The Loader)

  • namespace.min.js (The Configuration)

  • bundle.min.js (The Tracking Logic)

Status: If you see all three files with a 200 Status, the script architecture is fully initialized.

Troubleshooting Errors

If the script does not load as expected, look for these specific error states:

Status 404 (Not Found)

A 404 indicates the request reached the Orbee server, but the server couldn't process it. This is generally caused by:

  • The Token is Wrong: There is a typo in the sid= value in your script snippet.

  • Missing Configuration: The "Redirect Domain" or "Redirect Token" is not yet mapped in the Orbee Platform Console. If you see this and the website is expected to be live, contact Orbee to ensure the tracking script is fully configured.

Request Not Found / Missing

If tms.js does not appear in the list at all:

  • Blocked by Ad-Blockers: Check if an extension is preventing the script from firing.

  • Blocked by Privacy or Compliance Tools: Consent Management Platforms may be blocking the script. Ensure that the that you have "Accepted" cookies on the page.

  • Placement Issue: The script may not be correctly placed in the <head> or is being suppressed by a Tag Manager trigger.