> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Welcome to MoEngage!

> New to MoEngage? Learn how the platform works, the key concepts you'll see in the dashboard, and what to set up first.

MoEngage is a customer engagement platform. You send MoEngage data about your users and what they do in your app or website, and MoEngage builds one profile for each user. Everything else in the platform works from those profiles: you segment users, reach them across channels, personalize their experience, and analyze the results. Merlin AI, the AI layer of MoEngage, works across all of it.

This page explains how the platform fits together, the terms you'll see in the dashboard, and what to set up first.

<div className="moe-pmap not-prose" role="figure" aria-label="How MoEngage works: collect data, unify it into user profiles, engage users, and measure results, with Merlin AI across every stage.">
  <div className="moe-pmap-stages">
    <div className="moe-pmap-stage">
      <p className="moe-pmap-eyebrow">01 Collect</p>
      <p className="moe-pmap-title">Bring in your data</p>
      <p className="moe-pmap-text">Send users, events, and attributes from every source.</p>

      <ul className="moe-pmap-chips">
        <li>Web and mobile SDKs</li>
        <li>REST APIs</li>
        <li>File imports</li>
        <li>Data warehouses</li>
        <li>Partner integrations</li>
      </ul>
    </div>

    <span className="moe-pmap-flow" aria-hidden="true" />

    <div className="moe-pmap-stage">
      <p className="moe-pmap-eyebrow">02 Unify</p>
      <p className="moe-pmap-title">Know each user</p>
      <p className="moe-pmap-text">Merge the data into one profile per user.</p>

      <ul className="moe-pmap-chips">
        <li>User profiles</li>
        <li>Events</li>
        <li>User attributes</li>
        <li>Computed traits</li>
        <li>Identity resolution</li>
      </ul>
    </div>

    <span className="moe-pmap-flow" aria-hidden="true" />

    <div className="moe-pmap-stage">
      <p className="moe-pmap-eyebrow">03 Engage</p>
      <p className="moe-pmap-title">Reach the right users</p>
      <p className="moe-pmap-text">Target segments with campaigns and journeys.</p>

      <ul className="moe-pmap-chips">
        <li>Segments</li>
        <li>Campaigns</li>
        <li>Flows</li>
        <li>Personalize</li>
        <li>Inform</li>
        <li>Messaging channels</li>
      </ul>
    </div>

    <span className="moe-pmap-flow" aria-hidden="true" />

    <div className="moe-pmap-stage">
      <p className="moe-pmap-eyebrow">04 Measure</p>
      <p className="moe-pmap-title">Learn what worked</p>
      <p className="moe-pmap-text">Analyze behavior and campaign performance.</p>

      <ul className="moe-pmap-chips">
        <li>Behavior</li>
        <li>Funnels</li>
        <li>Retention</li>
        <li>Dashboards</li>
        <li>Campaign and flow stats</li>
      </ul>
    </div>
  </div>

  <div className="moe-pmap-ai">
    <p className="moe-pmap-eyebrow">Merlin AI across every stage</p>
    <p className="moe-pmap-text">Predict user behavior, pick the best time and channel, generate content, and automate decisions.</p>

    <ul className="moe-pmap-chips">
      <li>Predictions</li>
      <li>Best time to send</li>
      <li>Most preferred channel</li>
      <li>Copywriter and Designer</li>
      <li>Campaign and offer decisioning</li>
      <li>MCP server</li>
    </ul>
  </div>
</div>

## How MoEngage Works

Some features on this page depend on your MoEngage plan or a paid add-on. For example, Inform depends on your plan, event exports are part of the Streams add-on, and segment sync is part of the Connected Segments add-on.

<Info>
  Availability of this feature depends on your MoEngage plan and may require a paid add-on. To check what's available for your plan, refer to [Plans and Pricing](https://www.moengage.com/plans-and-pricing/). To get this feature, contact your MoEngage Customer Success Manager (CSM) or the Support team.
</Info>

### 1. Collect Data

Your developers integrate the MoEngage SDKs into your app or website and send server-side data through the REST APIs. Your data team can also import files or connect a data warehouse. For more information, refer to [Overview - Data](/docs/user-guide/data/key-concepts/overview-data) and [Imports](/docs/user-guide/data/imports/overview-imports).

