Main Product Integration with QuickPass Tasks

What are QuickPass Tasks

Tasks are a way to motivate users to be more active with the main product. Users see tasks like "Make 5 bets of 100+ rubles per day", complete them, and receive rewards.

How it Works

1. User performs familiar actions in the main product (bets, spins, games)
2. Main product sends an event to QuickPass as a structured object (json, protobuf, ...)
3. QuickPass checks: does the user have suitable tasks
4. If yes - counts progress, if task is completed - gives reward
5. User sees progress and gets motivation to continue playing

What the User Sees

In Task Interface

• List of available tasks with descriptions and rewards
• Completion progress (e.g., "3 out of 5 bets completed")
• Time remaining until task completion
• Received rewards

Task Example

"Make 5 bets of 100+ rubles per day"

• User activates the task
• With each bet ≥100 rubles, main product sends event to QuickPass
• QuickPass counts progress: 1/5, 2/5, 3/5, 4/5
• After the 5th bet, task completes, user receives reward

Requirements from Main Product Team

Minimum Requirements

1. Define Events - what user actions need to be tracked
2. Configure Data Sending - send structured object to QuickPass on each event
3. Agree on Rewards - if planning to give main product coins/bonuses through tasks

Technical Implementation of Data Transfer

Event Format:

{
  "user_id": "12345",
  "event_type": "bet_placed",
  "timestamp": "2024-01-15T14:30:00Z",
  "amount": 250.00,
  "currency": "RUB",
  "game_type": "roulette",
  "outcome": "win",
  "bet_type": "red"
}

Transfer Methods:

• REST API - HTTP POST requests with JSON objects
• Message Broker - Kafka/RabbitMQ for high-load systems
• Webhook - for real-time events

When to Send:

• Immediately after user action
• Asynchronously to avoid affecting main product performance
• With delivery guarantee for critical events

Types of Events That Can Be Tracked in Main Product

Gaming Actions

• Bets: placement, wins, losses
• Roulette: spins, wins, specific bet types
• Slots: games, wins, large payouts
• Card Games: rounds, victories, achievements
• etc.

Financial Operations

• Deposits: account top-ups
• Withdrawals: withdrawal requests
• Bonuses: promo code activation

Social Actions

• Profile: data filling, updates
• Referrals: inviting friends
• Activity: daily logins

How QuickPass Processes Events

What Happens When Event is Received

1. User Check - is user in QuickPass system
2. Active Tasks Search - what tasks are running for user
3. Condition Validation - does event match task requirements
4. Progress Update - counting completed action
5. Completion Check - is task fully completed
6. Reward Distribution - crediting coins, items, bonuses

Counting Rules

• Only actions after task activation are counted
• If task has minimum amount - smaller bets don't count
• Duplicate events are ignored
• Time frames are considered (day/week/month)

Main Product Reward Processing

When task completes and includes main product reward:

1. QuickPass Sends Crediting Request:

{
  "user_id": "12345",
  "reward_type": "bonus_coins",
  "amount": 100,
  "task_id": 123,
  "reason": "Task completion reward"
}

2. Main Product Processes Request:

   • Checks user existence
   • Credits bonus
   • Logs operation

3. QuickPass Response:

{
  "success": true,
  "transaction_id": "tx_789",
  "new_balance": 1500 // if needed
}

4. QuickPass Notifies User about received rewards

Analytics and Metrics

Key Indicators

• Percentage of users activating tasks
• Average number of completed tasks per user
• Impact of tasks on game frequency and bet sizes
• Retention rate of users with active tasks
• New user conversion through task chains

Integration Monitoring

• Number of processed events per second
• Percentage of successful event deliveries
• QuickPass API response time
• Number of event validation errors