Skip to main content
You are here: integration

Bridged LoaderJS Integration Guide

The Bridged LoaderJS enables dynamic injection of Bridged interactive components (such as AI cards and engagement widgets) into your website with minimal technical effort.

This integration is lightweight, asynchronous, and fully compatible with modern web frameworks — including SPA environments.

1. Inserting Bridged LoaderJS

1.1 Add the Loader Script

To activate Bridged components on your article or content pages, insert the following script inside the <head> section of your page template:

<script type="text/javascript" src="https://loader.bridged.media/bridged-agent.js" id="bridged-loader-js"></script>

1.2 Important: Domain Access vs Agent Execution

Adding the Bridged script to the header does NOT mean the agent will run on the entire domain.

It only provides Bridged with technical access to pages under that domain.

All runtime behavior is controlled separately from the Bridged Self-Service Dashboard, including:

  • Which pages the agent runs on

  • Which pages are excluded

  • URL-based targeting rules

  • Category-based targeting

  • Date-based activation rules

  • Conditional logic and triggers

The script must be available globally so the dashboard rules can determine where and when the agent should execute.

If the script is not present on a page, the dashboard cannot activate the agent there.

1.3 Performance Characteristics

  • First load: ~300 kB total

  • Subsequent loads: ~5 kB (cached assets)

  • Async loading: Prevents blocking page rendering

  • SPA compatible: Works with modern JavaScript frameworks

  • Cross-browser tested: Compatible with modern browsers

2. Validation & Verification

After integration, validate that the loader is functioning correctly.

2.1 Confirm Script Injection

Open your browser’s Developer Tools → Elements tab and verify:

  • bridged-agent.js is present in the <head>

  • bridged-loader.js is automatically injected

You should see both script tags in the DOM.

Troubleshooting Checklist

If components do not appear:

  • Ensure the script is placed inside the <head> section.

  • Confirm there are no CSP (Content Security Policy) restrictions blocking loader.bridged.media.

  • Check for JavaScript errors in the console.

  • Verify that your domain is authorized within Bridged.