docs(limits): integrate Personalize & Decisioning limits in-context (§11)

[mallikarjun-dhulange]

Platform limits — Personalize / Offer Decisioning POD

Integrates the Personalize & Offer Decisioning platform limits (Confluence §11) into the docs, in context. No snippets, no hub. Confluence is the source of truth for this work.

Gaps filled in-context

• Max active Personalize experiences = 20 → overview-personalize.mdx
• Max offerings input per Decision Policy = 50 (added alongside the existing output=10 line) → decision-policy.mdx

Verified already-documented (no change needed)

A/B variations per offering 5 · offering attributes per workspace 50 · offerings output per policy 10 · conversion goal tracking window 10 days (1 hour–10 days).

⚠️ Conflict — held for PM (see PR comment)

• Max active offerings: the docs state a cap of 100 (with a raise path); Confluence §11 says no limit. Left the docs' 100 in place — removing a real, specific customer-facing cap on the strength of a vaguer reference-doc value would be the wrong direction.

Deferred

• Fetch API rate (10,000 RPM) and max experience keys per request (25) → API POD (API-surface limits, belong on api/ pages).
• WYSIWYG campaign refresh interval (15 min) → no clean user-guide home; this is an SDK re-fetch behaviour and likely belongs in the Personalize SDK / client-side technical docs. Flagged for a home decision.

🤖 Generated with Claude Code

[mallikarjun-dhulange]

🚩 One conflict held for PM

Max active offerings — docs say 100, Confluence §11 says "no limit".

The live docs state a maximum of 100 active offerings (with a "contact CSM to raise" path) in faqs-on-offerings.mdx. Confluence §11 lists this as no platform-enforced limit. I kept the docs' 100, because removing a specific, customer-facing cap that has a documented raise-path — on the strength of a vaguer reference value — is the risky direction.

Please confirm: is there a real 100-offering cap (keep docs as-is), or is it genuinely unlimited (then I'll update the FAQ)?

Deferred (not in this PR)

• Fetch API rate (10,000 RPM) and max experience keys per request (25) — API-surface limits, will land in the API POD PR on the api/ pages.
• WYSIWYG campaign refresh interval (15 min) — this is an SDK re-fetch behaviour with no clean user-guide home. It likely belongs in the Personalize SDK / client-side technical docs. Where would you like 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:06 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, 5:56 AM

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