This record is generated by AI from the cited source. How AI is used
API to block or unblock a specific device from receiving push notifications, for fraud or device-loss scenarios.
- Platform
- MoEngage
- Capability
- Mobile push · Channels also: APIs & extensibility
- Vendor's name
- Device opt-out API
- First recorded
- Record last updated
Record dates describe acquisition and updates, not human review. About corrections.
Lifecycle history 1 state
- GAApr 2026First recorded 28 Sep 2026 · recorded from the source history · vendor release notes · moengage.com ↗ · archived copy, 25 Oct 2026 ↗
Something wrong or out of date in this record? , ideally with a link to better evidence. How corrections work
Mobile push on other platforms latest first
- Treasure AITime-sensitive delivery for mobile pushGA2 Oct 2026
- KlaviyoPush notifications to primary device onlyGA30 Sep 2026
- Adobe AJOLive Activities for AndroidGA30 Sep 2026
- KlaviyoExternal URL action for push and in-app formsGA1 Sep 2026
- Adobe AJOAndroid push notification layout pickerGA1 Sep 2026
- Adobe AJOExecution metadata for Live Activity campaignsGA19 Aug 2026
- Adobe AJOHigh-throughput transactional messaging for pushGA11 Aug 2026
- BloomreachMobile push delivery and device identity improvementsGA10 Jun 2026
- KlaviyoPush notification action buttonsGA5 Jun 2026
- KlaviyoiOS background processing for push notificationsGA6 May 2026
More from MoEngage in Mobile push
- Icon Shortcuts Android push templateBetaOct 2026
- Primary device per userGAApr 2026
- Background update push templateGAApr 2026
- iOS transactional live activitiesGAFeb 2026