Skip to main content
Welcome to Zixflow’s event tracking system. This guide covers what events are, the core building blocks, and how to track your first event.

​
What is the Event System?

Zixflow’s event tracking system is a Customer Data Platform (CDP) that captures and organizes every user interaction in your application. Similar to platforms like Segment or Amplitude, it creates a complete, searchable history of how users engage with your product. What you can do with it:
  • Understand user behavior patterns and preferences
  • Trigger automated campaigns at the right moments
  • Analyze what drives conversions and retention
  • Make data-driven product and marketing decisions

​
How It Works

Every user action becomes a structured event that includes:
  • Who: Which user took the action (by ID or anonymous tracking)
  • What: The specific action they took (like “Purchased” or “Signed Up”)
  • When: The exact time it happened
  • Context: Details like what device they used, where they were, etc.
Once tracked, events are typically available within 2–5 seconds for campaigns, segments, and analytics.

​
Why Track Events?

GoalExamples
Product analyticsFeature adoption, activation, retention, cohorts
MarketingAttribution, personalization, abandoned-cart recovery
RevenueTrial-to-paid funnels, upgrades, churn risk
Lifecycle automationOnboarding, re-activation, upsell, win-back
For industry-specific patterns, see the scenario guides.

​
Key Concepts at a Glance

​
Events

Structured records of user actions — think Segment’s track() calls or Amplitude events. Examples: Signed Up, Feature Used, Trial Extended, Payment Failed

​
Users

Unified profiles across the anonymous → identified journey.
  • Anonymous: Pre-signup visitors tracked via browser/device ID — still useful for funnels and first-touch attribution
  • Identified: Post-signup/login users — cross-device tracking, messaging, and full journey merge
See Users & Identity for how merging works.

​
Attributes

Profile fields that describe who a user is and their current state (plan_type, trial_ends_at, etc.). Attributes = state. Events = changes to that state. See Attributes.

​
Devices

Endpoints (phone, tablet, browser) linked to a user or anonymous visitor so you can send push and understand cross-device behavior. See Devices & Push Notifications.

​
Your First Event

​
JavaScript (Web)

// After user creates account
Zixflow.track({
  name: 'Signed Up',
  properties: {
    plan: 'free',
    source: 'homepage'
  }
});

​
Flutter (Mobile)

// After user creates account
Zixflow.instance.track(
  name: 'Signed Up',
  properties: {
    'plan': 'free',
    'source': 'homepage',
  },
);
What happens: The SDK enriches the event, sends it securely, and Zixflow links it to the user profile. Your app gets an instant response; events are ready for use within a few seconds. Offline events are queued and sent when connectivity returns. For the full pipeline, see The Data Journey.

​
What You Can Do With Your Data

​
Trigger automated campaigns

  • User signs up → welcome series
  • User abandons cart → reminder after 2 hours
  • User hits usage limit → upgrade prompt

​
Analyze journeys

Conversion funnels, path analysis, and cohorts by signup source or plan.

​
Measure what matters

Activation rate, retention (D1/D7/D30), feature adoption, time to value, revenue metrics.

​
Reliability & Privacy

  • Events are queued locally if the network drops, then retried automatically
  • Transmission uses encrypted HTTPS
  • GDPR/CCPA-oriented controls: export, deletion, and opt-out support

​
Next Steps

​
Concepts

​
Implementation

​
SDK & API

Ready to dive deeper? Continue to Understanding Events →