Skip to main content
Description: The Recipients Report provides a detailed record of all messages sent to individual subscribers from the previous day. This includes broadcast, recurring, autoresponder, system, test, and transactional messages. This report enables users to track each message campaign at the individual subscriber level, offering valuable insights into message deliverability, including whether a message was successfully delivered or bounced. Note: list_id and list_name can be null for system messages at the account level. In this case any custom fields tied to a given subscriber will not be returned. Frequency: Daily/Weekly/Monthly Output: .csv file Scope: Includes data from all lists on the account Customization: Users can request to append subscriber-level custom fields to the report, such as CRM IDs (e.g., cons_id from Blackbaud Luminate Online). These custom fields must be pre-configured within the list in the user’s Tatango account to appear in the report. Fields:
  • report_run_date: The date when the report was generated.
  • owner_account_id: The Tatango account ID for the owner account of the organization.
  • company_name: The name of the company associated with the Tatango account.
  • list_id: The unique Tatango ID of the list from which the messages containing the clicks were sent.
  • list_name: The name of the list in Tatango.
  • phone_number: The phone number of the subscriber that received the message.
  • recurring_message_id: The ID of the parent recurring message. Only applicable if the message was a child of a recurring message.
  • message_id: The unique id of the message the subscriber received.
  • momt_id: The unique id of the individual message sent to the phone number.
  • message_name: The name of the broadcast or recurring message the subscriber received.
  • message_type: This identifies the type of message that was sent.
    • broadcast: Broadcast messages are large audience blast messages sent from within the Tatango UI.
    • recurring: Recurring messages are scheduled messages set to trigger based off of subscriber actions.
    • system: System messages are default system messages that are triggered based off of subscriber actions (opt-ins, opt-outs) or by texting in keywords like HELP.
    • test: Test messages are messages sent during the broadcast creation process by users to validate the content of the broadcast message they are creating.
    • transactional: Transactional messages are messages sent using our Transactional Message API.
  • content: The content of the message sent to the subscriber.
  • sent_at: The time the message was sent.
  • delivery_status: The status of the message sent to the subscriber.
  • Delivered: The carrier has confirmed the message was received by the subscriber’s handset.
  • Bounced: The carrier attempted delivery but was unsuccessful.
  • Pending: Awaiting a response from the carrier.
  • bounce_type: The bounce type of the individual message sent to the subscriber. Only applicable if the delivery_status is Bounced.
  • soft: The handset is temporarily unable to receive the message (e.g., subscriber’s phone is off or out of service).
  • hard: The device is permanently unable to receive messages (e.g., landline, incompatible device, subscriber changed carriers, blocked number, etc).
  • total_message_parts: The number of individual SMS parts sent to the specific subscriber.