The Client Runtime

The client runtime is the browser script that makes Fluxyn real on the page.

It is responsible for:

• booting with the correct application id
• loading the published configuration for that app
• attaching the listeners the application allows
• reading the data layer and page state
• executing matching flows when events happen

Startup Order and Network Footprint

At a high level, startup looks like this:

1. The script loads with your appId.
2. The runtime fetches the published payload for that application.
3. It evaluates application-level settings such as listeners and event queueing.
4. It attaches the listeners the app needs.
5. It processes any relevant existing window.dataLayer state.

The runtime is intentionally small in scope. It does not carry Studio UI behavior with it. Its job is execution, not editing.

Script Snippet Installation

For production, Fluxyn currently ships through the CDN script shown in the Application Script tab.

<script src="https://cdn.fluxyn.net/latest/rt.js?appId=YOUR_APP_ID"></script>

Live Preview uses the runtime debug relay to test the saved application branch before production release.

Event Processing Integrity

The runtime treats different kinds of pushes differently.

• A payload with an event name can start a flow if a trigger matches it.
• A payload without a trigger-worthy event may still update state for later flows.
• Each execution gets access to both the current event data and the current page state.

Event Queueing

Some implementations need to delay work until a setup flow has completed. Fluxyn supports that through application-level event queueing.

When queueing is enabled:

• incoming events are queued by default
• only Event Trigger nodes with Bypass queue enabled can run before the queue is released
• queued events replay after a flow calls Release Queue
• queued events replay in the same order they originally arrived

If queueing is disabled:

• all events run normally
• Fluxyn still updates consent state when your consent-update flow runs

The runtime stores queued events in sessionStorage and trims the oldest items automatically if storage pressure gets too high.