# MoEngage > MoEngage is a hosted customer engagement platform that stores user profiles and events, builds segments and sends campaigns and flows by push, email, SMS and WhatsApp. Agents reach it through REST APIs and a hosted MCP server. - Canonical: https://www.anchorterminal.com/tools/moengage - Markdown: https://www.anchorterminal.com/tools/moengage.md (~8,400 tokens) - Slim: https://www.anchorterminal.com/tools/moengage.min.md (~2,180 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/moengage.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade B · 65.2/100 · rank #327 of 950 · #3 in Lifecycle marketing & customer engagement · not agent-ready · confidence medium** ## Assessment MoEngage publishes 36 OpenAPI files covering 140 operations, a per-endpoint rate limit table, Markdown docs and a hosted MCP server that builds drafts and leaves publishing to a person. No price, trial or self-serve signup is published, and on 17 August 2026 the Inform API in one data centre accepted requests for about 16 hours without sending the messages. ## Facts | Field | Value | | --- | --- | | Vendor | MoEngage, Inc. (https://www.moengage.com) | | Kind | HTTP API | | Category | Lifecycle marketing & customer engagement (https://www.anchorterminal.com/categories/lifecycle-marketing) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://mcp.moengage.com` | | Auth | OAuth or key · Access needs a MoEngage customer workspace, which is sold through sales. A dashboard user creates API keys under Settings, Account, APIs. The default is HTTP Basic with the Workspace ID as username and the API key as password, with separate keys for Data, Push, Inform, Campaigns and Personalise. An API key dashboard, in early access and enabled on request, adds named keys scoped to chosen API groups, OAuth 2.0 client credentials (access tokens of 5 to 60 minutes, refresh tokens of 30 days, issued at `https://oauth2-{dc}.moengage.com`) and AWS STS role ARNs. Segmentation and Inform accept Basic only. The MCP server uses OAuth with the user's own MoEngage login and role, a second factor, and a 30-day session with a 7-day idle timeout. No app review or partner approval was found. | | Pricing | Paid (Paid) · No public prices. https://www.moengage.com/plans-and-pricing/ lists Growth and Enterprise plans, counted in monthly tracked users, with a sales contact and a one-year minimum commitment. No free tier, trial or self-serve signup was found. Each workspace has Live and Test environments and Inform has a sandbox host, but both sit inside a customer account, so an agent can't start without a contract. API and MCP calls aren't priced per call in any page read (checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the API documentation, the OpenAPI files, the pricing page or the legal pages (checked 2026-10-09). | | Licence | Proprietary service under MoEngage's Terms of Use and a customer agreement | | Tools exposed | 52 | | Docs | https://www.moengage.com/docs/api/introduction | | llms.txt | https://www.moengage.com/docs/llms.txt | | Last release | 2026-10-09 | | API | REST over JSON at `https://api-{dc}.moengage.com`, described in 36 OpenAPI 3 files with 140 operations on 119 paths (79 POST, 31 GET, 16 PUT, 12 PATCH, 2 DELETE). Push uses `pushapi-{dc}`, OAuth `oauth2-{dc}` and Message Archival `archival-{dc}` | | Data centres | DC-01 and DC-04 (United States), DC-02 (EU, Frankfurt), DC-03 (India), DC-05 (Singapore, closed to new signups), DC-06 (Indonesia) and DC-101. Data can't be moved between them | | Resource groups | Users, events, devices and bulk import, file imports, GDPR and CCPA requests, business events, templates for email, push, SMS, in-app and on-site messages, content blocks, catalogues, coupons, recommendations, campaigns, flows, segments, subscriptions, analytics queries, cards, Inform alerts and live activities | | Credentials | HTTP Basic with Workspace ID and API key by default. With the API key dashboard (early access), named keys scoped to API groups, OAuth 2.0 client credentials or AWS STS role ARNs. Regenerating a key invalidates the old one | | Rate limits | Per workspace. Track User 10,000 updates a minute, Track Event 30,000 events a minute, bulk import 60,000 users and 60,000 events a minute, filter segment creation 50 a minute and 1,000 a day, V5 campaign draft creation 5 a minute and 100 a day, file segment operations 10 an hour | | Payload limits | 128 KB a request on the Data APIs, 5 MB on catalogue calls, 150 MB a file for file segments | | Errors | Standard body with `status`, `error.message`, `error.type` and `error.request_id`. V5 APIs return `response_id` and `error.code`, `message`, `target` and `details`. Authentication failures add a `MOENGAGE-AUTH-ERROR-CODE` header such as ER008 for an expired token | | Idempotency | `Idempotency-Key` header on V5 campaign writes and test sends and on flow status changes. Inform treats a repeated `transaction_id` within 5 minutes as a duplicate. None on the Data or segment APIs | | Campaign control | The V5 campaigns API creates, updates, validates and tests Push and Email drafts and pauses, resumes or stops live campaigns. Publishing goes through the V1 `PATCH /core-services/v1/campaigns/{campaign_id}` call or the dashboard | | MCP server | Hosted at https://mcp.moengage.com, OAuth through moeauth.moengage.com. 52 tools in the docs tables. Builds and validates drafts, creates filter segments, reads flows and dashboards, runs five analysis types, and can pause, resume, stop, retire or archive a flow. PII attributes aren't exposed | | SDKs | Android, iOS, Web, React Native, Expo, Flutter, Cordova, Capacitor and Unity client SDKs, each with a dated changelog. No server-side API client library was found | | Status | status.moengage.com on Statuspage, with about 25 components for each data centre and an RSS and Atom history feed | | SLA | 99.9 per cent monthly availability, scheduled downtime 05:00 to 06:00 GMT on Saturdays, backups every 12 hours kept for 3 months | | Certifications | SOC 2 Type 2, ISO 27001:2022, ISO 27701:2019, ISO 22301:2019, CSA STAR Level 1 and HIPAA per the security page. No bug bounty | | Sub-processors | List last modified 1 September 2026 with locations. Amazon Web Services for hosting in each data centre, Google Cloud for PII stores in Qatar and Saudi Arabia, SendGrid for email, and Azure, Google and AWS Bedrock models for the AI functions | | Capabilities | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates, notify.push | | Tags | official, hosted, mcp, oauth, api-key, openapi, llms-txt, closed-source, sales-led, enterprise, eu-region, status-page, soc2, sla | | JSON | https://www.anchorterminal.com/api/v1/tools/moengage.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 74 | 14.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 87 | 14.1 | | Agent ergonomics | 13% | 16.2 | 68 | 11.1 | | Security & auth | 14% | 17.5 | 69 | 12.1 | | Payments & pricing | 10% | 12.5 | 0 | 0.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 75 | 6.6 | | Transparency & trust (editorial 60, provenance 89) | 7% | 8.8 | 75 | 6.6 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **65.2 → B** | ### Why each score - Reliability 74: Graded on the REST API, with the hosted lines. Statuspage site at status.moengage.com with components for each data centre, among them Data APIs, Push APIs, Custom Segment API and Inform (20). Four incidents between 11 July and 9 October 2026. On 17 August the Inform API in DC-03 returned HTTP 200 for about 16 hours while a subset of messages was never sent, and MoEngage could not replay them. On 27 July DC-01 ran degraded across several services for about four and a half hours after a cloud provider fault, on 25 July Inform and triggered campaigns in DC-01 were degraded for about three hours, and on 24 September the campaign list page showed errors for about 45 minutes. One major incident and two long degradations (8). Numeric limits are published for every endpoint group (15). 429 responses carry `x-ratelimit` headers, the OAuth and some V5 endpoints add `Retry-After`, and V5 campaigns and flow status changes take an `Idempotency-Key`. The Data APIs have no idempotency key (12). The published SLA commits to 99.9 per cent monthly availability with service credits (10). The REST API is generally available, with the Flows endpoints and the API key dashboard in early access (9). Total 74. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 87: 36 OpenAPI 3 files are linked from the docs index, with 140 operations on 119 paths and 535 schemas (25). The docs publish llms.txt, llms-full.txt, a Markdown twin of every page, a skill.md file and a docs MCP server (10). All 140 operations have a summary and a description, and the MCP page states what each tool can't do, but few descriptions say when not to use an endpoint (16). The files carry 503 enums and required lists, while 121 of 1,132 object schemas have no declared properties (12). There are 1,725 example entries, 400 or 401 on every operation and 429 on 103 (14). Versions are mixed (v1, v2, v2.1, v5 and a dated 2025-11-20 campaigns file). Monthly product release notes list new APIs and SDK changelogs are dated, but no API changelog was found (10). Total 87. - Agent ergonomics 68: List and search calls take `page`, `limit` or a cursor, and the MCP server hides tools the user's role can't use, though it documents 52 tools (15). V5 list calls return `next_cursor`, and campaign, segment, flow and template search calls take filters (17). Errors use a standard envelope with `message`, `type` and `request_id`, V5 adds `code`, `target` and `details`, and authentication failures carry a `MOENGAGE-AUTH-ERROR-CODE` header. Segment creation returns a 400 that names no field (16). `Idempotency-Key` is required on V5 campaign writes and accepted on flow status changes, and Inform deduplicates on `transaction_id` for 5 minutes. The Data and segment APIs have none, and MCP tool annotations couldn't be read without signing in (12). A campaign draft needs three fields. SDKs cover Android, iOS, web and six cross-platform frameworks, but no server-side API client was found (8). Total 68. - Security & auth 69: Keys can be scoped to chosen API groups and individual APIs, regenerated and archived, and can use OAuth 2.0 client credentials with tokens of 5 to 60 minutes or AWS STS role ARNs. This dashboard is in early access, and Segmentation and Inform accept Basic authentication only (26). One endpoint, `GET /installInfo`, takes an attribution key in the query string, so 3 of the 10 points for that line come off (23). Keys limited to selected APIs, an API firewall that restricts categories by IP address, an MCP server bound to the user's role that builds drafts and can't publish, and a campaign approval workflow sold as an add-on. The legacy campaigns API can still publish (16). The MCP server masks PII attributes, email and mobile number, and the AI policy describes schema validation and allowlisted tool calls for MoEngage's own agents. No guidance for outside agents reading customer content was found (7). Audit logs are listed as a plan item on the pricing page. Whether they record API calls wasn't established (7). Responsible disclosure policy with safe harbour, a 24-hour acknowledgement and a PGP key, no bug bounty, no security.txt, and SOC 2 Type 2, ISO 27001, ISO 27701, ISO 22301, CSA STAR Level 1 and HIPAA on the security page (16). Total 69. - Payments & pricing 0: No x402, MPP or L402 (0). No prices are published. The pricing page lists Growth and Enterprise plans with a sales contact (0). No free tier or trial was found (0). A person has to buy through sales and create keys in the dashboard (0). Total 0. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 75: The Android SDK changelog has an entry dated 9 October 2026 and the Web SDK one dated 8 October (30). The Web SDK alone has seven dated releases since 11 July, and product release notes are published monthly, September 2026 among them (20). Public release notes with an RSS feed, support through a ticket portal and a docs feedback tool. No public issue tracker or community forum was read (10). Client SDKs are current. The MCP server isn't in the official MCP registry, and no API client library was found (10). The SDK repositories and their CI weren't read (5). Total 75. - Transparency & trust 75: Closed service. The published Terms of Use are short and undated, and the Master Service Agreement that the acceptable use policy refers to isn't public (13). A public DPA, a privacy policy dated 26 August 2026 that covers MoEngage as processor, an SLA that states backups every 12 hours kept for 3 months, and an AI policy that commits to no training of third-party models on customer data. Retention periods sit in a help centre article that wasn't read (22). No API deprecation policy was found. The docs say legacy API keys will be deprecated, with no date, and that the early access Flows endpoints won't receive breaking changes (5). The sub-processor list, last modified 1 September 2026, gives each processor's service and location, and the docs name the region of each data centre (20). Total 60. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (18 items): https://www.anchorterminal.com/fixes/moengage.md (JSON https://www.anchorterminal.com/fixes/moengage.json) ### What we couldn't check - unchecked: https://www.moengage.com/security/ answered 403 and wasn't retried, and trust.moengage.com wasn't read, so certifications are taken from the scale and security page - unchecked: the MCP tool definitions, their input schemas and any readOnlyHint or destructiveHint annotations, which need a signed-in session. The tool count of 52 is from the docs tables - unchecked: audit log coverage of API and MCP calls. Audit logs appear on the pricing page as a plan item and no docs page for them was read - unchecked: the data archival policy on help.moengage.com that the SLA cites for retention periods - unchecked: MoEngage's GitHub repositories, so stars, CI and issue handling for the SDKs are not recorded - The Master Service Agreement isn't published, so provenance.terms points at the Terms of Use, which say they govern the website and related software and services - Monthly product release notes carry no day, so lastRelease is the Android SDK changelog entry of 9 October 2026 - The lead gave https://moengage.com/docs/developer-guide/ as the docs link. That is the SDK guide. The API reference is at /docs/api/introduction, and the lead didn't mention the hosted MCP server - Scores follow the generally available REST API, with the hosted MCP server counted where the checklist asks about tools ### Sources - docs index (llms.txt) with the OpenAPI file list: (seen 2026-10-09) - API introduction (hosts, authentication, errors): (seen 2026-10-09) - rate limits: (seen 2026-10-09) - OAuth 2.0 overview: (seen 2026-10-09) - API key dashboard: (seen 2026-10-09) - API firewall: (seen 2026-10-09) - OpenAPI file, Data APIs (one of 36 read): (seen 2026-10-09) - OpenAPI file, V5 campaigns: (seen 2026-10-09) - MCP server and connector: (seen 2026-10-09) - MCP OAuth resource metadata: (seen 2026-10-09) - documentation access for agents: (seen 2026-10-09) - product release notes, September 2026: (seen 2026-10-09) - Android SDK changelog: (seen 2026-10-09) - Web SDK changelog: (seen 2026-10-09) - status page: (seen 2026-10-09) - status history feed: (seen 2026-10-09) - pricing page: (seen 2026-10-09) - Terms of Use: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - Service Level Agreement (PDF): (seen 2026-10-09) - DPA, MoEngage Global Inc. (PDF): (seen 2026-10-09) - sub-processor list: (seen 2026-10-09) - AI terms of usage policy: (seen 2026-10-09) - acceptable usage policy: (seen 2026-10-09) - responsible disclosure policy: (seen 2026-10-09) - security page: (seen 2026-10-09) - official MCP registry search: (seen 2026-10-09) - RDAP record: (seen 2026-10-09) ## Who's behind it (provenance 89/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | MoEngage, Inc. | 20/20 | | Domain age | moengage.com, registered 2014-04-19 (12 years) | 15/15 | | Endpoint on the vendor's domain | mcp.moengage.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects | 9.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.moengage.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The Terms of Use name MoEngage, Inc., a Delaware corporation, and say they govern the website and related software and services. They carry no date. The DPA and sub-processor list name MoEngage Global Inc. The acceptable use policy (last updated 14 May 2026) refers to a Master Service Agreement between MoEngage and its customers. That agreement isn't published. The privacy policy was last updated on 26 August 2026 and covers MoEngage as processor for its customers' end users. The API answers at api-{dc}.moengage.com and the MCP server at mcp.moengage.com, both on the vendor's domain. https://www.moengage.com/.well-known/security.txt returns 404. Reports go to the address in the responsible disclosure policy. Release notes are one page a month under /docs/release-notes/product/, with separate dated changelogs for each SDK. RDAP for moengage.com gives a registration date of 2014-04-19. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.moengage.com/terms-of-use/), read 2026-10-09, gives no date, states 6 of the 7 things a reader expects. - To know. Says access can be ended without notice or for any reason. "4.1 MoEngage may, in its sole discretion, discontinue offering the Services or terminate or suspend your access to the Services at any time." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Says how changes to the terms are announced. Changes are posted, with no other notice named. - Refers to a service level or uptime commitment. Names 99.99% availability. - Also in the text (2026-10-08). MoEngage may aggregate and anonymise customer data and publish it, including in benchmark studies. "MoEngage shall have the right to aggregate and anonymize your data and to publish such aggregated and anonymized (non-personally identifiable) data (or) benchmark studies." - Also in the text (2026-10-08). MoEngage may name the customer in customer lists and testimonials. "3.2 MoEngage may use your name in any of the customer lists and testimonials, solely for the purpose of identifying you as a customer of MoEngage." **Privacy policy** (https://www.moengage.com/privacy-policy/), read 2026-10-09, dated 2026-08-26, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Our use of some of these services may constitute the “sale” or “sharing” of Personal Information as defined under the CCPA to/with third party advertisers." - Gives the date it was last updated. Last updated 2026-08-26. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on standard contractual clauses. - Also in the text (2026-10-08). MoEngage reserves the right to disclose any information about customers or their end users to officials or private parties when it believes this necessary, at its sole discretion. "Accordingly, we reserve the right to disclose any information about App Providers or End Users to government or law enforcement officials or private parties as we, in our sole discretion, believe necessary:" - Also in the text (2026-10-08). Customer data left unused for a set period is archived or permanently deleted from production systems on an automated schedule. "Data that has not been actively used or required for a pre-defined period for marketing activities, segmentation, or personalization is systematically archived or permanently deleted from our production systems." ## Live (updated 2026-10-10 02:07 UTC) - Right now: up, HTTP 401, 34 ms, checked 2026-10-10 02:07 UTC (get on `https://mcp.moengage.com`, asks for auth) - Uptime 24h 99.07% (107 probes) · 30 days 99.07% (107 probes) · p50 37 ms · p95 135 ms - Vendor status page: none, All Systems Operational - Watching changelog - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/moengage.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - 36 public OpenAPI files with 140 operations, every one with a summary and description, and a 429 response documented on 103 - A rate limit table with numbers for every endpoint group, plus `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset` response headers - The hosted MCP server at mcp.moengage.com uses OAuth tied to the user's role, masks PII attributes and cannot publish a campaign - API keys can be scoped to chosen API groups, use OAuth 2.0 tokens of 5 to 60 minutes or AWS STS roles, and be limited by IP address - A published SLA of 99.9 per cent monthly availability, a public DPA and a sub-processor list with locations dated 1 September 2026 ## Weaknesses - No public price, free tier or trial. The pricing page lists Growth and Enterprise plans with a one-year minimum and a sales contact only - On 17 August 2026 the Inform API in DC-03 returned HTTP 200 for about 16 hours while some messages were never sent, per the status page - Scoped keys, OAuth 2.0 and AWS STS keys sit in an API key dashboard that is in early access and enabled on request - Segmentation and Inform accept Basic authentication only, and new Push API keys can't be created - No API deprecation policy was found, and no official server-side API client library was found in the documentation ## Before you call it (notes for agents) 1. Take the data centre number from the dashboard URL and call `https://api-{dc}.moengage.com`. Data can't be moved between data centres 2. Send an `Idempotency-Key` header (UUID v4) on V5 campaign writes and test sends, and a `transaction_id` on Inform alerts, which deduplicates for 5 minutes 3. Use internal event and attribute names in segment filters, and run `deep_validate_segment_filters` first. A wrong event name is accepted and the count later fails with no reason 4. Use `in` with a list for text equality in segment filters. `equals` returns a 400 that names no field 5. Reuse an OAuth access token until it nears expiry. The token endpoint allows 5 requests a minute and 30 per 10 minutes for each key ## Connect First request: ```bash curl --request POST \ --url https://api-{dc}.moengage.com/v1/customer/YOUR_WORKSPACE_ID \ --header 'Authorization: Bearer YOUR_ACCESS_TOKEN' \ --header 'Content-Type: application/json' \ --data '{ "type": "customer", "customer_id": "user_12345" }' ``` MCP client configuration: ```json { "mcpServers": { "moengage": { "url": "https://mcp.moengage.com" } } } ``` Through letme (picks today, calling later): https://letme.dev/moengage. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Customer.io | BB | 74.5 | 69 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates, notify.push | no | https://www.anchorterminal.com/tools/customer-io.md | | Klaviyo API + MCP | BB | 71.7 | 119 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/klaviyo.md | | Omnisend | B | 64.9 | 334 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/omnisend.md | | Mailchimp Marketing API | C | 57.4 | 609 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/mailchimp-marketing.md | | Iterable | C | 55.2 | 664 | marketing.profiles, marketing.events, marketing.segments, marketing.campaigns, marketing.journeys, email.templates | no | https://www.anchorterminal.com/tools/iterable.md | | Braze | C | 61.2 | 475 | marketing.profiles, marketing.events, marketing.campaigns, marketing.journeys, marketing.segments | no | https://www.anchorterminal.com/tools/braze.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The docs index links 36 OpenAPI 3 files, 140 operations in all, from Data and Campaigns to Analytics and Message Archival (source: ) - The hosted MCP server at https://mcp.moengage.com documents 52 tools for campaign drafts, content blocks, segments, flows, dashboards and analyses. Publishing a campaign stays in the dashboard (source: ) - The MCP server is available in data centres DC01 to DC04, and campaign creation through it covers Push and Email only (same page) - The rate limit page gives a number for every endpoint group, for example 10,000 user updates a minute on Track User and 5 campaign drafts a minute (source: ) - On 17 August 2026 the Inform API in DC-03 returned HTTP 200 for about 16 hours while a subset of messages was never sent (source: ) - The SLA commits to 99.9 per cent monthly availability, with a 500 dollar credit below 95 per cent and 1,000 dollars below 90 per cent (source: ) - The security page lists SOC 2 Type 2, ISO 27001:2022, ISO 27701, ISO 22301, CSA STAR Level 1 and HIPAA (source: ) - The responsible disclosure policy promises an acknowledgement within 24 hours and says there is no monetary bug bounty (source: ) - A separate docs MCP server at https://www.moengage.com/docs/mcp searches the documentation only and needs no login (source: ) - #3 of 9 in Best lifecycle marketing and customer engagement platforms for AI agents: https://www.anchorterminal.com/best/lifecycle-marketing/index.md - All 36 lifecycle marketing comparisons: https://www.anchorterminal.com/compare/lifecycle-marketing/index.md ## Compare - [ActiveCampaign vs MoEngage](https://www.anchorterminal.com/compare/activecampaign-vs-moengage.md): D 50.5 vs B 65.2 - [Braze vs MoEngage](https://www.anchorterminal.com/compare/braze-vs-moengage.md): C 61.2 vs B 65.2 - [CleverTap vs MoEngage](https://www.anchorterminal.com/compare/clevertap-vs-moengage.md): D 48.8 vs B 65.2 - [Customer.io vs MoEngage](https://www.anchorterminal.com/compare/customer-io-vs-moengage.md): BB 74.5 vs B 65.2 - [Iterable vs MoEngage](https://www.anchorterminal.com/compare/iterable-vs-moengage.md): C 55.2 vs B 65.2 - [Klaviyo API + MCP vs MoEngage](https://www.anchorterminal.com/compare/klaviyo-vs-moengage.md): BB 71.7 vs B 65.2 - [Mailchimp Marketing API vs MoEngage](https://www.anchorterminal.com/compare/mailchimp-marketing-vs-moengage.md): C 57.4 vs B 65.2 - [MoEngage vs Omnisend](https://www.anchorterminal.com/compare/moengage-vs-omnisend.md): B 65.2 vs B 64.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on moengage.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "moengage", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html MoEngage on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![MoEngage on Anchor Terminal](https://www.anchorterminal.com/badges/moengage.svg)](https://www.anchorterminal.com/tools/moengage) ``` Plain link: ```html MoEngage on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say MoEngage is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/moengage-dark.png - Light: https://www.anchorterminal.com/assets/share/moengage-light.png