Android — MoEngage Integration

Integrate MoEngage self-handled in-app campaigns into your Digia-powered Android app using the digia-moengage Android library.

The digia-moengage Android library bridges MoEngage self-handled in-app campaigns into Digia's Jetpack Compose rendering engine. When MoEngage triggers a campaign, this plugin intercepts the payload and renders the experience using a layout you designed in Digia Studio.

Artifact: com.github.Digia-Technology-Private-Limited:digia_moengage Version: android.1.0.0-beta.2 Platform: Android Min SDK: 21

---

How It Works

MoEngage Campaign Trigger
        │
        ▼
[MoEngage Android SDK]
        │  SelfHandledAvailableListener
        ▼
[digia-moengage]
        │  maps payload → InAppPayload
        ▼
[digia_engage runtime]
        │  SHOW_BOTTOM_SHEET / SHOW_DIALOG  → DigiaHost renders overlay
        │  SHOW_INLINE                      → DigiaSlot renders inline
        ▼
Campaign UI (native Compose widgets from Digia Studio)

---

Prerequisites

1. MoEngage account with your project configured. See MoEngage Docs.

2. Digia Studio account with campaign pages designed.

3. digia_engage Android SDK already set up. See Digia Engage — Android.

4. MoEngage Android SDK integrated. See MoEngage Android Integration.

---

Installation

1. Add JitPack repository

In your root settings.gradle.kts (if not already added for digia_engage):

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://jitpack.io") }
    }
}

2. Add dependencies

// build.gradle.kts (app module)
dependencies {
    implementation("com.github.Digia-Technology-Private-Limited:digia_engage:android.1.0.0-beta.2")
    implementation("com.github.Digia-Technology-Private-Limited:digia_moengage:android.1.0.0-beta.2")
    // MoEngage Android SDK — use your current version
    implementation("com.moengage:moe-android-sdk:<moengage-version>")
}

---

Integration

1. Initialize MoEngage, Digia, and Register the Plugin

Do this in your Application.onCreate(), in order:

import com.digia.engage.Digia
import com.digia.engage.DigiaConfig
import com.digia.moengage.MoEngagePlugin
import com.moengage.core.MoEngage
import com.moengage.core.config.FcmConfig
import com.moengage.core.config.NotificationConfig

class MyApplication : Application() {
    override fun onCreate() {
        super.onCreate()

        // 1. Initialize MoEngage
        val moEngage = MoEngage.Builder(this, "YOUR_MOENGAGE_APP_ID")
            .configureNotificationWithMoEngageOptions(
                NotificationConfig.Builder()
                    .withSmallIcon(R.drawable.ic_notification)
                    .build()
            )
            .build()
        MoEngage.initialise(moEngage)

        // 2. Initialize Digia
        Digia.initialize(
            context = applicationContext,
            config = DigiaConfig(apiKey = "YOUR_DIGIA_API_KEY"),
        )

        // 3. Register MoEngagePlugin with Digia
        Digia.register(MoEngagePlugin(applicationContext))
    }
}

2. Set Up DigiaHost

Wrap your root composable with DigiaHost so overlay campaigns (bottom sheets, dialogs) can be rendered above all content:

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            MyAppTheme {
                DigiaHost {
                    AppNavHost()
                }
            }
        }
    }
}

3. Add DigiaSlot for Inline Campaigns

Place DigiaSlot composables at positions in your screens where inline campaign content should appear. The placementKey must match the placement ID set in the Digia dashboard.

@Composable
fun HomeScreen() {
    Column {
        DigiaSlot(placementKey = "home_hero_banner")

        DigiaSlot(
            placementKey = "product_offers",
            modifier = Modifier
                .fillMaxWidth()
                .height(180.dp),
        )
    }
}

4. Screen Tracking

Forward screen changes to Digia so MoEngage can evaluate screen-based campaign trigger rules:

navController.addOnDestinationChangedListener { _, destination, _ ->
    Digia.setCurrentScreen(destination.route ?: return@addOnDestinationChangedListener)
}

---

Creating Campaigns in MoEngage

In your MoEngage dashboard, create an in-app campaign and set the template type to Self Handled. In the campaign payload JSON, specify what Digia should render.

Nudges (Bottom Sheet or Dialog)

{
  "type": "SHOW_BOTTOM_SHEET",
  "viewId": "promo_offer_sheet"
}

{
  "type": "SHOW_DIALOG",
  "viewId": "welcome_back_dialog"
}

Inline Content (Cards & Banners)

{
  "type": "SHOW_INLINE",
  "placementId": "product_offers",
  "viewId": "product_offers-3YVNuN"
}

Field	Required	Description
type	Yes	SHOW_BOTTOM_SHEET, SHOW_DIALOG, or SHOW_INLINE.
viewId	Yes	Slug of the Digia Studio page. See Finding Slugs.
placementId	Inline only	Must match the DigiaSlot placementKey in your composable.

---

MoEngagePlugin Lifecycle

MoEngagePlugin implements DigiaCEPPlugin. Digia manages the full lifecycle automatically after Digia.register(...).

Method	Called By	Description
setup(delegate)	Digia.register(...)	Registers SelfHandledAvailableListener with MoEngage.
forwardScreen(name)	Digia.setCurrentScreen	Calls setInAppContext on MoEngage and fetches campaigns for the new screen.
notifyEvent(event, payload)	DigiaHost / DigiaSlot	Dispatches impression, dismiss, and click events back to MoEngage.
teardown()	Digia.register(newPlugin)	Removes the listener and clears cached campaigns.
healthCheck()	Diagnostics	Returns whether the plugin is healthy (delegate is set).

---

Troubleshooting

Campaign not rendering

• Verify Digia.initialize(...) is called before Digia.register(...).

• Ensure the MoEngage campaign template is set to Self Handled.

• Confirm viewId in the payload matches the page slug exactly (case-sensitive).

• For inline campaigns, verify placementId matches the DigiaSlot placementKey.

• Check that DigiaHost wraps the root composable for overlay campaigns.

Build errors

• Ensure JitPack is added to your settings.gradle.kts repositories.

• Confirm all dependency versions are compatible with your min SDK (21).

---

Dependency Reference

Artifact	Version	Role
com.github.Digia-Technology-Private-Limited:digia_engage	android.1.0.0-beta.2	Digia CEP rendering engine
com.github.Digia-Technology-Private-Limited:digia_moengage	android.1.0.0-beta.2	MoEngage CEP plugin for Digia
com.moengage:moe-android-sdk	your version	MoEngage Android SDK

---

Next Steps

• Digia Engage — Android — Core Android SDK reference.

• Finding Slugs — Copy page slugs from Digia Studio to use as viewId in campaign payloads.