> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/setup-and-monitor/plan-and-integrate/set-up-the-environment/platform-limits.md). # Platform limits The documented ceilings across the platform, and what to do when you need more. ## Your goal Design your integration within the limits the platform documents, and know which of them are defaults that can be raised. ## How to read this page Every figure below comes from the behaviour of a specific feature. Limits marked as **default** are set per organisation and can be discussed with your mediarithmics contact; the others are properties of the feature. {% hint style="info" %} If a limit blocks a use case, get in touch with your mediarithmics contact before designing around it. Several of these are defaults rather than hard ceilings. {% endhint %} ## Segmentation and audience | Limit | Value | Notes | | -------------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | Custom segment metrics per datamart | 5 | One per available technical name. See [Segment metrics](/setup-and-monitor/plan-and-integrate/set-up-the-environment/set-up-segment-metrics.md). | | Standard segment builder instances per datamart | 20 | See [Standard segment builder](/setup-and-monitor/plan-and-integrate/set-up-advanced-features/standard-segment-builder.md). | | Lines in an audience-feature final-values file | 100,000 | Each line must match your schema. | | Aggregations unsupported in segment metric queries | `@cardinality` | Use a different aggregation. | ## Automations Automation limits are set per [organisation](/setup-and-monitor/plan-and-integrate/set-up-the-environment/prerequisites-organisation-and-datamart.md#organisations-and-communities) and are defaults. | Limit | Default | Enforced when | | --------------------------------------- | -------------------------------- | -------------------------------------------------------------------------- | | Scenarios in `PAUSED` or `ACTIVE` state | 100 per organisation | On scenario creation. The request returns `403` when the limit is reached. | | Scenarios in `ACTIVE` state | 20 per organisation | On activation. Returns `403`. | | Nodes per scenario | 20 | On activation. Returns `403`. | | Wait nodes across active scenarios | 20 per organisation | On activation. Returns `403`. | | UserPoints woken per wait node per hour | 50,000 (service level objective) | Indicative. Above it, some users may not be woken in a timely fashion. | ## Querying | Limit | Value | Notes | | -------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | GraphQL endpoint | Read-only | Queries are supported; mutations are not. | | GraphQL rate limit | Rate-limited | Returns HTTP `429` when the queries-per-second rate exceeds the limit. Discuss the applicable rate and any increase with your account manager. | | Activities returned by a GraphQL query | 100 maximum | Not configurable, and there is no warning. Because an event always belongs to an activity, the limit applies indirectly to events: only events in the first hundred activities are returned. A `@filter` is applied **after** this limit. | See [GraphQL queries](/setup-and-monitor/operate-and-monitor/query-your-datamart/graphql-queries.md). ## Data lifetime | Data | Retention | | -------------------------------------- | --------------------- | | Activities analytics data | 4 months | | Events ingestion monitoring statistics | 3 months | | Collection volume statistics | 2 years | | Usage report statistics | 2 years | | Device technical identifiers | 1 year after creation | Retention of your own events and profiles is something you decide - see [Data retention](/setup-and-monitor/plan-and-integrate/set-up-the-environment/manage-data-retention.md). ## Plugins and computed fields | Limit | Value | Notes | | ------------------------------------------ | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Computed field `State` size | 1 MB maximum | Above it, the update is discarded and not saved. See [Computed fields](/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/computed-fields.md). | | Computed field initial computation | Up to 72 hours | It computes the timelines of all UserPoints. | | Plugin call rate, concurrency, and timeout | Configurable per plugin version | Set with throttlings, at global, container, organisation, or datamart scope. See [Plugin architecture](/setup-and-monitor/extend-the-platform/plugin-architecture.md). | ## Client-side segmentation (Edge) | Limit | Value | | -------------------------------------------------------- | ----------------------------------------------------- | | Events stored in the visit timeline, per domain and user | 200. Beyond that, each new event replaces the oldest. | | Segments stored client-side | No limit | | Client-side storage expiry | None - no automatic cleaning or expiration | See [Edge](/setup-and-monitor/plan-and-integrate/set-up-advanced-features/edge.md). ## Exports | Limit | Value | Notes | | --------------------------------------------------- | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Recommended file maximum size for file destinations | 100,000 KB (about 100 MB) | The file is uploaded as soon as the aggregated data reaches this size; it is the main limiting factor on export batching. See [File destination](/setup-and-monitor/collect-and-manage-your-data/export-your-data/file-destination.md). | ## Related pages
Data retentionThe windows you control, and the ones you do not.Data retention
Monitor resource usageSee how close you are to your own consumption.Monitor resource usage
Set up the environmentBack to the environment setup sequence.Set up the environment
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.mediarithmics.io/setup-and-monitor/plan-and-integrate/set-up-the-environment/platform-limits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.