Crobox Snippet Implementation

Integrating Crobox on your website is lightweight and fast. All you need to get started is to implement the Javascript Snippet (i.e., tag) manually or in your tag manager.

Integrating the Crobox snippet is the first step in your setup. Add the snippet to every page of your website. You can do this manually or through Google Tag Manager.

Choose your setup method

• Manual Snippet Implementation Add the snippet directly to your website code.

• Google Tag Manager Snippet Implementation Add the snippet through a GTM tag that fires on all pages.

Use the snippet that belongs to your Crobox environment. You can find it in Settings → Website Integration → HTML or Javascript (alternative).

What matters most

• Add the snippet to every page

• Load it from your own Crobox environment

• In GTM, fire the tag on All Pages

• Do not copy the example values below into production

The examples below show the structure only. They are not valid for your environment.

Manual implementation

If you manage your website code directly, place the Crobox snippet in the <head> of every page.

This is usually the simplest setup when you control the template or frontend directly.

<!-- Crobox Javascript Snippet -->
<script src="//cdn.crobox.io/js/000000.js" async defer></script>

It is important to load the snippet on every page, since Crobox collects data across the full funnel.

Google Tag Manager implementation

If you use Google Tag Manager, create a Custom HTML tag and paste in your Crobox snippet.

Then set the trigger to All Pages.

That ensures Crobox loads across the full funnel.

Step 1: Create a new tag

Open Google Tag Manager in the workspace for your website and create a new tag.

Step 2: Rename the tag

Rename the tag to something clear, such as Crobox Javascript Tag.

Step 3: Choose the tag type

Select Custom HTML as the tag type.

Step 4: Paste your Crobox snippet

Paste the snippet from your Crobox environment into the tag.

Each Crobox snippet is unique. Use the snippet from your own environment or the one shared by your Crobox contact.

Step 5: Set the trigger

Open Triggering and set the tag to fire on All Pages.

If the tag only fires on part of the site, tracking and experiences will be incomplete.

Step 6: Publish your changes

Once the tag is ready, publish the container.

Next step

Once the snippet is live, set up event tracking.

Event tracking sends pageviews and key actions to Crobox.

FAQ

Does the snippet affect page performance?

The Crobox snippet is served from a CDN with global coverage for fast delivery.

It is typically smaller than 50 KB before compression, and loads asynchronously with async and defer.

That means it does not block page parsing or delay rendering.

Why don't Crobox experiences load in automated tests (Selenium, Playwright, BrowserStack)?

To keep automated traffic out of your analytics and A/B test results, the Crobox snippet does not run in browsers controlled by automation tools such as WebDriver.

In these sessions, Crobox experiences (such as Product Finders and Campaigns) will not appear, and no requests are sent to Crobox. Your tests can still interact with the rest of your website as normal.

If you need to include Crobox experiences in your automated test suite, contact your Customer Success Manager for guidance.