MMS Detailed

The time and date (in UTC) when we accepted a valid message request from your account or from a mobile operator.

While not required fields, we recommend adding the Accepted Date, Delivered Date and Updated Date fields as they are useful in analyzing an SMS message's history. If included, you can select to group messages by:

• Second — this is the default value.
• Minute
• 15 Minutes
• 30 Minutes
• Hour
• Day — as per the UTC
• Week — this is Sundays to Saturdays
• Month — each calendar month
• Quarter — The quarters are: January-March, April-June, July-September, October-December
• Year — year by 1st of January until 31st of December

Filterable? Yes. When used as a filter, it is always required.

You can filter the report by the following:

• Predefined — select a predefined choice. This can be either Today, Yesterday, This Week, Last Week, This Month, or Last Month; however remember that the maximum date range is restricted to 2 days for this report (as set in the Accepted Date filter)
• Rolling — select the type of time period (e.g. Hours) and how many units of that time you want included in the report. For example, "5 Hours" will create a report that, when run, includes the last 5 hours data.
• Equals — select a specific date by clicking the calendar icon, or by entering the date using a yyyy/mm/dd format.
• Custom Range — select a date range; however, remember that the maximum data range is 2 days for this report.

When creating a scheduled report, use either the Predefined or the Rolling options as these adjust for each run of the report to show data relative to the run time.

The time and date (in UTC) when the end user received the message.

This is based on the delivery receipt we receive from the mobile operator. The accuracy of the receipt depends on the mobile operator and the region that the message was sent to.

Note that in some locations we can only send the messages at a specific time of day; for example, promotional messaging in India are restricted to business hours due to local regulations. Use with the Accepted Date field to calculate the delivery speed. Add the Updated Date if you want to also see when messages failed.Use with the Accepted Date field to calculate the delivery speed. Add the Updated Date if you want to also see when messages failed. If included, you can select to group messages by:

• Second — this is the default value.
• Minute
• 15 Minutes
• 30 Minutes
• Hour
• Day — as per the UTC
• Week — this is Sundays to Saturdays
• Month — each calendar month
• Quarter — The quarters are: January-March, April-June, July-September, October-December
• Year — year by 1st of January until 31st of December

Filterable? Yes.

You can filter the report by the following:

• Predefined — select a predefined choice. This can be either Today, Yesterday, This Week, Last Week, This Month, or Last Month; however remember that the maximum date range is restricted to 2 days for this report (as set in the Accepted Date filter)
• Rolling — select the type of time period (e.g. Hours) and how many units of that time you want included in the report. For example, "5 Hours" will create a report that, when run, includes the last 5 hours data.
• Equals — select a specific date by clicking the calendar icon, or by entering the date using a yyyy/mm/dd format.
• Custom Range — select a date range; however, remember that the maximum data range is 2 days for this report.

When creating a scheduled report, use either the Predefined or the Rolling options as these adjust for each run of the report to show data relative to the run time.

Time and date that the message was forwarded on to the carrier. If included, messages can be grouped by:

• Second — this is the default value.
• Minute
• 15 Minutes
• 30 Minutes
• Hour
• Day — as per the UTC
• Week — this is Sundays to Saturdays
• Month — each calendar month
• Quarter — The quarters are: January-March, April-June, July-September, October-December
• Year — year by 1st of January until 31st of December

Filterable? Yes.

You can filter the report by the following:

• Predefined — select a predefined choice. This can be either Today, Yesterday, This Week, Last Week, This Month, or Last Month; however remember that the maximum date range is restricted to 2 days for this report (as set in the Accepted Date filter)
• Rolling — select the type of time period (e.g. Hours) and how many units of that time you want included in the report. For example, "5 Hours" will create a report that, when run, includes the last 5 hours data.
• Equals — select a specific date by clicking the calendar icon, or by entering the date using a yyyy/mm/dd format.
• Custom Range — select a date range; however, remember that the maximum data range is 2 days for this report.

When creating a scheduled report, use either the Predefined or the Rolling options as these adjust for each run of the report to show data relative to the run time.

The unique ID of an account you have with OpenMarket. Depending on your business requirements, you may have multiple accounts to send MMS messages. Include if your business is using multiple accounts, particularly if your business units use different accounts that you will need to report on.

