Runtime Behavior

The runtime is the script that runs Fluxyn in the browser.

Startup order

When the runtime loads, it fetches the application bootstrap config first.

That is how it learns:

• trigger settings
• held events
• bypass events
• queue rules

Then it can initialize only the listeners it needs and replay any existing dataLayer items with the correct rules already in place.

Normal event processing

• Event pushes with an event key can trigger flows.
• Eventless pushes update page state only.
• $ represents the current merged page-state snapshot.
• $eventData remains the raw current event object.
• Built-in browser listeners can emit events like tf.click, tf.scroll, and tf.history_change.

When events are being held

• bypass events still run
• other event pushes queue
• eventless state updates still merge immediately
• queued events replay in order when blockers are released

Related guides

• Data layer and page state
• Held events and bypass events