Skip to main content

Overview

Event tracking is the foundation of EngageFabric’s gamification system. When players perform actions in your application, you send events to EngageFabric. The Rules Engine then evaluates these events and automatically triggers rewards like XP, currency, quest progress, and badges.

How It Works

Tracking Events

Basic Event

Event with Idempotency

Use idempotency keys to prevent duplicate event processing:

Common Event Types

Here are recommended event types for different use cases:

Learning Platform

E-commerce

Fitness App

Batch Events

Send multiple events in a single request for better performance:

Rules Engine Integration

Events are processed by the Rules Engine to trigger automated rewards.

Example Rule Configuration

This rule:
  1. Triggers on lesson_completed events
  2. Checks if score >= 80
  3. Awards 100 XP, 25 coins, and progresses a quest

Event Properties

Properties provide context for rule evaluation:

Real-Time Updates

When events trigger rewards, connected clients receive real-time updates via WebSocket:

Best Practices

Consistent Naming

Use snake_case for event types: lesson_completed, purchase_made

Rich Properties

Include relevant context in properties for flexible rule creation

Idempotency Keys

Use idempotency keys for important events to prevent duplicates

Batch When Possible

Batch multiple events together to reduce API calls

Debugging Events

View Event History

Check Processing Status

Rules Engine

Configure rules to respond to events

Player Management

Learn about player state and profiles