Sign-up to silence
Someone signs up but never reaches activation. Your generic welcome email doesn't notice or react.
eventuser_signed_up
+ 0dwelcome email sent
+ 7dstill no project_created
missedno follow-up triggered
BetaFree for three months · opens by end of May 2026
Send emails based on what users actually do.
Trigger onboarding, nudges, trial reminders, and retention flows from real product events. Auto-capture browser and server analytics, build unified profiles, and ship behavior-triggered lifecycle email, from one platform with one SDK.
app.getfluxly.com / live
Live event stream
project: acme · last 60s
09:42:18pricing_viewed · neo@zion.devbrowser
09:42:11subscription_started · usr_847server
09:42:04project_created · usr_847server
09:41:58pageview · /dashboardbrowser
09:41:53identified · usr_847sdk
09:41:49click · #cta-signupbrowser
09:41:42pageview · /pricingbrowser
Customer profile
stitched · just nowN
planFree
last_seen3m ago
activationStep 2 / 4
pricing_views3 / 7d
Automation Upgrade nudge
when pricing_viewed ≥ 3trigger
wait 2 hoursdelay
send “Still thinking it over?”email
Use the email provider you already run.Native sending from GetFluxly is coming soon. Until then, plug in the relay your team already operates.
- Resend
- Mailgun
- Amazon SES
- Postmark
- SMTP2GO
- Custom SMTP
- GetFluxly Mail · Coming soon
The gap
Your users are doing important things. Your email tool doesn't know.
Email platforms send what you tell them to send. Behavior happens in your product. A nightly export, a brittle Zapier flow, or a custom sync job is the usual bridge, and it's the part that breaks when the lifecycle moments matter most.
High intent, no follow-up
A user views pricing three times in a week and doesn't upgrade. Your email tool can't see browsing behavior.
eventpricing_viewed × 3
traitplan = "free"
traitlast_seen = 2d ago
missedupgrade nudge never sent
Stalled new project
A team creates their first project, then never invites a teammate or runs their first action. The drop-off goes unnoticed.
eventproject_created
+ 3d0 invites sent
+ 3d0 events received
missedactivation nudge never sent
Quiet feature churn
A power user who used a key feature weekly stops using it. By the time you spot it in a dashboard, they're already half-gone.
eventfeature_used (12w avg)
- 14d0 occurrences
traitplan = "team"
missedretention save never sent
The platform
Track. Profile. Segment. Automate. Send.
Five primitives. One platform. The loop that turns product behavior into the right message at the right moment, without nightly exports or brittle Zapier flows.
01 · Track
Capture every signal.
Pageviews, clicks, forms, plus trusted server events. One JavaScript SDK or one HTTP API, installed in one line.
html
<!-- One tag. Pageviews, clicks, and forms auto-capture. --> <script> window.__GFLUX__ = { apiKey: "gflux_pub_live_REPLACE_ME", apiHost: "https://api.getfluxly.com" }; </script> <script src="https://cdn.jsdelivr.net/npm/@getfluxly/browser@latest/dist/gflux.iife.js"></script>
js
// React, Next.js, Vue, Svelte, anything bundled. $ npm install @getfluxly/browser import { initGFlux } from "@getfluxly/browser"; const gflux = initGFlux({ apiKey: "gflux_pub_live_REPLACE_ME", apiHost: "https://api.getfluxly.com" }); gflux?.page(); // Clicks and forms auto-capture from here.
curl
# Trusted server events stitch to the same customer record. curl https://api.getfluxly.com/v1/events/batch \ -H "Authorization: Bearer gflux_secret_live_REPLACE_ME" \ -H "Content-Type: application/json" \ -d '{ "events": [{ "event": "subscription_started", "external_id": "usr_847", "properties": { "plan": "team", "amount": 4900 } }] }'
02 · Profile
One unified profile.
Anonymous activity stitches to identified users automatically.
anon_8c2f…0a13browser
anon_a91b…ff04browser
usr_847server
03 · Segment
Group by behavior.
Filter on events, traits, and time. Live counts, no SQL.
iftraitplan = free
anddidpricing_viewed≥ 3 / 7d
anddid notsubscription_started
04 · Automate
Trigger from real events.
Wait, branch, delay, exit. Flows run on the customer profile, not on a list you maintain by hand.
1when project_created
2wait 24h
3if invited_teammate? false
4send “Invite your team”
5wait 3d · exit on event
05 · Send
Ship the moment.
Onboarding, nudges, retention, win-backs. Send through Resend, Mailgun, AWS SES, Postmark, or any SMTP relay. Outcomes flow back to the same profile.
acme <hello@acme.dev>
Still thinking it over, Neo?
Hey {{ first_name }}, saw you swung by pricing a few times this week. The Team plan is what most folks on your trajectory pick up. Reply with questions, or grab 15 minutes on a call.
Developers
One SDK. One line. Ship today.
No tags to glue together, no nightly export. The JavaScript SDK auto-captures browser behavior. The HTTP Events API handles trusted server events. Both write to the same customer profile, so server-only events still trigger lifecycle email reliably.
- Auto-capture pageviews, clicks, and forms
- Anonymous → identified stitching out of the box
- Type-safe events with custom properties
- GDPR-friendly: consent, DNT, GPC honored out of the box
~ / acme-app
$ npm install @getfluxly/browser
+ added 1 package in 0.6s
$ echo "GFLUX_BROWSER_KEY=gflux_pub_live_..." >> .env
$ cat src/app.tsx
import { initGFlux } from "@getfluxly/browser";
const gflux = initGFlux({
apiKey: process.env.GFLUX_BROWSER_KEY,
apiHost: "https://api.getfluxly.com",
});
gflux?.page();
// Clicks and forms auto-capture from here.The product
One dashboard for events, profiles, and automations.
A peek at the workspace. Manage projects, watch the live event stream, and edit automations in the same console.
app.getfluxly.com / dashboard
Events / 24h
12,418
↑ 8.2% vs last week
Active profiles
847
↑ 12 new today
Activation funnel · last 30 days
cohort: trial signups
user_signed_up1,204
project_created867
teammate_invited494
first_action349
subscription_started169
FAQ
Questions, answered.
Pricing, sending, imports, and how the platform fits the rest of the modern SaaS stack.
Built-in sending is in active development. Until it ships, plug in your own ESP (Resend, Mailgun, AWS SES, Postmark, SMTP2GO, or any SMTP relay) and GetFluxly handles everything else: events, profiles, segments, automations, and lifecycle email. When native sending lands you can migrate over for free, with extra perks if you joined during the early beta.
We haven't finalised pricing. The private beta is free for the first three months and runs through summer 2026. Beta members get grandfathered into whatever plans we ship later. If you want a heads-up the day pricing goes live, request access and we'll email you.
A subscriber is an email address that has received at least one message from GetFluxly in the last 60 days. Anonymous events don't count. Dormant contacts don't count. Never-emailed profiles don't count. You only pay for the people you're actively reaching.
CSV import is in development and lands with the end-of-May private beta. Upload existing subscribers, map columns to GetFluxly profile traits, identity links resolve automatically. Bring an existing list, drop in the SDK, start sending.
Two paths. The JavaScript SDK auto-captures pageviews, clicks, and forms in the browser. The HTTP Events API handles trusted server events (signup, billing, internal state changes). Both write to the same customer record, so server-only events still trigger lifecycle email reliably.
Identity stitching merges anonymous browser activity with the real user you eventually identify. A user visits your site, clicks around, signs up. Every event before and after signup lands on the same customer profile. Identity links are auditable and resolvable manually if anything ever looks off.
Yes. You decide what gets tracked. Auto-capture is opt-in per project. Identification only happens when the SDK is told a real user is present with consent. Profile traits are editable and deletable per user. The primitives you need for subject access and erasure requests are there.
The free private beta opens by the end of May 2026. Approved teams get three months of full platform access, no card on file. The application takes about a minute. The more context you share about your use case and event volume, the faster onboarding goes.
Private beta
Free for the first three months.
The beta opens by the end of May 2026. Accepted teams get three months of full GetFluxly platform access at no cost. The request takes about a minute. Share your use case and expected event volume so we can scope onboarding.
Prefer a direct conversation? Email hello@getfluxly.com. Slack Connect is available on request. Full security posture is at getfluxly.com/security.
Good fit if
- You have a SaaS product live (or close enough that real users are starting to use it).
- You want onboarding, activation, or retention email driven by what users actually do.
- You prefer a developer-friendly setup with a real SDK and a clean HTTP API over a marketing-only tool.
- You want one platform for events, profiles, and lifecycle email. Plug in your ESP today; native sending lands soon.