> For the complete documentation index, see [llms.txt](https://docs.digia.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digia.tech/digia-engage/start-here/readme.md).

# Overview

Digia Engage helps product and marketing teams create app-native experiences without waiting for an app release for every campaign. You design the experience in the [Digia Engage Dashboard](https://engage.digia.tech), then launch it through the Customer Engagement Platform (CEP) your team already uses, such as CleverTap, MoEngage, or WebEngage.

Your CEP continues to decide the audience and timing. Digia Engage decides what the user sees inside the app.

***

## Why Digia Engage

Shipping an in-app experience, even a simple banner or tooltip, often depends on an app release. That slows down promotions, onboarding changes, feedback collection, and feature announcements.

Digia removes that bottleneck. After a one-time app setup, campaign creators can design, update, test, and launch in-app experiences from the dashboard. The CEP still handles segmentation, journeys, and campaign rules, so your existing growth workflows stay in place.

***

## How It Works

Digia complements your CEP; it does not replace it. The responsibilities split cleanly:

| Question               | Owner    | How                                               |
| ---------------------- | -------- | ------------------------------------------------- |
| **Who** sees it?       | Your CEP | Audience segmentation, user properties            |
| **When** does it show? | Your CEP | Event triggers, journey rules                     |
| **What** is shown?     | Digia    | A layout you design in the Digia Engage Dashboard |

At a high level:

1. Create the in-app experience in Digia Engage.
2. Create the matching campaign in your CEP.
3. Use your CEP to choose the audience and trigger.
4. When a user qualifies, the app shows the Digia experience.

**Example:** a user taps **Checkout** and sees a "Get 20% off" bottom sheet.

<figure><img src="/files/GwrAzDkJOu9wZ10s3PQH" alt="Campaign platform decides audience and trigger while Digia Engage renders the native in-app experience"><figcaption><p>Your campaign platform decides who and when; Digia Engage renders what the user sees.</p></figcaption></figure>

***

## Experience Types

Digia Engage supports four experience types.

### Nudge

An overlay shown above the app screen, such as a bottom sheet or dialog. Use Nudges for promotions, announcements, upgrade prompts, and quick calls to action.

### Guide

A tooltip or spotlight that points to something in the app. Use Guides for onboarding tours, feature discovery, and step-by-step education.

Guides work best when your app team has already shared the list of places a guide can point to.

### Survey

A feedback flow shown inside the app. Use Surveys for NPS, satisfaction checks, product feedback, cancellation reasons, and other structured questions.

### Inline

Content placed directly inside the app screen, such as banners, cards, and carousels inside a feed or home page. Use Inline when the message should feel like part of the screen instead of an overlay.

***

## Get Started

If you are new to Digia Engage, start with [Core Concepts](/digia-engage/start-here/core-concepts.md). It explains the vocabulary used across the docs in plain language.

If your app still needs to be connected to Digia Engage, share the [Developer Guides](/digia-engage/developer-guides/developer-integrations.md) with your app team.

Once setup is complete, use the [User Guides](/digia-engage/user-guides/guides.md) to build and test Nudges, Guides, Surveys, and Inline campaigns from the dashboard.

If you are building a Survey, read [Understanding and Building Surveys](/digia-engage/experience-guides/surveys/understanding-surveys.md) before choosing a campaign-platform-specific Survey guide.