Overview

There are two ways to gather data.

• Dashboard in the back office: perfect for gaining quick insights into key behavioral metrics without the need Watchers provides a robust method for additional integration. No extra setup is required partners to access this data.
• Data collection via webhook: recommended for those needing deeper, receive real-time analytics. This approach involves setting up a webhook URL in the admin panel to receive event data directly in your system. These on user interactions within chat environments by sending events can be used directly to create custom scenarios triggered through your backend, such as rewarding users for specific actions.

Back Office Dashboard

The back office dashboard includes the following sections and functionalities:

1. Overview Metrics
   1. DAU/WAU/MAU metrics available for daily, weekly, and monthly user engagement tracking.
   2. Messages and User Activity
   3. Metrics for total messages sent, animated reactions, and reactions to messages are available for the last 90 days and 6 months.
   4. Active users and users who sent at least one message are tracked over the same periods for comprehensive insights.
   5. Active users for a particular period
   6. Copy-betting widgets usage - if activated (a number of shared bets, a number of clicks on "copy button")
   7. Win-sharing widget usage - if activated (a number of shared wins, and a number of click on the game in-widget button)
2. Data Updates
   1. A "Refresh" button for instant data updates and then refresh the page.
   2. Automated synchronisation with the latest metrics occurs at 00:00 GMT (0).

This dashboard system allows partners to track key behavioural metrics in chats. For deeper analytics, we recommend implementing a system to monitor and respond to user activities, ensuring seamless integration with your data collection via a webhook, which is described in the next section.

Webhooks

📘

Note: All event timestamps are stored in GMT+0. Please take this into account when building charts to ensure accurate time-based analysis. handling protocols.

Enabling Event Tracking

Webhooks can be configured to receive real-time events directly into an external database. Here’s how to set it up:

All Events Webhook: To begin receiving chats, are tagged. A list of events can be found below.

1. Enable events, enable this feature through the toggle under the "All events" section.
2. Provide a valid URL where events Admin Panel. Once enabled, our system will be sent.
3. Click "Save" to transmit event data to confirm the settings.
4. Use the "Test" button to verify the webhook configuration.

Room Events Webhook:

1. Enable the toggle under the "Rooms" section.
2. Provide the desired URL for room-specific events.
3. Events include:
   1. Create your specified API endpoint each time a scheduled room is created.
   2. Updates to scheduled room details (date, time, name), including status changes.
   3. Deletion of a scheduled room.
   4. Updates to the list of users with voice permissions (speakers) whenever room data is modified.
4. Save and test relevant user interaction occurs within the configuration as needed.

Webhooks enable seamless integration of platform events into external systems for further analysis and processing.

API Endpoint Requirements

Each event is communicated via a POST request to your API. The general structure of these requests is as follows:

{
"event": "event_name",
"value": {
	"user_id": "user_id",
	"project": "project_name",
	...other fields depends on event
	}
}

Recommendations for Data Storage and Analysis Tools

ClickHouse is a columnar database management system that is ideal for handling large volumes of event data due to its:

• High performance for real-time data ingestion.
• Excellent support for analytical queries.
• Compatibility with structured and semi-structured data formats.

Recommended Steps:

• Create a dedicated table for events: Depending on your specific needs, design a schema that includes necessary fields such as event_type, user_id, timestamp, and additional properties.
• Process webhook events directly: Capture webhook payloads in real-time and write them into ClickHouse using an HTTP endpoint.
• Partition data: Partition your tables by time (e.g., daily or hourly) to optimize query performance and simplify data management.

_Optional: If you anticipate high throughput or require buffering, consider integrating tools like Kafka to preprocess or distribute webhook events before storing them in ClickHouse.

Properties Contained in EVERY Event

Important: These fields are automatically added to ALL events by the system.

Events and Properties

This section outlines the key events tracked for product analytics, offering insights into user behavior and interactions within chats. Each event is detailed in the table below, including its name, associated properties, and a brief description.

List of Events

🚧

Note: Events highlighted in bold in the ‘Event’ column are mandatory for tracking basic product metrics related to user interactions within the chat.

Example Payload

{
  "event": "session_started",
  "value": {
    "user_id": "BUmXxFyNMNE6FUVhL+ECSQ==",
    "event_id": "16888417",
    "event_name": "session_started",
    "created_at": "2026-01-14T12:30:45.123Z",
    "source_url": "https://chat.example.com/room/123",
    "user_name": "John Doe",
    "nickname": "John Doe",
    "room_title": "EPL Final Discussion",
    "decrypted_user_id": "user_12345",
    "platform": "web",
    "screen_size": "1920x1080",
    "platformUserAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36",
    "project": "partner-prod",
    "source": "room",
    "read_only": false,
    "room_status": "on_air"
  },
  "key": "JGMHFqonZuwKeoly+bzNnw=="
}

Events Reference

Note: Events marked with bold are mandatory for tracking basic product metrics. All timestamps are stored in GMT+0.

Session & Room Events

Onboarding Events

Settings Events

User List Events

Messaging Events

Moderation Events

Emotions & Reactions Events

Stickers Events