Filterable? Yes. Enter one or more account IDs on which to filter. From the drop-down list, enter the account ID, and then select it from the list. Search and add additional account IDs as needed. A tally keeps track of the number of IDs added to the filter. Alternately, you can filter on Account Name.

The unique name of an account you have with OpenMarket. Depending on your business requirements, you may have multiple accounts to send and receive SMS messages.

You can alternatively use Account ID in the report. Include if your business is using multiple accounts, particularly if your business units use different accounts that you will need to report on.

Filterable? Yes. Enter one or more account names on which to filter. From the drop-down list, enter the account name, and then select it from the list. Search and add additional account names as needed. A tally keeps track of the number of account names added to the filter. Alternately, you can filter on Account ID.

The message recipient. For MT messages, this is the end user's phone number. For MO messages, this is one of your message originators.

Filterable? Yes. Filter by a specific number or alphanumeric string. If you are entering a dialable number that's not a short code, make sure it is in international format. For example, enter 12515550100 for a US number or 447700900750 for a UK number. If you want to see both the sender and receiver of a message, include Source Address.

Indicates whether or not OpenMarket performed an operator lookup for a message.

Filterable:? Yes. Choose from the following:

• 1 — True. Indicates an operator lookup was performed.
• 0 — False. Indicates that no operator lookup was performed.

The external message identifier received from the carrier, used to identify the message being sent or received.

Filterable?: Yes.

Enter the exact external message ID. Partial search is not supported.

Text description that identifies the reason the message failed to be delivered. Use this field to see the reason that the message failed to be delivered to the end user.

Filterable?: Yes. This is a text-only field that supports the following failure reasons:

• NULL

• RECIPIENT_BLOCKED

• RECIPIENT_NOT_FOUND

• INDETERMINATE_CARRIER_ERROR

• INDETERMINATE_SYSTEM_ERROR

• ERROR_FORWARDING_TO_CUSTOMER

• RECIPIENT_DEACTIVATED

• RECIPIENT_SUSPENDED

• RECIPIENT_NOT_AVAILABLE_FOR_MMS

• ERROR_FORWARDING_TO_CARRIER

• UNABLE_TO_PARSE_RESPONSE

• SHORT_CODE_NOT_FOUND_OR_ALLOWED

• GENERIC_GET_CONTENTS_ERROR

• UNABLE_TO_ROUTE_MESSAGE

• CONTENT_BLOCKED_OR_REFUSED

• CARRIER_CAMPAIGN_NOT_FOUND

• DEREGISTERED

• NOT_FOLLOWING_REDIRECTS

• CARRIER_CAMPAIGN_BLOCKED

• DEFERRED

• GET_CONTENT_TOO_LARGE

To add multiple values to the filter, enter a value from above, and then press Enter. Add another value. Continue to add as many values as you want to filter on.

Indicates whether or not the message included video.

Filterable? Yes. Choose from one or both of the following:

• 1 — True. The message included a video file.
• 0 — False. The message did not include a video file.

The source number used to send an MT message or receive an MO message. Types of originators include short codes, text-enabled landlines, toll-free numbers, alphanumeric strings, and virtual mobile numbers (long codes).

Filterable? Yes. Multiple values are supported. This is a free-text field, so you will need to know your originators before using this filter. To add multiple originators, include a line space between each number—that is, press the Enter key after adding each number so that each number is on its own line. Use this to split the message traffic by your message originators. You can use this in conjunction with the Message Direction field to see the messages coming from and to that originator.

This field describe the type of originator.

Filterable?: Yes. This is a text-only field that supports the following message originator types:

• SHORTCODE: Indicates a short code originator.
• ALPHANUMERIC: Indicates an alphanumeric originator.
• TELL: Indicates a text-enabled land line (TELL) originator.
• TETFN: Indicates a text-enabled toll-free number (TETFN) originator.
• VMN: Indicates a virtual mobile number (VMN) originator.

Multiple values are not permitted. You can filter on only one message type at a time.

Summarizes the current or final status of a message. For example, this could be SUCCESS or FAILED. Use to see the status of the message. For a failed message, you can get additional detail if you've included the Failure Reason field.

Filterable?: Yes. This is a text-only field that supports the following message statuses:

• SUCCESS
• FAILED
• IN PROGRESS

Multiple values are permitted. Press Enter after adding a message status to add another status.

Whether the message was sent from your account (MT) or the end user (MO). Use this filter to see the direction/type of message.

Filterable?: Yes. This is a text-only field that supports the following message types.

