Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.fluxomail.com/llms.txt

Use this file to discover all available pages before exploring further.

Why it matters Marketers need flexible, intuitive journeys that react to real user behavior. Many tools are either too simple or too complex. Event‑driven journeys balance power and ease. How it works
  • Triggers: Product events (signup, upgrade), attributes (plan, LTV), or time‑based schedules
  • Branching: If/then logic, delays, exit conditions, and A/B branches
  • Personalization: Templates render with user data; preferences respected per contact
  • Measurement: Per‑node delivery, open/click, and conversion tracking
  • Guardrails: Bulk policies, unsubscribe handling, and rate controls per org
Benefits
  • Launch sophisticated flows without engineering tickets
  • Test and iterate faster with built‑in A/B paths
  • Drive higher engagement through timing and relevance
Best practices
  • Keep branches simple; test one hypothesis per flow.
  • Use idempotent triggers; deduplicate with event IDs.
  • Respect user preferences at every node.
Success metrics
  • Activation/retention deltas per journey
  • Open/click rate improvements vs. control
  • Time to launch a new flow
Related APIs
  • Send: POST /api/v1/emails/send
  • Preferences: GET/POST /api/v1/preferences