Untitled :: Mobile Engage Docs

Mobile Engage Docs

Services

General Push Notification Admin Service Android Emarsys SDK Client Service Content Service Delivery Service Device Event Service E2E Service Embedding Messaging Service Event Publisher Service In-app Inbox Infrastructure iOS Emarsys SDK ME Event Personalization ME Pub/Sub Delayer Msg Generator Scheduler SDK Management Secret Manager Segment Diff Wallet Service Web Emarsys SDK

Download

General

Internal API
External API
Formats
- Push Notification Payload
  - Fcm
  - Apns
  - Huawei
  - Vapid
Concepts
Operations
Quality Assurance
- Test Accounts
Minerva
- AWS Rotate Access Keys
How Tos
Tools
- ME CLI
- Validate Database Migration

General master

Admin Service
- main
Android Emarsys SDK
- master
Client Service
- master
Content Service
- main
Delivery Service
- master
Device Event Service
- master
E2E Service
- main
Embedding Messaging Service
- main
Event Publisher Service
- master
General
- master
In-app
- master
Inbox
- master
Infrastructure
- master
iOS Emarsys SDK
- master
ME Event Personalization
- main
ME Pub/Sub Delayer
- master
Msg Generator
- main
Push Notification
- master
Scheduler
- master
SDK Management
Secret Manager
- main
Segment Diff
- master
Wallet Service
- master
Web Emarsys SDK
- master

General
Architecture
Dynamo DB

In following Google Doc it is explained why we chose DynamoDB for device registration data.

This page was built using the Antora default UI.

The source code for this UI is licensed under the terms of the MPL-2.0 license.