Infobip SMS/MMS

Infobip is an additional SMS/MMS provider that gives you more granular delivery reports and tracking than standard providers. This guide covers how to set up the integration, supported use cases, event tracking, and delivery report behavior.

❗️
Initial setup
The initial Infobip SMS/MMS setup must be completed by an SMS specialist. Contact your specialist before configuring the integration at the project level.

Set up the integration

Go to Data & Assets > Integration > Infobip SMS.
Set up Infobip as your SMS provider as outlined on the Infobip site. The integration includes tracking of enqueued messages.
Retrieve the required API key from Infobip.

Infobip SMS integration screen accessed via Data and Assets in Bloomreach — Accessing the Infobip SMS integration via **Data & Assets** > **Integration** > **Infobip SMS**.

Configure a sender profile

To use the integration, set it up as a sender profile in Project settings > Campaigns > SMS / MMS / RCS. For details, read the SMS or MMS campaign documentation. The setup process is the same for both SMS and MMS.

Use cases

Infobip SMS/MMS integration is well suited for:

Omnichannel campaigns across multiple channels.
SMS double opt-in subscription with automated confirmation and consent management.
Abandoned cart personalized messages.
Abandoned browse reminders.
Follow-up messages for unopened email offers.
Flash sale notifications.
Price drop notifications.
Product availability notifications.
Shipping notifications.
Phonebook and list hygiene management.
NPS responses or customer feedback collection by SMS reply.

Track events

By default, Infobip SMS/MMS activity is tracked as a campaign event with action_type = sms. You can map events to a different event name in Project settings > Campaigns > Mapping > Campaign events.

The following properties are tracked on each campaign event:

Event property	Value	Description
`comment`	For example, "The number doesn't exist or it hasn't been assigned to any active subscriber in the operator's user database."	Optional detailed error message.
`error`	For example, `EC_UNIDENTIFIED_SUBSCRIBER`	See Infobip's Delivery report statuses.
`number_of_message_parts`	`number`	Count of message parts.
`status`	`delivered`	The message was successfully delivered to the recipient's handset.
`status`	`enqueued`, `enqueue_failed`	Whether the message was successfully forwarded to the SMS provider for delivery.
`status`	`rejected`, `failed`	The message was rejected by Infobip or delivery failed.
`status_code`	Numerical value, for example `400`	See Infobip's Delivery report error codes and SMPP error codes.

Infobip delivery reports

Delivery reports show how many messages were delivered to recipients' handsets and when. Infobip calls a Bloomreach callback with delivery reports in 2 ways:

Immediately: For messages with a rejected status.
Later: For delivered and failed statuses, once the recipient's operator responds.

The following delivery statuses are tracked as SMS campaign events:

delivered: Successfully delivered to the recipient's handset.
rejected: Rejected by Infobip.
failed: Delivery unsuccessful.

Waiting period

Delivery reports can take up to 4 days to arrive, depending on the destination country and operator. All possible delivery reports are tracked within the first 4 days after sending.

Countries without delivery reports

Some countries don't provide delivery reports for SMS messages. These countries are: Bangladesh, Benin, Brazil, Burundi, Cambodia, Germany, Guadeloupe, Guam, Hong Kong, Indonesia, Kuwait, Malaysia, Marshall Islands, Mauritania, Mexico, Nauru, Northern Mariana Islands, Pakistan, Panama, Papua New Guinea, Peru, Samoa, Solomon Islands, South Sudan, Sri Lanka, Sudan, Tajikistan, Timor-Leste, Tonga, Tuvalu, Uzbekistan, Venezuela, Vietnam, Wallis, and Futuna Islands.