docs(limits): integrate Data platform limits in-context (§1, §2, §3, §5)

[mallikarjun-dhulange]

Platform limits — Data POD

Covers the Data platform limits (Confluence §1 Ingestion FUP, §2 Profile Storage, §3 Schema Caps, §5 Data Warehouses). No snippets, no hub. Confluence is the source of truth for this work.

This POD was almost entirely documented already — this PR adds the one genuine gap and records what was verified.

Gap filled in-context

• Data warehouse historical migration rate = 15M rows/hour · 50M rows/day (shared user+event pool) → overview-imports.mdx, in the existing historical-imports note.

Verified already-documented (no change needed)

• §1 Ingestion FUP — 100/min, 300/5min, 500/hr, 1000/day with block actions; 3 consecutive breaches → 7-day block; max 1,000 devices/profile. All on fair-usage-policy-fup.mdx.
• §2 Profile storage — activity feed 12,000 events / 12 MB / 30 days (fair-usage-policy-fup.mdx); list/array element caps (data-tracking-policies.mdx, support-for-object-data-type.mdx).
• §3 Schema caps — unique events 512, user attributes 256, event attributes 100/event, name length 200, value length 512, list max 50 elements, URL value >512 rejected. All on data-tracking-policies.mdx.
• §4 File-import rates (600K/hr, 14M/day users) are also already documented in the imports limits table.

Deferred / flagged (see PR comment)

• User merge limit = 50 per operation → API POD (it's a User Merge API operation cap).
• User/device record deletion after 60 days of inactivity → not published: it's marked SDP-internal in Confluence and appears to conflict with the retention-policy messaging on the FUP page ("permanent storage based on your retention policy"). Needs PM confirmation.

🤖 Generated with Claude Code

[mallikarjun-dhulange]

Notes for review

This POD was already ~95% documented, so the diff is intentionally tiny (one addition). Two items were held rather than published:

Deferred to the API POD: User merge limit (50 profiles per operation) — this is a User Merge API operation cap and belongs on the api/ User Merge page with the other API-surface limits.

Held for PM — possible conflict: Confluence §2 states a user/device record with no activity for 60 days is automatically deleted (marked "hard-coded in SDP"). This appears to conflict with the retention messaging on fair-usage-policy-fup.mdx, which says events have permanent storage based on your retention policy. Publishing "your inactive user data is deleted after 60 days" is both alarming to customers and potentially inaccurate. Please confirm the actual behaviour before we document it.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
moengage	🟢 Ready	View Preview	Jul 24, 2026, 6:20 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
moengage	🟡 Building	–	Jul 24, 2026, 6:10 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.