How it works
From raw events to automations you approve.
GetFluxly captures what people do in your product, turns it into unified profiles and live segments, and lets AI draft the lifecycle automations, ones you review and approve before a single message goes out.
Step 01
Connect your data
Drop in the SDK or send events straight from your backend. Browser and server events land in real time, no sampling and no nightly batch. One snippet starts the whole pipeline.
Step 02
Profiles assemble themselves
Identity resolution stitches anonymous activity to known users the moment someone signs in or is identified. Every event, trait, and session rolls up into one unified profile you can actually read.
Step 03
Segment by real behavior
Build live segments from what people actually did, not static lists. Membership updates itself as events arrive, so ‘inactive 30 days’ or ‘hit the usage limit’ always means what it says right now.
Step 04
Describe the automation
Tell the builder the outcome you want in a sentence. It assembles the triggers, waits, branches, and sends into an editable graph, working from your own segments, templates, and reserved traits, never your customers' raw data.
Step 05
Review, edit, approve
Every step is inspectable and editable. Change a wait, rewrite a branch, swap a template. Nothing leaves Draft until a human signs off, so the AI never ships anything on its own.
Step 06
It runs, deterministically
Once approved, your workers execute the exact graph you signed off on, through the email provider you already use. Same inputs, same behavior, every run logged and replayable.
The AI works from the shape of your data, not the data itself.
What the model sees
- Reserved traits
- Your templates
- Automation and segment structure
- Brand assets like your logo
What it never sees
- PII
- Raw profile values
- Event payloads
- Your customers' data
The AI drafts. It never decides on its own.
The model proposes structure from your segments, templates, and reserved traits. What actually runs is a deterministic graph you approved, versioned and logged, so the same inputs always produce the same behavior. No black box sending on your behalf.