### 2. Unify User Profiles

MoEngage merges the events and attributes it receives into a single profile per user. A visitor who browses anonymously and later signs in keeps one profile. For more information, refer to [User Profile](/docs/user-guide/data/user-data/user-profile) and [Anonymous to Registered User Merge](/docs/user-guide/data/user-data/anonymous-to-registered-user-merge).

### 3. Engage Users

Build segments from profile data, then reach those users with one-off campaigns on a single channel or with flows that move users across channels based on what they do. Send transactional alerts with Inform, and personalize your website for each visitor. For more information, refer to [Basics of Segmentation](/docs/user-guide/segment/getting-started/basics-of-segmentation), [Channels in MoEngage](/docs/user-guide/campaigns-and-channels/getting-started/introduction/moengage-channels), [Overview - Flows](/docs/user-guide/flows-cross-channel-messaging/getting-started/overview-flows/overview-flows), [Overview - Inform](/docs/user-guide/inform/overview-inform), and [Overview - Personalize](/docs/user-guide/personalize/overview/overview-personalize).

### 4. Measure Results

Track how users behave in your app or website and how your campaigns and flows perform, then refine your segments and messages. For more information, refer to [MoEngage Analytics](/docs/user-guide/analyze/moengage-analytics/overview).

### Merlin AI

Merlin AI predicts user behavior, picks the best time and channel for each message, helps you build segments and flows, and generates content. Campaign and offer decisioning choose which campaign or offer each user receives. For more information, refer to [Merlin AI Studio](/docs/user-guide/ai-and-intelligence/merlin-ai/merlin-ai-studio).

### Data Out

You can export events to your data warehouse or cloud storage, sync segments to ad networks and other tools, and connect AI assistants to your workspace through the MoEngage MCP server. For more information, refer to [Overview - Event Exports](/docs/user-guide/data/exports/events/overview-events-exports), [Outbound Segment Sync](/docs/user-guide/data/exports/segments/outbound-segment-sync), and [MoEngage MCP Server and Connector](/docs/user-guide/ai-and-intelligence/merlin-ai/moengage-mcp-server).

## Key Concepts

These terms appear throughout the dashboard and the docs. For the full list, refer to [Terms to Know](/docs/user-guide/getting-started/overview/terms-to-know).