• MTMMS - MMS sent from your account
• MOMMS - The end user sent an MMS in response
• MOSMS - The end user sent an SMS in response

Multiple values are permitted. Press Enter after adding a type to add another message type.

Use this field if you want to see the operators your end users are connected to, organized by mobile operator ID. Use this field if you want to see the operators your end users are connected to. Note, however, that this does not always indicate the operator that we directly sent the messages to; some messages are sent off-net —for example, using a related operator in the same region— or in more remote locations by a high-quality route. This can be useful for troubleshooting high message failures with a specific operator.

Filterable?: Yes. This is a text-only field that will always be a number — for example, enter 383 for AT&T, and 348 for T-Mobile in the UK. Multiple values are permitted, but each value must be on its own line. Enter a mobile operator ID, and then press Enter. Add the next operator ID, and again press Enter. Add as many mobile operator IDs as you want to filter on.

Name of the mobile operator associated with the end user's phone number. Use this field if you want to see the operators your end users are connected to, organized by mobile operator ID. Use this field if you want to see the operators your end users are connected to. Note, however, that this does not always indicate the operator that we directly sent the messages to; some messages are sent off-net —for example, using a related operator in the same region— or in more remote locations by a high-quality route. This can be useful for troubleshooting high message failures with a specific operator. You can use this field instead of Mobile Operator ID.

Filterable?: Yes. This is a text-only field that will always be a number — for example, enter AT&T or Vodafone.. Multiple values are permitted, but each value must be on its own line. Enter a mobile operator name, and then press Enter. Add the next operator ID, and again press Enter. Add as many mobile operator IDs as you want to filter on.

Additional data included in your message request. This might be used for including reference to a support ticket or system information. Include this field if your MT message requests specified Note; otherwise, you can ignore this field. This field is empty for MO messages

Filterable?: Yes. This is a text-only field. You must enter the note contents exactly as they were sent in the message.

For messages sent in either direction (MT or MO), this is the end user's phone number.

Add Message Originator to the report if you would like to see the end user's number, and Message Direction to see who sent the message.

Filterable? Yes. Multiple values are supported. This is a free-text field, so you will need to know the end user's number before using this filter. To add phone numbers, include a line space between each ID—that is, press the Enter key after adding each number so that each number is on its own line. The phone number should also use an international format—for example: 12515550100 (US) or 447700900750 (UK). Don't include the plus (+) character.

Text description that identifies the current or final delivery state of a message. Use this field to determine the final current or delivery state of the message.

Filterable?: Yes. This is a text-only field that supports the following values:

• NULL
• Delivered
• Rejected
• Expired

Multiple statuses are supported. Enter a status from the list above, and then press Enter. Add any additional statuses, pressing Enter after each entry.

The size of the message. Use this field to see the byte size of the media file attached to the message.

Filterable?: Yes. Use the spinner to select the size, or enter a number.

The message sender. For MTs, this will be a shortcode, longcode, etc. For MOs, this will be an end user's phone number. If you want to see both the sender and receiver of a message, include Destination Address.

Filterable?: Yes. Multiple values are supported. This is a free-text field, so you will need to know the end user's number before using this filter. Short codes are not supported. You must enter a dialable number in an international format—for example: 12515550100 (US) or 447700900750 (UK). Don't include the plus (+) character. Each phone number must be on its own line—that is, press the Enter key after adding each number.

Indicates any subaccount associated with the message. Include this field if you are grouping messaging programs using subaccount; otherwise, you can ignore this field.

Filterable?: Yes. Use to filter the report by one or more of your subaccount groups. This is a free-form text field, so you'll need to know the possible values you have sent with your messages. To add multiple subaccount groups, add a line between each subaccount by pressing Enter on your keyboard.

The subject of the message. Use this field to see the subject of the message. For MT messages, this is the text you included. For MO messages, this is the text the end user sent.

Filterable?: Yes. This is a free-form field. You must enter the subject text exactly as it was passed in the message.

US ONLY: Alphanumeric string associated with a program and registered with a mobile operator. The pre-provisioned program linked to the short code messaging service you are providing. OpenMarket provides you with the value during provisioning. This is required only for certain messaging programs in the US, such as short code messaging. Only include this field if your messaging programs use a program ID.

Filterable?: Yes. This is a free-form field. You must pass the program ID exactly as it is being used in your messaging program. Partial text is not supported.