> ## Documentation Index
> Fetch the complete documentation index at: https://moengage-gr001-partner-ingestion-limits.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Partner Data Ingestion Rate Limits

> Ingestion rate limits and payload caps for data imported into MoEngage from CDPs, cohort syncs, connected sources, files, and data warehouses.

MoEngage applies an ingestion rate limit and a payload cap to the data that a partner sends into your workspace. This page groups the limits by import type, because a partner that sends users and events has a different limit from the same partner syncing cohorts.

<Note>
  These limits are valid unless a different value is explicitly called out in the documentation for a specific partner. Check the partner's own integration guide for any override.
</Note>

## CDP Import Limits

These limits apply to users and events that a Customer Data Platform forwards to MoEngage, such as mParticle, Twilio Segment, and Adobe Real-Time CDP. The following table describes the limit for each entity:

| Entity | Ingestion rate limit | Payload size | On breach                                                                                                  |
| ------ | -------------------- | ------------ | ---------------------------------------------------------------------------------------------------------- |
| Users  | 500 RPS              | 128 KB       | MoEngage returns a `429 (Too Many Requests)` error. Partners are expected to handle retries automatically. |
| Events | 500 RPS              | 128 KB       | MoEngage returns a `429 (Too Many Requests)` error. Partners are expected to handle retries automatically. |

## Cohort Sync Import Limits

These limits apply to cohorts and audiences that a partner syncs into MoEngage. The rate limit depends on the partner. The following table describes the limit for each partner:

| Partners                            | Entity | Ingestion rate limit | Payload size | On breach                                                                                                  |
| ----------------------------------- | ------ | -------------------- | ------------ | ---------------------------------------------------------------------------------------------------------- |
| mParticle, Amplitude, Hightouch     | Cohort | 300 RPM              | 128 KB       | MoEngage returns a `429 (Too Many Requests)` error. Partners are expected to handle retries automatically. |
| Twilio Segment, Adobe Real-Time CDP | Cohort | 500 RPS              | 128 KB       | MoEngage returns a `429 (Too Many Requests)` error. Partners are expected to handle retries automatically. |

## Other Partner Import Limits

These limits apply to connected sources and other partner integrations, such as Ventrata, RevenueCat, Zoho CRM, and HubSpot CRM. The following table describes the limit for each entity:

| Entity                     | Ingestion rate limit | Payload size | On breach                                                                                                  |
| -------------------------- | -------------------- | ------------ | ---------------------------------------------------------------------------------------------------------- |
| Users, Events, and Cohorts | 500 RPS              | 128 KB       | MoEngage returns a `429 (Too Many Requests)` error. Partners are expected to handle retries automatically. |

## File Import Limits

These limits apply to imports from S3, SFTP, and manual uploads. The following table describes the hourly and daily limit for each entity:

| Entity | Hourly limit | Daily limit | On breach                                         |
| ------ | ------------ | ----------- | ------------------------------------------------- |
| Users  | 600K         | 14M         | MoEngage queues the files until the limits reset. |
| Events | 5M           | 40M         | MoEngage queues the files until the limits reset. |

## Data Warehouse Import Limits

These limits apply to imports from Snowflake, Databricks, and BigQuery. Users and events share the same pool, so both entity types draw from one limit. The following table describes the hourly and daily limit:

| Entity           | Hourly limit | Daily limit | On breach                                             |
| ---------------- | ------------ | ----------- | ----------------------------------------------------- |
| Users and Events | 10M          | 50M         | MoEngage processes the import on a best-effort basis. |

<Note>
  If your ingestion volume regularly approaches any of these limits, contact your MoEngage Customer Success Manager (CSM) to discuss your requirements.
</Note>

## Related Integrations

To set up a specific partner, refer to the following integration guides:

* [Adobe Real-Time CDP](/partner-guide/data-and-analytics/cdps/adobe-real-time-cdp/overview)
* [mParticle](/partner-guide/data-and-analytics/cdps/mparticle/getting-started/overview)
* [Twilio Segment](/partner-guide/data-and-analytics/cdps/twillio-segment/getting-started/moengage-source)
* [Data Imports](/user-guide/data/imports/overview/overview-imports)