| Term | What it means |
| - | - |
| Workspace | The account your team works in on the MoEngage dashboard. Each workspace has a Test environment and a Live environment. |
| Test and Live environments | The Test environment is for integration and QA, and the Live environment is for production data and campaigns. Each environment has its own Workspace ID and its own settings, available under **Settings** > **Account** > **General settings**. For more information, refer to [Live and Test Environments](/docs/user-guide/getting-started/initial-setup/dashboard-overview#live-and-test-environments). |
| Data center | The region where MoEngage hosts your workspace. It determines your dashboard URL and your SDK and API endpoints. For more information, refer to [Data Centers in MoEngage](/docs/user-guide/data/key-concepts/data-centers-in-moengage). |
| User attribute | A property of a user, such as name, email, or city. |
| Event | An action a user takes, such as viewing a product or making a purchase. Events can carry their own attributes. |
| Segment | A group of users you target or analyze, defined by conditions on their data or uploaded from a file. |
| Campaign | A message you send on one channel, such as a push notification or an email. |
| Flow | A multi-step journey that moves users across channels based on what they do. |

## Set Up Your Workspace

Steps 3 and 5 need a developer, and so does adding push credentials in step 4.

<Steps>
  <Step title="Log in and secure access">
    Log in to the dashboard and set up 2-step verification. If your organization uses an identity provider, configure single sign-on (SSO).

    For more information, refer to [Log In to MoEngage](/docs/user-guide/getting-started/initial-setup/log-in-to-moengage) and [Single Sign-On (SSO)](/docs/user-guide/settings/account/security/single-sign-on-sso).
  </Step>

  <Step title="Invite your team">
    Add team members and assign each one an access role, so they see only the parts of the dashboard they need.

    For more information, refer to [Manage Members](/docs/user-guide/settings/account/team-management/manage-members) and [Access Roles](/docs/user-guide/settings/account/team-management/access-roles).
  </Step>

  <Step title="Integrate your data">
    Your developers add the MoEngage SDK to your app or website and track the events and attributes you plan to use. Use the integration checklist to agree on what to track before they start.

    The SDK decides which environment receives data. On Android and iOS, debug builds send data to the Test environment and signed release builds send data to the Live environment. On the Web SDK, your developers set the environment to `TEST` or `LIVE` in the SDK configuration.

    For more information, refer to the [Integration Checklist](/docs/user-guide/getting-started/integration/integration-checklist), the [SDK Integration Guide](/docs/developer-guide/introduction), and [Imports](/docs/user-guide/data/imports/overview-imports).
  </Step>

  <Step title="Set up your channels">
    Configure each channel you plan to use. For example, connect your email sender, connect an SMS or WhatsApp provider, or add push credentials. Push credentials come from your Firebase project for Android and your Apple Developer account for iOS. Add them in both the Test and Live environments.

    For more information, refer to [Channels in MoEngage](/docs/user-guide/campaigns-and-channels/getting-started/introduction/moengage-channels).
  </Step>

  <Step title="Validate the integration">
    Use a debug build of your app, or a website set to `TEST`, so the data goes to the Test environment. Confirm that events and user attributes reach MoEngage, and that test push notifications and in-app messages reach your device. When validation is done, release a signed build of your app, or set your website to `LIVE`, so production data goes to the Live environment.

    For more information, refer to [User Events Integration Validation](/docs/user-guide/getting-started/integration-validation/user-events-integration-validation), [User Attribute/Profile Integration Validation](/docs/user-guide/getting-started/integration-validation/user-attributeprofile-integration-validation), [Android Push Notifications Integration Validation](/docs/user-guide/getting-started/integration-validation/android-push-notifications-integration-validation), [iOS Push Notifications Integration Validation](/docs/user-guide/getting-started/integration-validation/ios-push-notifications-integration-validation), [Web Push Notifications Integration Validation](/docs/user-guide/getting-started/integration-validation/web-push-notifications-integration-validation), and [In-App Notifications Integration Validation](/docs/user-guide/getting-started/integration-validation/in-app-notifications-integration-validation).
  </Step>

  <Step title="Launch your first campaign">
    Create a segment of the users you want to reach, send them a campaign, and review the results.

    For more information, refer to [Basics of Segmentation](/docs/user-guide/segment/getting-started/basics-of-segmentation), [Create Push Campaigns](/docs/user-guide/campaigns-and-channels/mobile-push/create/create-push-campaigns), and [Campaign Stats](/docs/user-guide/analyze/dashboards/campaign-stats).
  </Step>
</Steps>

## Where to Start for Your Role

| If you are | Start with |
| - | - |
| A marketer or growth team member | [Channels in MoEngage](/docs/user-guide/campaigns-and-channels/getting-started/introduction/moengage-channels), then [Basics of Segmentation](/docs/user-guide/segment/getting-started/basics-of-segmentation) and [Overview - Flows](/docs/user-guide/flows-cross-channel-messaging/getting-started/overview-flows/overview-flows). |
| A developer | The [SDK Integration Guide](/docs/developer-guide/introduction) for your platform. |
| On a data team | The [API Documentation](/docs/api/introduction), [Imports](/docs/user-guide/data/imports/overview-imports), and [Partner Integrations](/docs/partner-guide/introduction). |
| An administrator | [Workspace Settings](/docs/user-guide/settings/account/general-settings/workspace-settings), [Manage Members](/docs/user-guide/settings/account/team-management/manage-members), and [Security](/docs/user-guide/settings/account/security/overview). |

## Get Help

* Ask [AIRA](/docs/user-guide/contact-support/aira-support-bot/aira-overview), the MoEngage support bot, or [raise a support ticket from the dashboard](/docs/user-guide/contact-support/raise-a-support-ticket-through-moengage-dashboard).
* Take self-paced courses in [MoEngage Academy](https://academy.moengage.com/student/catalog).
* Follow new features in the [release notes](/docs/release-notes/product).
* Use these docs from your LLM, IDE, or AI agent. For more information, refer to [Documentation Access to Agents](/docs/documentation-access-to-agents).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.