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

Verifying Namespaces for Redirect Scripts (Domains & Subdomains)

What is a Namespace?

In the Orbee ecosystem, a Namespace is the unique identifier for the specific digital location where your script is installed. For the data to route correctly, the namespace provided in the script must match the exact domain or subdomain shown in the browser's address bar.

1. Identifying the Correct Namespace

Whether you are on a primary domain or a specific subdomain, the namespace must exclude the protocol (https://) and any trailing slashes (/).

  • Primary Domain Example:

    • URL: https://www.primary-dealer.com/

    • Namespace: primary-dealer.com

  • Subdomain Example:

    • URL: https://inventory.primary-dealer.com/

    • Namespace: inventory.primary-dealer.com

The Rule: The namespace must match the specific environment where the script is executing. If the script is on a subdomain but you only provide the primary domain, the redirect will fail.

2. Implementation in the Script Snippet

A Redirect Script requires the sid parameter to combine your unique Redirect Token with the Namespace, separated by a colon.

  • Standard Format: sid=REDIRECT_TOKEN:subdomain.primary-dealer.com

  • Encoded Format: sid=REDIRECT_TOKEN%3Asubdomain.primary-dealer.com

Note: Both formats are valid. Many Tag Managers automatically convert the colon (:) into its encoded version (%3A) when the page loads.

3. How to Verify the Namespace is Firing

Use the Network tab to confirm that the domain/subdomain is being passed correctly to the Orbee servers.

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

  2. Filter for Orbee: Type orb in the search/filter box.

  3. Refresh the page: Perform a Hard Reload to see the fresh requests.

  4. Inspect the Loader: Look for the request named tms.js?sid=....

    • Success: The sid value includes both your token and the correct domain or subdomain string.

    • Failure: Only the token is visible, or the namespace is missing entirely.

4. Confirming a Successful Redirect (The Asset Chain)

The ultimate proof of a successful installation is the "Asset Chain." If the Orbee server recognizes the Token + Namespace combination, it will load the property's specific configuration files.

You must see these three files in the Network tab for a successful audit:

  1. tms.js?sid=... (The Base Loader)

  2. namespace.min.js (The Configuration)

  3. bundle.min.js (The Tracking Logic)

The Sign-Off Rule: If you see namespace.min.js loading with a 200 Status, it is proof that the namespace was accepted and the redirect was successful.

Troubleshooting Namespace Errors

  • Missing Colon: Ensure the sid isn't just the token. It must follow the {Token}:{Namespace} structure.

  • Domain Mismatch: If the script is installed on a subdomain but the namespace in the code is set to the primary domain, the Orbee server may not be able to find the correct property mapping.

  • Status 404 (Configuration Required): If the namespace is firing correctly in the Network tab (e.g., sid=TOKEN:subdomain.dealer.com) but the subsequent files return a 404 error, the Redirect Token and Namespace have not been linked on the backend. Contact Orbee to verify the mapping is active for that specific domain string.