Skip to main content

Documentation Index

Fetch the complete documentation index at: https://moengage-crashes-in-debug-feedback.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

The following are the contents of the files for the messages archived.
Channel and PlatformFile Contents (S3)File Contents (SFTP)
Email
  • Main content (HTML)
  • From email address
  • Sender name
  • Subject
  • Reply-to email address
  • Date and time of email delivery
  • User details (To email address)
  • Main content (HTML)
  • From email address
  • Sender name
  • Subject
  • Reply-to email address
  • Date and time of email delivery
  • User details (User ID and To email address)
  • Campaign Info (ID, name, type, app key)
  • Workspace Name
  • Delivery Type
SMS
  • Main content
  • User details (mobile number)
  • Channel
  • Connector info
  • Short code or service ID
  • Template type
  • Delivery time
  • Tracked URLs
  • Main content
  • User details (User ID and mobile number)
  • Channel
  • Connector info
  • Short code or service ID
  • Template type
  • Delivery time
  • Tracked URLs
  • Campaign Info (ID, name, type, app key)
  • Workspace Name
Push - Android (This is not a preview, but only the content. This is because the message may render differently for each device.)
  • Main content
  • Backup content (wherever backup is supported, except for basic templates)
  • Campaign details
  • User details (Push token)
  • Channel
  • Platform
  • Main content (summary, title, message, URLs)
  • Backup content (wherever backup is supported, except for basic templates)
  • Campaign details (ID, name, type, app key, Workspace name)
  • User details (User ID and Push token)
  • Channel
  • Platform
  • Delivery type and time
Push - iOS (This is not a preview, but only the content. This is because the message may render differently for each device.)
  • Main content
  • Backup content (wherever backup is supported, except for basic templates)
  • Campaign details
  • User details (Push token)
  • Channel
  • Platform
  • Main content (summary, title, message, URLs)
  • Backup content (wherever backup is supported, except for basic templates)
  • Campaign details (ID, name, type, app key, Workspace name)
  • User details (User ID and Push token)
  • Channel
  • Platform
  • Delivery type and time
Push - Web (This is not a preview, but only the content. This is because the message may render differently for each device.)
  • Main content
  • Backup content (wherever backup is supported, except for basic templates)
  • Campaign details
  • User details (Push token)
  • Channel
  • Platform
  • Main content (summary, title, message, URLs)
  • Backup content (wherever backup is supported, except for basic templates)
  • Campaign details (ID, name, type, app key, Workspace name)
  • User details (User ID and Push token)
  • Channel
  • Platform
  • Delivery type and time

​
Example of Message Content

​
Structure of a Single Message Object

The following are examples of the file content for a single message archived via SFTP and S3: 
{
 "message_content": {
 "summary": "{message_summary}", 
 "related_urls": ["{image_or_deep_link_url}"],
 "title": "🎉 MarketingCampaigner Implemented!!",
 "message": "Sample push notification message"
      }, 
 "backup_content": {
 "summary": "{message_summary}",
 "related_urls": ["{image_or_deep_link_url}"],
 "message": "{message_body_content}",
 "title": "{message_title}",
 "message_details": {
 "sent_time": "Tue, 21 Jan 2025 09:54:59 EST",
  "template_info": {
      "id": "basic", 
      "type": "Native"
      },
 "delivery_type": "API_TRIGGERED", 
  "service": {
       "type": "APNs"
      },
 "channel": "push", 
 "message_type": "campaign", 
 "message_id": "{{message_id}}",
 "message_to": "", 
 "platform": "ios"
      }
      }
The following images are some examples of file contents archived via the S3 archival method:
  • The View Sent Message feature is not available for the SFTP method in the UI.
  • In case of non personalized message, SFTP message archival will have only one copy in the message content and MoEngage appends “user_ids” of all the user receiving the message.
16.png