Skip to content

docs(limits): integrate In-App/OSM/Cards limits in-context (§13, §14) - #446

Draft
mallikarjun-dhulange wants to merge 2 commits into
mainfrom
docs/limits-messaging
Draft

docs(limits): integrate In-App/OSM/Cards limits in-context (§13, §14)#446
mallikarjun-dhulange wants to merge 2 commits into
mainfrom
docs/limits-messaging

Conversation

@mallikarjun-dhulange

Copy link
Copy Markdown
Member

Platform limits — In-App / OSM / Cards POD

Integrates the In-App, On-Site Messaging, and Cards platform limits (Confluence §13 + §14) into the docs, in context. No snippets, no hub. Confluence is the source of truth for this work.

Gaps filled in-context (§13 In-App/OSM)

Verified already-documented (no change needed)

§13: screens per trigger 5 · After Delay 1 day (86,400 s) · "AND then" wait 24 h · A/B variations 5 · locales 11 · native image 10 MB.
§14 Cards: header 30 / message 115 chars · image/GIF 10 MB · card expiry 180 days · auto-sync 45 min · inbox refresh 5 min · pull-to-refresh 5 s · analytics unique window 72 h.

Deferred / flagged (see PR comment)

  • Cards Fetch API & Delete API rate = 50K RPM → API POD (API-surface).
  • Meta-call refresh (15 min) and self-handled In-Apps per trigger (5) → SDK behaviours; likely belong in the mobile SDK docs, not user-guide.
  • "Max active cards at a time" — value is blank in Confluence §14; nothing to publish until a PM fills it.

🤖 Generated with Claude Code

Add active campaigns 200, re-evaluate eligibility 5, app contexts 5,
FC rules 10 (incl 3 tag-based), nudges/screen 3, video nudge 10MB.
Cards §14 already fully documented except API rates (→ API POD) and
the blank "max active cards" value. Meta-refresh & self-handled caps
flagged as SDK-doc material.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mallikarjun-dhulange

Copy link
Copy Markdown
Member Author

Notes for review

Deferred to the API POD: Cards Fetch API and Delete API rate limits (50K RPM each) are API-surface limits and will land on the api/ Cards pages in the API POD PR.

Likely SDK-doc material (not user-guide): two §13 limits are pure SDK runtime behaviours with no natural user-guide home —

  • Meta-call refresh interval (15 min) — how often the SDK re-fetches eligible In-App campaigns.
  • Max self-handled In-Apps per single trigger (5) — the SDK returns the top N in priority order.

These read better in the mobile SDK integration docs. Flagging for a home decision rather than forcing them onto a dashboard page.

Blank in Confluence: §14 "Max active cards at a time" has no value filled in — nothing to publish until the PM completes that row.

@mintlify

mintlify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

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

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

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

@mintlify

mintlify Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

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

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

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

…confirmed)

Adds the eligible-campaign refresh behavior (15-min foreground refresh,
immediate on new session / relaunch) to the In-App native page of every
mobile SDK: Android, iOS, React Native, Flutter, Unity, Cordova, Capacitor.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant