Event Payloads: The Engagement Engine

Events track real-time actions. The more metadata you include in the value object, the more powerful your targeting becomes.

Standard Payload Structure

All data should be sent in JSON format. Every event payload must include the unique user identifier and a timestamp to ensure accurate journey mapping.

Standard Event Payload

{
    "event": "some_event",
    "user_id": "some_user",
    "user_attributes": {
        "any_attr": "any_name"
    },
    "timestamp": "2025-01-01 12:00:00",      
    "value": {
        "any_key": "any_value",
        ....
    }
}

Below are some of the essential triggers for an iGaming environment, followed by some recommended JSON payload structures.

• User Management and KYC

1. customer_registration

2. kyc_verification

3. login

4. player_update

• Payments and Financials

1. deposit

2. withdrawal

• Sports Betting

1. add_to_betslip

2. bet_placed

3. bet_settled

• Casino

1. casino_wager_placed

2. casino_wager_settled

• Bingo

1. bingo_ticket_purchase

2. bingo_ticket_purchase

3. bingo_ticket_settlement

• Lottery

1. lottery_ticket_purchase

2. lottery_ticket_settlement

• Promotions and Bonuses

1. bonus_awarded

2. bonus_expired

3. bonus_used