ComposableStack.AI CDP
Back to agent
Modalitymodality.push

Push Notification

Mobile/web push delivery via APNs, FCM, and web-push protocols. Permission-revocable in one tap — fatigue is the dominant operational risk.

confidence 85%v1reviewed Apr 26, 2026modality, push, apns, fcm, fatigue

Push Notification

Mobile and web push delivery. Permission is fragile — users revoke push permission with one tap, and once revoked, it's hard to win back.

Operational risk. Fatigue. The use-case.abandoned-cart cautionary tale (source.cdp-recommendation-agent-md) — too-frequent push reminders pushed users to disable notifications entirely — is a push-channel pattern. Frequency caps and orchestration across channels are not optional.

Sources

Related

← Referenced by

  • applies-to-modalityconcept.modality-complexity— Each modality contributes to complexity
  • prerequisite-ofconcept.consent-management— Push permission is platform-enforced; revocation must disable all targeting immediately.
  • governsconstraint.tcpa-revoke-all-universal-opt-out— TC-78. Push notification opt-out (in-app unsubscribe, OS-level disable) is a 'reasonable means' under the Revoke-All rule and must propagate to the sender's other active channels.
  • applies-to-modalityuse-case.loyalty-program-personalization— OC-055. Push notifications are the real-time event-triggered loyalty channel: tier upgrades, milestone completions, expiring-offer alerts, and lapse-risk nudges fire outside the active app session to opted-in members. Push is distinct from mobile-app (in-session): it reaches members between sessions, complementing the intra-day freshness requirement (OC-054). Node body names push in the multi-channel delivery list.