Sunbird UCI
  • Overview of Sunbird UCI
  • 📙Learn
    • UCI use cases
    • UCI for Education(Case study)
    • Tech Overview
      • Glossary
      • High-level Architecture Design
      • Design Principles
      • Standards
  • 🚀Use
    • Choose your Persona
    • Adopter - Install and use UCI
      • Pre-requisites, Installation Setup, Post Setup
      • Setting up your very first conversation
      • API Documentation
      • Data Exhaust and Analytics
      • Posthog Event
      • Whatsapp (Netcore)
      • Environment Variables
    • Developer - Contribute to UCI
      • UCI Basics
        • XMessage Specification
        • Transformers
          • ODK Transformer
            • Interactive-Messages
            • Media Messages
            • Location
          • Broadcast Transformer
        • Adapters
          • Firebase Notification Adapter
        • User Segment
        • Schema Overview
          • UCI Core Schema
            • XMessage Schema
            • Assessment DB Schema
          • UCI API Schema
      • Development environment
        • Backend Setup
        • Setting up IDE
        • Environment variable setup
        • Debug services
        • Build and Execute UCI
        • Frontend Setup (Admin Console)
        • Frontend Setup (PWA)
        • Transport Socket
      • API Documentation
        • Bot Setup APIs
        • History APIs
        • Direct Message APIs
        • Vault APIs
      • Database Schema
        • Cassandra Xmessage Database
        • Postgres Forms Database
        • Postgres User Analytics Database
        • Postgres Comms Database
      • Contribution Guide
        • Your first PR
        • Contribute an Adapter
        • Adapter Implementation
        • Create a Transformer
    • Contact the administrator
  • ✅Releases
    • Release V2
  • 🤝Engage
    • Software License
    • Acceptable Use Policy
    • Terms of Service
    • Source Code
    • Discussion Forum
Powered by GitBook
On this page
  • Introduction
  • 1. Table Schema

Was this helpful?

Edit on GitHub
  1. Use
  2. Developer - Contribute to UCI
  3. Database Schema

Postgres User Analytics Database

Introduction

This database is built using PostgreSQL, and its primary role is to keep track of the delivery status of notifications and their current status. It helps us generate final reports that show which notifications were sent, which users received them, and which users clicked on them. We use this database to store information about messages that were successfully delivered and messages that were read by users.

1. Table Schema

  • Table Name - delivery_report

Column Name
Type
Description

id

UUID

Unique identifier for the record.

external_id

Varchar

A unique identifier generated by the transaction layer when sending notifications. This identifier is used on the Android side to manage notifications.

user_id

Varchar

Identifier of the user its kind of Mobile/Phone number.

bot_id

Varchar

This is the bot id to identifiy bot related information.

bot_name

Varchar

This is the bot name to show the bot name on the ui.

fcm_token

Varchar

Firebase Cloud Messaging (FCM) token for notifications.

message_state

Varchar

State or status of the message like DELIVERED, READ.

cass_id

Varchar

Cassandra id to check the notification related information like xmessage, fcm messageid etc.

created_on

Timestamp

Timestamp indicating when the record was created.

---

PreviousPostgres Forms DatabaseNextPostgres Comms Database

Last updated 1 year ago

Was this helpful?

🚀