Get started with GetFluxly
GetFluxly does two jobs that usually need two separate tools. It is an analytics tool, so you can see what people actually do on your site or app. And it is an email tool, so you can message those same people based on what they did. Both halves share one customer list, so you never have to copy data between an analytics product and an email product, and an email can react to something a person did seconds ago.
This page is the guided tour. It walks the whole journey from creating an account to your first automation, and it explains why each step exists, not just which button to press. Where a step involves code, we link to the technical page instead of repeating it here. If you are a developer who just wants to send an event, jump straight to the Quickstart.
Here is the whole journey at a glance. Each card jumps to that step:
You do not have to finish everything in one sitting. Steps 1 to 3 get you useful analytics on day one. Steps 4 to 7 are what turn that data into email your users actually want. Steps 8 and 9 help you learn from all of it.
Create your account and workspace
Sign up at app.getfluxly.com. There is no password to remember: we email you a sign-in link or a one-time code, or you can continue with Google or GitHub.
Right after signup, a short setup flow asks for your name and the name of your product, then creates your first workspace. A workspace is your product's home inside GetFluxly. Everything in this guide, the events, the people, the emails, the automations, lives inside it. In a few places the app also calls it a project; they are the same thing.
Along the way you will be asked to acknowledge two house rules, and they are worth knowing before you invest time:
While a visitor is anonymous, GetFluxly does not plant cookies or hidden identifiers in their browser.
Customers, sign-ups, people who opted in. Cold lists and purchased lists are not allowed.
Every new account starts with a 14 day free trial of the full product, no card needed. After the trial, GetFluxly has a single plan that scales with the number of people you track.
Install GetFluxly in your product
Why it matters Every other step depends on data. Until your site or app tells GetFluxly what is happening, your dashboards stay empty and there is nobody to email. Installing early also means your history starts building now, so by the time you send your first email you already know who is active and who is not.
How to do it Your new workspace opens with a Get started page that holds your install snippet and your API key. There are a few paths, pick whichever fits how your product is built:
- A small script tag you paste into your website once. This is the fastest path and needs no programming beyond copy and paste. Using a site builder? There are step-by-step pages for Webflow and Framer.
- An SDK, a small library for your framework or backend. See the SDKs overview for browser, React, Next.js, Node, Python, and Ruby.
- Let your coding assistant do it. The Get started page can hand you a ready-made prompt or rules file for tools like Cursor or Claude Code, so an AI assistant wires GetFluxly into your codebase for you.
- Not the technical person on your team? Send the snippet from the Get started page to whoever runs your website. It is a one-time paste.
Once installed, GetFluxly starts recording the basics on its own: page views, clicks, form submits (only the names of the fields, never what people type into them), and page errors. You do not have to define anything up front. Later, you or your developer can add custom events for moments that matter to your business, like "started trial" or "created invoice"; the Quickstart shows how in a few lines.
Note: cookieless tracking is the default. Anonymous visitors are counted without anything being stored in their browser, which is friendlier to your users and to privacy laws. You stay in control of the details under Settings, in Sources and SDKs and in Retention and privacy.
If you run more than one site, say a marketing site, a docs site, and the app itself, you can track them all in one workspace and still tell them apart. That is what Surfaces are for.
Check that events are arriving
Why it matters A broken install is invisible until you go looking. Confirming data flow takes a minute now and saves you discovering weeks later that half your traffic was never recorded.
How to do it Two easy checks inside the app.
- The setup checklist on your workspace's Get started page ticks off "Install the SDK" by itself the moment your first event lands. No manual confirmation needed.
- Open the events area of your workspace and watch the live feed. Visit your own website in another tab, click around, and you should see your own page views and clicks appear within moments.
If nothing shows up, the most common causes are the snippet not being deployed yet or an ad blocker on your own browser. The install pages for Webflow and Framer include short troubleshooting lists.
Tell GetFluxly who your users are
Why it matters Out of the box, GetFluxly sees visitors as anonymous. That is fine for analytics, but you cannot email "anonymous visitor number 8,341". For the email half of GetFluxly to work, your app needs to introduce your users: this visitor is Jane, and her email address is jane@example.com.
How to do it When someone signs up or logs in, your app makes a one-line "identify" call that tells GetFluxly who the person is, along with traits: simple facts about them like their email address, name, or plan. From then on, everything that person does is attached to their profile, and everything they did anonymously before signing up is stitched onto it too, so you keep their full story. This is a small developer task; the Identity model page explains the idea, and the stitching guide covers how the joining works.
You can browse the results in the People section of your workspace, where every identified user has a profile showing who they are and what they have done.
Already have a customer list from a previous tool? You do not have to wait for everyone to log in. Upload a CSV under Settings, in Sources and SDKs, and GetFluxly creates profiles from it. The Contacts import page walks through the format and the consent rules.
Connect an email provider
Why it matters GetFluxly designs your emails, decides who gets them and when, and tracks what happens after. But the actual sending goes out through an email provider account that you own. This is deliberate: your sender reputation and your domain stay yours, instead of your deliverability depending on strangers sharing a pipe with you. Until a provider is connected, you can build everything, but nothing can be sent.
How to do it Go to Settings, then Email providers, and add one. GetFluxly works with Resend, Amazon SES, Mailgun, or any standard SMTP service. You paste in the credentials from your provider account, choose the from address and from name your emails should use, and save. Your credentials are encrypted and never shown again.
GetFluxly checks the connection in the background and marks the provider as verified when it is working; there is also a test button so you can confirm it on the spot. One more thing lives on this screen: the records that prove to inbox providers that you really own your from address (you may have seen the terms SPF and DKIM). The provider screen shows you what to set up, and for Amazon SES it can even create those records for you.
Add a tracking domain
Why it matters When GetFluxly measures whether an email was opened or a link was clicked, those measurements travel through a web address. By default that address is a shared GetFluxly one. A tracking domain replaces it with your own, for example track.yourcompany.com, which does two good things: the links in your emails carry your brand instead of ours, and inbox providers see consistent infrastructure behind your mail, which strengthens your sender reputation over time.
How to do it Go to Settings, then Tracking domains, and enter your domain. GetFluxly gives you two DNS records to add wherever you manage your domain, with field-by-field help for the common hosts like Cloudflare, GoDaddy, and Namecheap. Add the records, come back, and press Verify. This step is optional, but do it before you start sending in earnest; it is ten minutes of setup that quietly pays off in the inbox.
Build your first automation
Why it matters This is the payoff for everything above. An automation is an email flow you set up once that then runs by itself for every person who qualifies: welcome each new sign-up, nudge someone whose trial is ending, win back a customer who went quiet. Because GetFluxly already knows what each person did, these emails react to real behavior instead of being sent to everyone on a schedule.
How to do it Open Automations in your workspace and create a new one. You can start from scratch, or, easier for your first, pick one of the built-in examples such as the welcome series or the win-back flow; these arrive fully assembled and you just adjust the words and timing.
Every automation has the same shape, and it reads like a sentence:
- A trigger, the "when": an event happens, someone enters or leaves a segment, or a scheduled time arrives.
- Steps, the "then": send an email, wait a day, or branch based on what the person has done.
The emails inside an automation come from the Templates editor, where you design them visually and can send yourself a preview of any template to see exactly what your users will get. To switch an automation on, you need a verified email provider from step 5 and a finished template; until then it simply stays paused. You can pause any automation whenever you like, and there is a stop-all switch that halts every automation in the workspace at once.
Group people with segments
Why it matters You rarely want to email everyone. Segments let you describe an audience in plain rules, and GetFluxly keeps the membership up to date on its own. Define "trialing but hasn't invited a teammate" once, and it is always current, with people flowing in and out as their behavior changes. Segments are also what make automations feel personal: "entered the inactive segment" is a much better trigger than "it is Tuesday".
How to do it Open Segments in your workspace, create one, and build its rules. Rules can look at three kinds of things, and you can combine them with and/or logic:
- Who someone is: their traits, like plan, country, or sign-up date.
- What someone did: performed an event, or did not, within a time window. For example, "has not logged in for 30 days".
- Where they already belong: inside or outside another segment, so you can build on audiences you already made.
Once saved, a segment is reusable everywhere: as an automation trigger, inside automation branches, and as the audience for one-off broadcast emails.
Measure with funnels
Why it matters A funnel answers the question every product team asks: where do people give up? You define the path you expect users to take, for example visited pricing, started trial, subscribed, and GetFluxly shows how many people make each step and exactly where the drop-off happens. That tells you where to focus, and it pairs naturally with automations: found a step where people stall? Build an email that nudges exactly those people.
How to do it Open Funnels in your workspace and create one. GetFluxly drafts the first version from your most common events so you are not staring at an empty screen; edit the steps into the journey you care about, in order. The funnel counts people who complete the steps within a time window, a week by default, and you can change that to fit your product's pace.
Where to go next
You now know the shape of the whole platform. Some good next stops:
In the app, it is also worth a look at Settings for Retention and privacy (consent choices), Discovered events (every event name GetFluxly has seen), and Traits (every fact it knows about people).
