M
Meza AI

📊 Data Models Overview

Learn how data models work in Meza AI and how to configure them.

What is a Data Model?

A data model is a structured representation of your customer data that defines how information is organized, stored, and accessed within Meza AI. Data models provide a blueprint for mapping data from your databases and integrations to Meza AI's analytics engine.

Think of data models as the foundation of your customer success platform. They tell Meza AI where to find your customer data and how different pieces of information relate to each other.

How Data Models Work

Your Database
→ SQL Query →
Data Model
→ Analytics →
Insights

Each data model is configured with a SQL query that extracts data from your database. Meza AI runs these queries periodically to keep your customer data up to date.

AI-Driven Configuration

Meza AI uses AI to streamline data model configuration. During onboarding, our AI analyzes your database schema and suggests optimal data models with pre-built queries tailored to your data structure.

AI Suggestions

When configuring a data model, click "AI Suggest" to have Meza AI analyze your schema and generate an optimized query automatically.

Available Data Models

💡 Note

The Accounts Model is mandatory and must be configured first. All other models link to accounts through the account_id field.

Recommended Configuration Order

  1. Accounts Model (Required)

    Start here — this is the foundation for all other models.

  2. Users Model

    Add user-level tracking for engagement analytics.

  3. Product Activity Model

    Track product usage events and feature interactions.

  4. Subscription & Plans Models

    Add billing data for revenue insights.

  5. Support Tickets & Conversations

    These are auto-created when you connect Zendesk or Intercom.

Model Relationships

All data models are linked through the account_id field. This allows Meza AI to aggregate data at the account level and provide a complete view of each customer.

Account (account_id)
├── Users (user_id → account_id)
├── Product Activities (activity_id → account_id, user_id)
├── Subscriptions (subscription_id → account_id, plan_id)
├── Support Tickets (ticket_id → account_id)
├── Conversations (conversation_id → account_id)
└── Usage (account_id)

What's Next?