Other common integrations
Two-way SMS messaging
Two-way messaging allows your customers to reply directly to the text messages received from your campaign. To learn more about two way messaging, see our Two way SMS messaging and Opt-out keywords documentation.
The following integration is available.
| Type | Description |
|---|---|
| Two-way messaging | This function enables the sending of bidirectional SMS communications. SMS contain the option to change marketing preferences by responding to the SMS "STOP" or other defined keywords. Ensure that the custom provider integration is in place and that the provider is selected as SMS service provider in project settings. Don’t forget to enable “2 Was SMS messaging” in project settings. |
Custom SMS provider integration
The following integration is available.
| Type | Description |
|---|---|
| Custom SMS provider | In order to send SMS via a custom service, you need to provide the details of your SMS provider’s API, such as the payload structure, endpoint, and authentication. A webhook in a scenario then sends data to the SMS provider. SMS provider is able to send responses or delivery information back to Bloomreach Engagement via Bloomreach Engagement API if needed. |
Call centre integration
The following integration is available.
| Type | Description |
|---|---|
| Call centre | In order to establish a connection between your call centre and Bloomreach Engagement, you need to provide the details of the call centre API, such as the payload structure, endpoint, and authentication. A web-hook in a scenario then sends data to the call centre. Call centre is able to send responses back to Bloomreach Engagement via its API if needed. |
Mobile SDK integration
The following integration is available.
| Type | Description |
|---|---|
| Mobile SDK | In order to track customer behaviour in mobile applications, you need to implement our Mobile SDKs to your mobile applications. With the Mobile SDK implemented, you are able to use native functionalities such as automatic session tracking, Bloomreach Engagement push notifications, or in-app messages. |
API triggered imports
The following integration is available.
| Type | Description |
|---|---|
| API triggered imports | To trigger imports via API, you need to create a definition of import in the Bloomreach Engagement project first. The API call contains the ID of the specific import. With an API trigger, you can run the import programmatically, directly from your backend system whenever it is ready. |
Transactional API
The following integration is available.
| Type | Description |
|---|---|
| Transactional API | To trigger a transactional email, you need to call the Transactional email endpoint published in our API Reference. The HTML can be included directly in the call or the ID of the email template stored in Bloomreach Engagement can be used instead. Delivery status information is tracked automatically. |
Looking for a specific integration?
Our Integrations pages include guides on connecting Bloomreach with tens of other tools.
Updated 10 months ago