Articles in this section

See more

RCS System Events

RCS events help you understand delivery and engagement, build audiences, and create Journey flows.

RCS events are available in segmentation and filtering, user profile history, RCS metrics and campaign analytics, system webhooks, and Iterable Export APIs.

# RCS Bounce (rcsBounce)

Iterable logs an RCS Bounce event when it cannot deliver a message. RCS Bounce events include errorCode, which identifies the specific failure reason, and messageStatus, which describes the delivery outcome.

# errorCode

The errorCode identifies the specific reason Iterable could not deliver the message.

IMPORTANT

The codes below are a partial reference. The full catalog of RCS bounce reason codes is not available. If you encounter a code not listed here and need help, contact your CSM or support.

  • 592 — Your sender or account is not provisioned for the recipient's mobile network. This can be permanent, such as an unsupported carrier, or temporary while your sender is partially approved.
  • 7002 — The recipient cannot be reached via RCS because their device may not support RCS or RCS may be disabled.

# messageStatus

The messageStatus describes the delivery outcome. Use errorCode for a specific failure reason and messageStatus for broader outcome categories.

  • REJECTED_NETWORK — The recipient's network is not covered or your sender is not provisioned for it.
  • UNDELIVERABLE_REJECTED_OPERATOR — The recipient's mobile operator rejected the message as undeliverable.

See the RCS Bounce example webhook payload.

# RCS Click (rcsClick)

Iterable logs an RCS Click event when a recipient clicks a shortened, tracked link in an RCS message. Enable Shorten and track in the RCS template to log these events.

For link-shortening setup, see Link Shortening and Click Tracking for RCS, SMS, and WhatsApp. See the RCS Click example webhook payload.

# RCS Reply (rcsReceived)

Iterable logs an RCS Reply event when a recipient replies to an RCS message, including when they select a reply button. Use this event to segment users, enter them into Journeys, and branch conversation flows.

The event is listed on System Webhooks as Received (rcsReceived). See the RCS Reply example webhook payload.

# RCS Seen (rcsSeen)

Iterable logs an RCS Seen event when a recipient opens your message and their device reports a read receipt.

Not every recipient generates this event. A recipient might disable read receipts, not open the message, or use a device or carrier that does not report RCS read receipts. A missing RCS Seen event does not necessarily mean that the recipient did not read the message.

See the RCS Seen example webhook payload.

# RCS Send (rcsSend)

Iterable logs an RCS Send event when it attempts to send a message.

See the RCS Send example webhook payload.

# RCS Send Skip (rcsSendSkip)

Iterable logs an RCS Send Skip event when it determines that it should not send a message.

For the full list of skip reasons, see Reasons for Send Skip Events.

See the RCS Send Skip example webhook payload.

Related articles