Core concepts
Core Concepts
Understand the mental model behind Fluxyn so flows are easier to design, debug, and publish with confidence.
Fluxyn gets much easier once you understand a few core ideas well.
Everything in the product builds on the same foundations:
- an application defines where the runtime is allowed to run and how it should behave by default
- a flow defines what should happen after a trigger fires
- the client runtime executes that logic in the browser
- state and expressions let each execution reuse the right context at the right moment
If you are building production tracking or vendor integrations, these pages are worth reading carefully. They explain not just what the settings do, but why they exist.
In this Section
- The Client Runtime: How the browser script boots, listens, queues, and executes.
- Applications: The boundaries around domains, environments, and runtime settings.
- Flows: How visual logic is organized and executed.
- Triggers: The difference between explicit events and built-in browser listeners.
- Variables and Expressions: The data available during a run and how to reference it safely.
- Data Layer and Page State: How Fluxyn separates the current event from longer-lived session context.