MoEngage
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by MoEngage, Inc. · www.moengage.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
MoEngage at a glance
- Vendor
- MoEngage, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates MoEngage 2/5, the mean of 6 judges. MoEngage presents itself as an agentic customer engagement platform for consumer brands. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
MoEngage presents itself as an agentic customer engagement platform for consumer brands. Channel coverage is the strength: scores sit at 7, crediting 16+ channels on one platform, one-click ad-audience sync to Google and Meta, and reach via TikTok, LinkedIn and Snapchat. Sovereignty is the weakness at 1-2 — the captured pages name only MoEngage Global Inc. and MoEngage India Pvt. Ltd., state that personal data is transferred to an Indian subsidiary bound by Standard Contractual Clauses, and we found no public information on an EU contracting entity, data residency or hosting location. Lead management sits flat at 3: the documented capability is RFM consumer-lifecycle segmentation and predictive churn, with no public information on lead scoring or sales handover. Journey orchestration spans 4-6 and consent and profiling spans 4-6; the spread reflects differing weight on what is documented — Flows with per-step drop-off analytics, rights handling through APIs — versus what has no public information: frequency capping, arbitration between overlapping journeys, consent timestamps and retention. CRM and data scores 3-4 on a native Salesforce connector whose field mapping and duplicate handling are undocumented.
Speaks for it
- Channel coverage scores at 7, covering 16+ channels on one platform with one-click ad-audience sync to Google and Meta and reach via TikTok, LinkedIn and Snapchat.
- No-code cross-channel journey Flows with per-step drop-off analytics, journey visualization and a natural-language flow builder are documented.
- User data export, deletion on demand, automated data collection requests and DSAR assistance through APIs are documented, plus a per-user SDK flag that stops engagement-data processing for that person.
- A native Salesforce integration built by MoEngage ships with a public setup guide, alongside 250+ marketplace connectors, APIs, SDKs and webhooks.
- Segments can be built directly on your own warehouse data without moving it, with a no-code builder in addition to SQL.
Held against it
- Sovereignty scores 1-2: the named contracting entities are MoEngage Global Inc. and MoEngage India Pvt. Ltd., the privacy policy states personal data is transferred to an Indian subsidiary bound by Standard Contractual Clauses, and no captured page establishes an EU contracting entity, data residency or hosting location.
- Lead management scores flat at 3 — documented RFM lifecycle segmentation and predictive churn, with no public information on lead scoring, routing to sales owners or handover to a sales queue.
- No public information on consent timestamps and sources, per-channel consent status, retention periods or erasure of derived scores, with opt-out processing stated at up to one calendar month and different statements across captured pages on automated decision-making — the privacy policy addresses MoEngage's own processing of customer and employee data while product pages describe AI decisioning deciding what each customer sees.
- No public information on two-way field mapping, duplicate handling, conflict resolution or published API rate limits for the CRM and API integrations.
- The captured pages show a pricing page exists but state no tier prices, contact limits, billing periods or the tier where automation begins, routing buyers to a talk-to-an-expert demo.
Best for
- You run consumer-brand lifecycle marketing — onboarding, retention, reactivation — and want behaviour-triggered cross-channel journeys with per-step drop-off analytics.
- You need many channels and ad platforms in one place, including one-click audience sync to Google and Meta with automatic exclusion of converted customers.
- You want documented data-subject request handling for consumer end users — user data export, deletion on demand and DSAR assistance through APIs.
- Your customer data lives in your warehouse and you want to build segments on it in place, with SQL support.
Avoid if
- Your procurement requires an EU contracting entity, EU data residency or named EU hosting; the captured pages name other entities and we found no public information establishing any of these.
- You need B2B lead scoring, qualification criteria and routing to sales owners; the documented capability is consumer lifecycle segmentation and lead management scores flat at 3.
- You need published tier prices, contact limits or billing periods to model an annual invoice before a sales conversation; pricing transparency scores at 1 and the documented path in is a talk-to-an-expert demo.
The scores
| Criterion | Panel median |
|---|---|
| Journeys & orchestration | 2.5 of 5 |
| Lead scoring, routing & lifecycle | 1.5 of 5 |
| Channels & personalisation | 3.5 of 5 |
| Consent, tracking & profiling | 2.5 of 5 |
| CRM integration & data model | 2 of 5 |
| European sovereignty | 1 of 5 |
Journeys & orchestration
Show reasoningHide reasoning
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Demand Gen Lead
No-code journey Flows run onboarding, retention and reactivation across the lifecycle, triggered by past activity with real-time trigger points and per-step drop-off analytics — real orchestration, not autoresponders. But we found no public information on branching logic, waits, exit conditions, or what happens when one contact qualifies for several journeys at once, which is the conflict handling I need before trusting a programme at scale. 5 7 9 4
The Sales Ops Manager
No-code cross-channel Flows for onboarding, retention and reactivation, automated messages triggered by past activity, drop-off analytics at every journey step, and a natural-language flow builder are all documented. I found no public information on frequency capping or suppression across journeys, priority when a contact qualifies for several at once, versioning of a live journey, or testing against real records — exactly the arbitration that stops journeys colliding with each other. 5 6 7 9 11
The Data Protection Officer
No-code cross-channel Flows triggered by past customer behaviour, with journeys visualised and drop-offs reported at every step, put this at the level of a real multi-step builder. The captured pages show nothing on frequency capping or suppression across journeys, or on what happens when a contact qualifies for several at once. 5 7 9 11
The Lifecycle Marketer
No-code cross-channel journey Flows are documented for onboarding, retention and reactivation, with automated messages triggered by past activity, drop-off visibility at every step of the journey, and an AI decisioning layer said to decide what each customer sees. I found no public information on frequency capping, suppression across journeys, priority when one contact qualifies for several, holdout groups for measurement, or versioning of a live journey, so I cannot treat the orchestration as programme-level. 5 6 7 9 11
The Solution Architect
No-code cross-channel Flows triggered by past customer activity are documented, with per-step drop-off analytics, journey visualization and an AI flow builder — that is well past linear autoresponders. But the captured pages show no branching and waits, no goals or exit conditions, and nothing on frequency capping, priority when a contact qualifies for several journeys, or versioning of a live flow, so I stop short of the full workflow-builder level. 5 7 9 11
The Skeptic
The pages describe no-code cross-channel journey Flows triggered by past customer activity, drop-off reporting at each journey step, and real-time trigger points — a behaviour-triggered flow builder. We found no public information on branching, waits, goals or exit conditions, frequency capping, or what happens when a contact qualifies for several journeys at once, so the documented level stops at the builder rung. 4 5 7 9 11
Lead scoring, routing & lifecycle
Show reasoningHide reasoning
How this is scored
Scoring, qualification and handover to sales — including whether the customer can explain to a lead why the system decided what it decided.
0 — No scoring, lifecycle or lead handling at all; the product is a sending tool for lists.
3 — A rule-based lead score from attributes or engagement, or lifecycle stages set by tags or fields.
5 — Configurable lead scoring on attributes and behaviour, lifecycle or pipeline stages, and qualified leads assigned or notified to sales.
8 — Multiple scoring models per product or region, negative scoring and score decay, account-level scoring alongside contact-level, routing rules to owners or teams with follow-up SLAs, and score history visible per contact.
10 — Scoring is explainable and accountable: the contribution of each signal visible per record, model changes versioned with their effect on the funnel, routing rules auditable, and predictive scoring — where offered — documented well enough for a DPO to assess it as automated decision-making.
The Demand Gen Lead
What is documented is consumer lifecycle work: RFM segments with categories like churn risk and champions, predictive churn, and campaigns across onboarding, retention and monetisation. We found no public information on lead scoring, routing to sales owners, or handover workflows — the machinery that makes a score sales trusts. 5 7 8 10
The Sales Ops Manager
Recency-frequency-monetary segmentation with stages like churn risk, champions and needs attention, plus predictive churn and hibernation algorithms, are documented as rule-based lifecycle categorisation. We found no public information on lead scoring, qualification criteria, or assignment to sales owners with follow-up commitments — which for my pipeline reporting is the whole criterion. 5 7 8
The Data Protection Officer
What is documented is lifecycle segmentation — RFM categories such as churn risk and champions — plus predictive churn algorithms. We found no public information on qualified leads being routed to sales, on score history per contact, or on how the predictive models reach a decision, which is what I would need to assess them as automated decision-making. 5 7 8
The Lifecycle Marketer
This is a consumer-lifecycle platform rather than a sales-lead tool: RFM segmentation, predictive churn and hibernation, and campaigns across onboarding, monetisation and retention are all documented. I found no public information on configurable scoring models, negative scoring or decay, routing to owners, or any handover of qualified leads to sales, so it sits at the rule-based-segmentation end with lifecycle framing around it. 5 7 8 10
The Solution Architect
What the lifecycle pages document is consumer-style segmentation — RFM categories like champions and churn risk, predictive churn algorithms, onboarding and first-transaction campaigns for new or anonymous customers — which is lifecycle categorization from engagement. I found no public information on configurable lead scoring, negative scoring or decay, routing to owners or teams, or handover to a sales queue. 5 7 8 10
The Skeptic
What the captured pages show is consumer lifecycle marketing — RFM segmentation into champions, churn risk and similar categories, predictive churn, and onboarding and monetization campaigns — which is lifecycle-stage marketing rather than lead qualification. We found no public information on scoring models, score history, or any handover and routing to a sales owner. 5 7 8 10
Channels & personalisation
Show reasoningHide reasoning
How this is scored
What the platform can send and personalise — email, SMS, push, on-site content, ad audiences — judged on what shares one profile and one suppression list.
0 — Not a sending platform; the product cannot deliver messages on any channel.
3 — Email with merge-field personalisation, plus sign-up forms or landing pages.
5 — Email plus at least one further channel (SMS, push, or ad-audience sync) driven from the same contact profile, and dynamic content blocks based on contact data.
8 — Email, SMS and push from one profile with shared unsubscribe handling, on-site personalisation, ad-audience sync to the major networks, cross-channel frequency capping, and content personalised on behaviour rather than only on stored fields.
10 — Channel is a delivery detail: one profile and one consent state across every channel, next-best-channel selection, and personalisation that draws on the full behavioural record without the marketer assembling it by hand.
The Demand Gen Lead
Sixteen-plus channels on one platform — email, SMS, push, in-app, WhatsApp, onsite messaging — with behaviour-driven personalisation, website personalisation, and one-click ad sync to Google, Meta, TikTok, LinkedIn and Snapchat including automatic exclusion of converted customers. A "Most Preferred Channel" feature points toward next-best-channel logic. We found no public information on shared unsubscribe handling or cross-channel frequency capping, which keeps this just short of the top band. 1 5 9 10
The Sales Ops Manager
Sixteen-plus channels including email, SMS, web and mobile push, in-app, WhatsApp and on-site messaging are documented on one platform with profiles built from attributes and behaviour, alongside ad-audience sync to Google, Meta, TikTok, LinkedIn and Snapchat and behaviour-triggered advertising. We found no public information on shared unsubscribe or suppression handling across those channels or on cross-channel frequency capping; "Most Preferred Channel" is described as a campaign feature, not a documented shared consent state. 5 9 10
The Data Protection Officer
Sixteen-plus channels on one platform, ad-audience sync to Google, Meta, TikTok, LinkedIn and Snapchat, and personalisation driven by behaviour and browsing patterns are documented. Shared unsubscribe handling across channels and cross-channel frequency capping do not appear in the captured pages. 1 5 9 10
The Lifecycle Marketer
Email, SMS, web and mobile push, in-app, WhatsApp, cards and on-site messaging are all listed on one platform, with one-click ad-audience sync to Google, Meta, TikTok, LinkedIn and Snapchat, lookalikes, converted-customer exclusion, website personalisation, and personalisation driven by behavioural data plus Best Time to Send and Most Preferred Channel features pointing at next-channel choice. Cross-channel frequency capping and shared unsubscribe handling across those channels are where I stop: I found no public information on either, and a programme where every channel obeys one cap is my bar. 1 5 9 10 11
The Solution Architect
Email, SMS, web and mobile push, in-app, onsite messaging, cards and WhatsApp are listed on one platform, alongside one-click ad sync to Google Ads and Meta, reach via TikTok, LinkedIn and Snapchat, ads triggered on behaviour, lookalike audiences and automatic exclusion of converted customers — plus a 'Most Preferred Channel' feature pointing toward channel selection. What the captured pages do not show is shared cross-channel unsubscribe handling and frequency capping, which keeps this just below the top band. 1 5 9 10
The Skeptic
Email, SMS, mobile and web push, in-app, on-site messaging and WhatsApp are listed as channels on one platform, with one-click ad-audience sync to Google and Meta and personalisation driven by behaviour and browsing patterns. We found no public information on shared unsubscribe handling across channels or cross-channel frequency capping, which holds this below the top rungs. 1 5 9 10
Consent, tracking & profiling
Show reasoningHide reasoning
How this is scored
The platform builds behavioural profiles of named people. Consent capture and proof, tracking that can be limited, retention, and whether automated decisions about individuals are documented and contestable.
0 — The vendor states a practice that defeats consent, such as importing purchased lists or tracking named contacts with no opt-in mechanism at all.
3 — Double opt-in available and unsubscribe handled per contact.
5 — Double opt-in with the consent timestamp and source stored per contact, consent or subscription status per channel, and a documented way to answer access and erasure requests.
8 — Consent reproducible as evidence with the wording versioned, tracking switchable per contact or a cookieless or first-party tracking mode, profiling suppressible per person, retention for inactive records stated and executed per data category, and erasure covering derived scores.
10 — Built for the accountability principle: a per-contact history of what was tracked, scored and decided, automated decision-making documented well enough to support an Art. 22 DSGVO assessment, profiling off by default for anyone who has not consented to it, and deletion that removes derived scores as well as raw events.
The Demand Gen Lead
The privacy policy gives a per-user SDK flag under which MoEngage stops processing that person's engagement data — profiling suppressible per individual — plus data subject request handling through APIs with on-demand export and deletion. We found no public information on double opt-in, consent timestamps or sources stored per contact, per-channel subscription states, or whether erasure covers derived scores; opt-out processing is stated to happen within one calendar month. 3 12
The Sales Ops Manager
Export, deletion on demand and automated handling of data subject requests through APIs are documented, and the SDK can flag a user whose engagement data must no longer be processed — per-person suppression I can actually act on. I found no public information on double opt-in, consent wording, timestamps and source stored per contact, per-channel consent status, or retention for inactive records, and the captured pages give different statements on automated decision-making: the privacy policy states none is used for customer and employee data while product pages describe AI decisioning deciding what each customer sees. 3 12
The Data Protection Officer
The rights machinery is real: data subject requests answered through APIs with export and deletion on demand, and an SDK flag that halts engagement-data processing for a named user — though the documented opt-out path allows processing to continue up to one calendar month. No captured page documents consent capture with stored timestamps and versioned wording, per-channel consent status, retention per data category, or erasure that covers derived scores. The vendor's statement that it does not use automated decision-making addresses its own processing of customer and employee data, while the platform's AI decisioning and churn prediction operate on end users, undocumented in the depth an accountability review would require. 3 12
The Lifecycle Marketer
Consent withdrawal at any time, a per-user suppression flag in the SDK that stops processing of that user's engagement data, automated data-subject requests with export and on-demand deletion, DSAR support through APIs, and a stated position that no automated decision-making is used in their processing operations are all documented. I found no public information on consent timestamps and source stored per contact, per-channel consent status, retention periods for inactive records, or whether erasure removes derived scores and model outputs. 3 12
The Solution Architect
A per-user opt-out flag in the SDK — engagement data stops being processed for that person — plus consent withdrawal and a documented route for access and erasure (data export, deletion on demand, automated collection requests, DSAR assistance through APIs) are stated, and optional data masking and encryption exist. But I found no public information on double opt-in, consent timestamp and source stored per contact, per-channel consent state, retention periods per data category, or whether erasure reaches derived scores. 3 12
The Skeptic
The privacy policy documents DSAR assistance via APIs, consent withdrawal, a per-user processing opt-out through an SDK flag, and on-demand export and deletion of user data. But we found no public information on double opt-in, consent timestamps and sources, per-channel subscription status or retention periods, and the policy's stated window for opt-out processing is one calendar month — long for a platform profiling named users. 3 12
CRM integration & data model
Show reasoningHide reasoning
How this is scored
The join that decides the implementation: how the platform and the CRM stay in agreement about who a person is, and what happens when they disagree.
0 — No way to get contact data in or out beyond typing it in.
3 — CSV import and export, and a sync or connector to a named CRM.
5 — Two-way sync with at least one major CRM (or a built-in CRM) with field mapping, duplicate handling, and a documented API.
8 — Configurable conflict resolution per field, account and contact objects both modelled, custom objects supported, near-real-time sync with retry and an error log, and API rate limits documented.
10 — One record, two systems, no ambiguity: identity resolution across anonymous and known states, field-level ownership defined per system, replay of failed syncs, and a data model the customer can extend without vendor services.
The Demand Gen Lead
A native Salesforce integration built by MoEngage ships with a published setup guide, alongside documented APIs, SDKs, webhooks and a marketplace of 250+ connectors — so the join exists. We found no public information on sync direction, field mapping, duplicate handling or conflict resolution, which is exactly what decides whether marketing and sales agree on who a person is. 14 1 9
The Sales Ops Manager
A native Salesforce integration with a public setup guide, plus APIs, SDKs, webhooks and 250+ marketplace connectors, are documented, with real-time data sync stated for the Shopify integration. We found no public information on sync direction for the CRM, field mapping, duplicate handling, configurable per-field conflict resolution, or a sync error log with retry — the specifics that decide how many duplicate contacts I inherit and whether the pipeline report can be trusted before it is wrong. 1 9 11 14
The Data Protection Officer
A native Salesforce integration built by the vendor with a public setup guide, 250+ marketplace connectors, APIs and webhooks, a native Shopify integration with real-time data sync, and segments built directly on warehouse data without moving it are documented. We found no public information on two-way field-level sync, duplicate handling, or what happens when the two systems disagree about who a person is. 1 9 11 14
The Lifecycle Marketer
A native Salesforce integration with a setup guide, 250+ marketplace connectors, APIs, SDKs and webhooks, real-time updates on customer profiles, and warehouse-native segments that query the customer's own warehouse data without moving it are documented. What decides the implementation — two-way sync behaviour, field mapping, duplicate handling, conflict resolution, account-level objects and API rate limits — has no public information I could find, so the join cannot be assessed beyond the connector existing. 1 9 11 14
The Solution Architect
A native, MoEngage-built Salesforce connector with a setup guide, 250+ marketplace connectors, APIs, SDKs and webhooks, real-time profile updates and warehouse-backed segments in SQL give a credible integration story. The hard parts of the join are undocumented: no field mapping, no duplicate or conflict handling, no custom objects, and no published API rate limits — the failure points I always hit. The path from anonymous visitor to known contact appears only as marketing copy about welcoming new or anonymous customers, not as a documented identity-resolution flow. 1 8 9 11 14
The Skeptic
A native Salesforce CRM integration built by the vendor with a setup guide, plus APIs, SDKs, webhooks, 250+ marketplace connectors, and a native Shopify integration with real-time data sync. We found no public information on two-way field mapping, duplicate handling, conflict resolution or sync error handling, so the documented level is a named-CRM connector with open APIs, one step above a bare connector. 1 9 11 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where behavioural profiles of named EU residents are processed, who the contracting entity is, and which subprocessors see them. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which given the profiling is heavily. Dimensions the sources do not establish are unknown, not non-EU.
0 — Proven non-EU: a non-EU vendor and contracting entity with hosting and tracking stated outside the EU.
3 — One European element proven — an EU contracting entity or EU data residency stated — with the rest of the chain undocumented.
5 — An EU contracting entity and EU hosting both stated, and a data processing agreement offered.
8 — EU hosting on named infrastructure, EU contracting entity, a subprocessor list published with locations, and any non-EU processing (tracking, AI scoring, support access) named with its legal basis.
10 — Sovereign end to end and evidenced: every profile, event and derived score processed in the EU by European subprocessors, certification published, and no transfer requiring a Schrems II argument to survive.
The Demand Gen Lead
For a platform profiling named EU consumers, we found no public information establishing an EU contracting entity or EU data residency: the named entities are MoEngage Global Inc. and MoEngage India Pvt. Ltd., the privacy policy states PII is transferred to the Indian subsidiary under Standard Contractual Clauses, and the published sub-processor list is noted to differ from customer to customer. Berlin and London offices appear on the site, but an office is neither a contracting entity nor a data centre, and I weight this heavily where behavioural profiles are concerned. 2 3 9
The Sales Ops Manager
The contracting entities named are MoEngage Global Inc. and MoEngage India Pvt. Ltd., and the privacy policy states personal data is transferred to an Indian subsidiary under Standard Contractual Clauses; a data processing addendum and a subprocessor list are published, though the captured pages show the addendum only as link titles and note the subprocessor list may differ customer to customer. We found no public information on the contracting entity's jurisdiction, EU data residency or EU hosting — with behavioural profiles of named people in scope, that chain is unproven end to end. 2 3
The Data Protection Officer
The only named contracting entities are MoEngage Global Inc. and MoEngage India Pvt. Ltd., the privacy policy states that personal data is transferred to an Indian subsidiary under Standard Contractual Clauses, and a subprocessor list is published but said to differ from customer to customer. No captured page establishes an EU contracting entity or EU hosting, so for a platform profiling named people nothing in the documented chain is anchored in Europe. 2 3 9
The Lifecycle Marketer
The contracting entities named on the legal pages are MoEngage Global Inc. and MoEngage India Pvt. Ltd., with jurisdiction, hosting and data residency not established on any captured page, and the privacy policy documents SCC-bound transfers of personal data to an Indian subsidiary. A subprocessor list is published and noted to vary from customer to customer, and SCC-based DPAs exist, but I found no public information proving an EU contracting entity or EU residency — which, for a platform profiling named people, is where my line sits. 2 3 9
The Solution Architect
The legal pages publish a data processing addendum, Standard Contractual Clauses and a sub-processor list, and state that personal data is transferred to an Indian subsidiary under SCCs — so one non-EU leg of the chain is named with its legal basis. No EU contracting entity and no EU data residency are stated anywhere in what I read, and where behavioural profiles are hosted is not established; for a platform profiling 1.3 billion consumers a month, that gap decides it for me. 2 3 9
The Skeptic
The entities named are MoEngage Global Inc. and MoEngage India Pvt. Ltd., the privacy policy states PII is transferred to the Indian subsidiary under SCCs, and the subprocessor list is published but may differ from customer to customer. We found no public information on where profiles and events are hosted or on any EU residency, and for a platform processing a trillion data points a month on named people, that undocumented chain weighs heavily. 2 3 9
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their contact base and send volume — including the tier where automation actually begins, overage, and mandatory onboarding — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or a single tier with its contact limit.
5 — Prices per tier public with the billing period and contact limits stated, and which tier includes automation visible.
8 — Every tier priced publicly with contact and volume limits, feature boundaries, overage rates, onboarding costs, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given contact count, send volume and feature set, including overage, additional users and any implementation fee stated outright.
The Demand Gen Lead
The only pricing fact captured is that a pricing page exists on the site; no tier figures, contact limits, billing periods, or the tier where automation begins appear in the captured pages, and the offered path is to talk to an expert. I cannot compute an annual invoice from this, and neither can procurement. 1 9
The Sales Ops Manager
The homepage carries a pricing link, but the captured pages contain no price figures, tiers, contact or send-volume limits, or onboarding costs, and the documented path in is a demo request. We found no public information from which a buyer could compute an annual invoice, including the tier where automation begins. 1
The Data Protection Officer
The captured pages show only that a Pricing page exists. No tier prices, contact limits, billing periods, overage rates or onboarding costs appear anywhere in the captured evidence, so an annual invoice is not computable from what was read. 1
The Lifecycle Marketer
The captured pages show a pricing page exists, but no price, tier, contact limit, send volume, overage rate or onboarding fee is stated anywhere I read, and the featured path is a talk-to-an-expert demo. A buyer cannot begin to compute an annual invoice, or even see which tier automation starts in, from what is public here. 1 9
The Solution Architect
The captured homepage lists a Pricing page, but no tier prices, contact limits, billing periods, or the tier where automation begins appear anywhere in what I read, and the pages route buyers to talk to an expert. I cannot compute an annual invoice from these captures, and with profiling at this scale I want to. 1 9
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The excerpt shows the DPA only as link titles on the legal index page; the agreement text itself is not included. |
1/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about MoEngage
Is MoEngage European?
Not determined: the vendor’s pages as captured do not say where MoEngage is based.
Where does MoEngage store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does MoEngage have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to MoEngage?
As of 18 Nov 2026, the panel rates Braze (3/5), HubSpot Marketing Hub (3/5) and ActiveCampaign (Automation) (3/5) highest among the other 20 Marketing Automation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Brevo (Automation) (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: MoEngage alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The excerpt shows the DPA only as link titles on the legal index page; the agreement text itself is not included.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 90 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.moengage.com Checked 17 Nov 2026 Details →
- 2 Legal notice — found from the homepage www.moengage.com Checked 17 Nov 2026 Details →
- 3 Privacy policy — found from the homepage www.moengage.com Checked 17 Nov 2026 Details →
- 4 Security / trust page — found from the homepage www.moengage.com Checked 17 Nov 2026 Details →
- 5 Journeys & orchestration — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 6 Journeys & orchestration — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 7 Lead scoring, routing & lifecycle — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 8 Lead scoring, routing & lifecycle — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 9 Channels & personalisation — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 10 Channels & personalisation — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 11 Consent, tracking & profiling — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 12 Consent, tracking & profiling — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 13 CRM integration & data model — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →
- 14 CRM integration & data model — found from sitemap www.moengage.com Checked 17 Nov 2026 Details →