Poll/Quiz Events

Marketing Offers (Highlights) Events

Stream & Connection Events

Feedback Form Events

Note: The following feedback events are defined but not yet implemented:

• ff_stream_type_of_problem_selected
• ff_stream_connection_tested
• ff_stream_success
• ff_stream_closed

Copy-betting Events

Win-sharing Events

Giveaway Events

Records (Audio Playback) Events

Info Pop-ups Events

Autotranslate Events

User Following Events

Thread Events

Personal Chat Events

Notification Events

Slow Mode Events

Widget Events

Miscellaneous Events

Backend Events (via Kafka)

These events are generated by backend services. They are sent to ClickHouse via Kafka topics.

Note: Backend events use Kafka topics pattern: webbackend.event.{event-name}.0 or adminproxy.event.{event-name}.0

User Activity Events

user_join

Triggered when user joins a room.

{
  "event": "user_join",
  "value": {
    "project": "partner-prod",
    "external_user_id": "user_12345",
    "room_id": "16888417",
    "is_bot": false,
    "is_moder": false
  }
}

user_leave

Triggered when user leaves a room.

{
  "event": "user_leave",
  "value": {
    "project": "partner-prod",
    "external_user_id": "user_12345",
    "room_id": "16888417"
  }
}

user_disconnect

Triggered when user disconnects from WebSocket.

{
  "event": "user_disconnect",
  "value": {
    "project": "partner-prod",
    "external_user_id": "user_12345"
  }
}

user_login

Triggered on user authentication.

{
  "event": "user_login",
  "value": {
    "project": "partner-prod",
    "external_user_id": "user_12345",
    "ip": "192.168.1.100"
  }
}

Messaging Events

thread_create

Triggered when a new thread is created.

{
  "event": "thread_create",
  "value": {
    "project": "partner-prod",
    "external_user_id": "user_12345",
    "room_id": "16888417",
    "thread_id": "thread_789"
  }
}

reaction_create

Triggered when user adds a reaction to a message.

{
  "event": "reaction_create",
  "value": {
    "project": "partner-prod",
    "external_user_id": "user_12345",
    "message_id": "msg_456",
    "reaction": "👍"
  }
}

message_reply

Triggered when user replies to a message.

{
  "event": "message_reply",
  "value": {
    "project": "partner-prod",
    "external_user_id": "user_12345",
    "message_id": "msg_789",
    "reply_to_id": "msg_456"
  }
}

message_moderation

Triggered when a message is moderated (hidden, deleted, etc.).

{
  "event": "message_moderation",
  "value": {
    "project": "partner-prod",
    "message_id": "msg_456",
    "action": "hide",
    "reason": "spam"
  }
}

Content Processing Events

text_translate

Triggered when text is translated.

{
  "event": "text_translate",
  "value": {
    "project": "partner-prod",
    "from_lang": "ru",
    "to_lang": "en",
    "chars": 156
  }
}

file_upload

Triggered when a file is uploaded.

{
  "event": "file_upload",
  "value": {
    "project": "partner-prod",
    "name": "image.png",
    "size": 245678
  }
}

pic_moderation

Triggered when an image is processed by moderation system.

{
  "event": "pic_moderation",
  "value": {
    "project": "partner-prod",
    "image_id": "img_123",
    "result": "approved"
  }
}

Invitation Events (Admin Proxy)

invitation_create

Triggered when admin creates an invitation.

{
  "event": "invitation_create",
  "value": {
    "project": "partner-prod",
    "admin_id": "admin_001",
    "token": "inv_abc123"
  }
}

invitation_update

Triggered when invitation is updated.

{
  "event": "invitation_update",
  "value": {
    "project": "partner-prod",
    "admin_id": "admin_001",
    "token": "inv_abc123",
    "is_active": false
  }
}

invitation_delete

Triggered when invitation is deleted.

{
  "event": "invitation_delete",
  "value": {
    "project": "partner-prod",
    "admin_id": "admin_001",
    "token": "inv_abc123"
  }
}

Backend Events Summary

Admin Panel Events

Events from the admin panel (webadmin). These events track admin actions for audit purposes.

Note: All admin events include base fields: user_id (admin ID), project, name (admin name), role.

Content Management

admin_message_sent

Admin sends a message to chat.

{
  "event": "admin_message_sent",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "name": "Admin User",
    "role": "admin",
    "room_id": "16888417",
    "message_id": "msg_123",
    "text": "Welcome to the chat!"
  }
}

admin_pin_created / admin_pin_deleted

Admin creates or deletes a pinned message.

{
  "event": "admin_pin_created",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "room_id": "16888417",
    "message_id": "msg_456",
    "title": "Important announcement"
  }
}

admin_autopost_created / admin_autopost_edited / admin_autopost_deleted

Admin manages autoposting.

{
  "event": "admin_autopost_created",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "autopost_id": "ap_123",
    "content": "Scheduled message content",
    "schedule": "0 12 * * *",
    "room_id": "16888417"
  }
}

admin_highlight_created / admin_highlight_edited / admin_highlight_deleted

Admin manages marketing highlights.

