Documentation · Analytics

Analytics in Fluxly: product analytics, profiles, and messaging in one tool

Fluxly is a modern analytics layer for SaaS and subscription businesses. It combines the best of PostHog (event analytics and product insight) and Customer.io (messaging and journeys) in a single place with more fluid, accurate customer data.

Flux · meaning

In physics and systems, flux means flow. In Fluxly, it means the continuous, lossless flow of customer data across analytics, profiles, and messaging.

Events and traits are not trapped in separate tools. They move as one stream so every chart, segment, and campaign sees the same truth.

Why this matters

No more tedious connections between separate analytics and email tools.
One profile per user across web, product, and billing.
Everything from events to profiles to automations lives in one tool.

Easy setup: JS SDK and HTTP API

Fluxly is designed for technical teams. You can start sending data in minutes using the browser SDK or plain HTTP requests from any backend or worker.

Choose your example

Under the hood, Fluxly normalizes SDK and HTTP payloads into the same event schema, enriches them with context, and stitches everything into a single profile timeline.

That means funnels, segments, and lifecycle metrics always read from one source of truth: no drift between product analytics and messaging data.

<!-- Fluxly Analytics -->
<script src="https://cdn.getfluxly.com/sdk.js" async></script>
<script>
  window.fluxly = window.fluxly || [];

  fluxly.push(["init", {
    projectId: "demo-project-id",
    apiKey: "pk_live_xxxxx"
  }]);

  // Auto page view
  fluxly.push(["page"]);
</script>

import requests

requests.post(
    "https://api.getfluxly.com/v1/events",
    headers={
        "Content-Type": "application/json",
        "X-API-Key": "pk_live_xxxxx",
    },
    json={
        "event": "subscription_created",
        "profile_id": "user_123",
        "properties": {
            "plan": "starter",
            "amount": 2900,
            "currency": "USD",
        },
        "context": {
            "source": "django_backend",
        },
    },
    timeout=2,
)

def handle_stripe_payment(event):
    user_id = event["data"]["object"]["customer"]

    requests.post(
        "https://api.getfluxly.com/v1/events",
        headers={"X-API-Key": "pk_live_xxxxx"},
        json={
            "event": "payment_succeeded",
            "profile_id": user_id,
            "properties": {
                "amount": event["data"]["object"]["amount"],
                "currency": "USD",
            },
        },
    )

Analytics features: one place for product and lifecycle insight

Fluxly works like a focused analytics and customer data platform tailored to SaaS and SMB software businesses. You get event tracking, funnels, retention, and user journeys alongside messaging performance, all on top of a unified profile model.

Event analytics and funnels

Track page views and custom events from web and backend.
Build funnels to see where users drop during onboarding or checkout.
Analyze which sources and campaigns produce the most revenue.

Unified customer profiles

Each profile has a complete timeline of events and messages.
Attach traits from product, billing, and support systems.
Build segments from behaviour, traits, and lifecycle stage.

Lifecycle messaging analytics

Connect SES, Mailgun, SMTP2GO, or any SMTP provider.
Measure deliverability, opens, clicks, and revenue per flow.
Attribute message performance back to concrete user behaviour.

Example use cases with Fluxly analytics

Because analytics, profiles, and messaging share the same data model, you can ship flows that usually require stitching multiple tools together.

Onboarding activation

Track feature usage and trigger education emails when users stall.

Event: project_created, integration_connected.
Measure: time to first value and activation rate.
Act: send targeted nudges based on missing steps.

Revenue cohort analysis

Combine payment events with product behaviour to see which cohorts expand.

Event: subscription_created, seat_added.
Dimension: source, plan, team size, industry.
Outcome: focus marketing spend on high-ROI sources.

Churn prevention and win-back

Detect drop-offs early using a mix of usage and billing signals, then react automatically.

Signals: fewer logins, failed invoices, feature decay.
Segment: “churn risk” profiles in the last 30 days.
Flow: send helpful interventions, not just discounts.

How Fluxly compares to PostHog and Customer.io

Fluxly is not a generic ESP or a generic analytics platform. It is a focused tool for SaaS founders, SMB owners, and product-led teams that want the strengths of PostHog and Customer.io in one place, with shared profiles and less integration work.

Versus PostHog

Similar: event analytics, funnels, and product insights.
Different: built-in lifecycle messaging on the same profiles.
Benefit: no separate messaging stack to wire on top.

Versus Customer.io

Similar: event-based messaging and journeys.
Different: product analytics and funnels using the same events.
Benefit: fewer discrepancies between “marketing data” and “product data”.

One stop for analytics needs

Product teams see usage and outcomes in one interface.
Growth teams see source, revenue, and lifecycle metrics together.
Engineering owns one integration instead of three.

Designed as documentation, useful as a decision guide

This analytics page is written as a technical document so search engines and human readers can understand what Fluxly does: event analytics, customer data, and lifecycle messaging on your own email infrastructure for SaaS and SMB products.

If you are exploring alternatives to product analytics tools like PostHog or messaging tools like Customer.io, Fluxly is a good fit when you want a single, accurate source of truth for user behaviour and messaging performance, especially if you run a SaaS or subscription business targeting US or EU customers.

Next step

Join the waitlist to use Fluxly for product analytics and lifecycle messaging.