Event Structure
An event consists of:- Event Name: Identifies the action (e.g.,
profile_completed,song_liked) - Event Metadata: Optional details about the action
Basic Event
Event with Metadata
Best Practices
Event Naming Conventions
Use past tense for event names to indicate actions that have already occurred: ✅ Good Examples:song_liked- indicates the song was already likedprofile_completed- the profile completion action finishedvideo_watched- the video viewing is complete
like_song- present tense, unclear if action completedcomplete_profile- imperative formwatch_video- present tense
Events vs Orders
Orders are special events. When you use the Orders API, Gameball automatically creates a
place_order event. You don’t need to manually track order events.Use Orders API for: E-commerce purchases, cashback, redemption
Event-Based Campaigns
Events power campaigns through the Gameball dashboard:- Reward Campaigns: “Award 100 points for first
add_to_cartevent” - Communication Campaigns: “Send message when
add_to_cartincludes specific category” - Event Engine Operators: Equals, Different Values, Accumulative Total, Repeated Value