{
  "event": "admin_highlight_created",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "highlight_id": "hl_123",
    "content": "Special offer!",
    "button_text": "Claim now",
    "url": "https://example.com/offer",
    "start_date": "2026-01-15T00:00:00Z",
    "end_date": "2026-01-20T23:59:59Z"
  }
}

admin_poll_created / admin_poll_deleted

Admin manages polls/quizzes.

{
  "event": "admin_poll_created",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "poll_id": "poll_123",
    "type": "quiz",
    "question": "Who will win?",
    "answers": ["Team A", "Team B", "Draw"],
    "correct_answer": 0,
    "room_id": "16888417"
  }
}

User Management

admin_user_banned

Admin bans a user.

{
  "event": "admin_user_banned",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "banned_user_id": "user_456",
    "ban_level": "permanent",
    "reason": "Spam",
    "room_id": "16888417"
  }
}

admin_user_unbanned

Admin unbans a user.

{
  "event": "admin_user_unbanned",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "unbanned_user_id": "user_456"
  }
}

admin_message_deleted

Admin deletes a user's message.

{
  "event": "admin_message_deleted",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "message_id": "msg_789",
    "message_author_id": "user_456",
    "reason": "Inappropriate content"
  }
}

Room Management

admin_room_created

Admin creates a new room.

{
  "event": "admin_room_created",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "room_id": "16888418",
    "title": "Champions League Final",
    "start_date": "2026-05-30T20:00:00Z",
    "status": "soon"
  }
}

admin_room_updated

Admin updates room settings.

{
  "event": "admin_room_updated",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "room_id": "16888417",
    "title": "Updated Room Title",
    "status": "on_air",
    "changed_fields": ["title", "status"]
  }
}

admin_room_deleted

Admin deletes a room.

{
  "event": "admin_room_deleted",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "room_id": "16888417"
  }
}

Settings Changes

admin_settings_updated

Admin changes project settings.

{
  "event": "admin_settings_updated",
  "value": {
    "user_id": "admin_001",
    "project": "partner-prod",
    "category": "moderation",
    "opai_is_enabled": true,
    "gcp_is_enabled": false,
    "auto_hide_is_enabled": true,
    "auto_ban_is_enabled": false
  }
}

Common settings categories and fields:

Admin Events Summary

Q&A on Data Storage and Processing

1. Location of Storage and Processing Data is processed and stored entirely within Google Cloud infrastructure. Data distribution is carried out based on territorial principles to ensure compliance with local data protection laws and regulations. For instance, data subject to GDPR regulations is stored in Google Cloud’s European regions. This approach provides enhanced protection a complete understanding of users’ personal data and ensures compliance with GDPR requirements for data processing and storage within the European Union. We strictly adhere to Google Cloud’s policies and technical security measures to safeguard our users’ data in line with best practices and international standards.

2. How Long? We retain users’ personal data only as long as necessary to provide our services in accordance with the contract and GDPR requirements. Once the data is no longer needed for these purposes, it is deleted or anonymized. Our processes ensure compliance with GDPR’s principle of storage limitation, and we regularly review stored data to remove any unnecessary information.

Scenarios and Retention Periods for Data Deletion:

a. End of Collaboration with a Partner. When the collaboration (contract) with a partner ends, we delete all data accumulated during the partnership, except for information that may be required by regulators. We ensure no information is retained longer than necessary.

b. User-Initiated Data Deletion:

• If a user or their representative requests data deletion from the platform where the chat is integrated, all data related to the user is erased.

• Users can delete their accounts through the chat interface. After deletion, chat messages what events are anonymized immediately, and all other user data is deleted within 30 days of the request. During this 30-day period, the user has the option to recover their data. After this period, all user data stored on Watchers’ side is permanently deleted.

• Users can also delete their messages sent in the chat. Once deleted, the message becomes hidden for all chat users and is marked as deleted in the database. After 30 days, the message is also removed from the message feed in the admin panel. However, if the message had any complaints filed against it, it will continue to appear in the report list. Once the complaints are reviewed and processed, the message will be moved to the archive

c. API Tracked, including payload examples for immediate data deletion. We provide an API that allows Watchers platform users to send requests for the immediate deletion of all data associated with each specific user, except for data required to meet regulatory requirements. This ensures partners can respond to user deletion requests promptly and securely, further enhancing GDPR compliance.

3. What Type of Data is Stored and Processed To ensure the operation of our chats and analyze user interactions, we work with two types of data:

• Operational Data: These data are necessary for the direct operation of the chats. They include the user's name or nickname, which may be classified as personal data. We use these data solely so that users can use our chats without issues.
• Chat Name / Nickname
• IP (optional)
• User messages
• Analytical Data: These data are used event, refer to analyze how users interact with our chats and which features they use. For analytics, we apply anonymized data, meaning they contain no personal information about the user. detailed event list section below. This allows us section will help you configure your systems to improve our services without compromising user confidentiality. Thus, we clearly differentiate data necessary for the operation of the chats (operational) handle and data necessary for analysis and improvement of our services (analytical), while ensuring the protection of our users' personal information.