> 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/developer-guides/integrations.md).

# Integrations

Connect Digia Engage to the platform that launches your campaigns — CleverTap, MoEngage, WebEngage, or Digia itself.

Your CEP decides **who** sees a campaign and **when**. Digia renders it.

Pick the guide for the CEP your app uses — you only need one.

| Campaigns are launched from | Use this guide                                                                    |
| --------------------------- | --------------------------------------------------------------------------------- |
| CleverTap                   | [CleverTap Integration](/digia-engage/developer-guides/integrations/clevertap.md) |
| MoEngage                    | [MoEngage Integration](/digia-engage/developer-guides/integrations/moengage.md)   |
| WebEngage                   | [WebEngage Integration](/digia-engage/developer-guides/integrations/webengage.md) |
| No CEP yet — Digia itself   | [Digia as Your CEP](/digia-engage/developer-guides/integrations/digia-cep.md)     |

Each guide covers installing the packages, the setup code each platform needs, and what to put in the CEP campaign so it points at a Digia campaign.

New here? Start with the [Overview](/digia-engage/developer-guides/developer-integrations.md). It explains the three keys every integration uses: `digia_campaign_key`, `anchorKey`, and `placementKey`.

{% hint style="info" %}
Anything that works the same on every CEP lives in [References](/digia-engage/developer-guides/reference.md) — including [Resolving Dependency Conflicts](/digia-engage/developer-guides/reference/dependency-conflicts.md) if install fails, and [SDK Debug Settings](/digia-engage/developer-guides/reference/debug-settings-deeplink.md) for checking what the SDK is doing on a device.
{% endhint %}