In this article, you will find out how to enable the Infobip integration in Synerise which will let you send emails to your profiles (for example, customers). Become familiar with [the events this integration generates](#tracking-bounce-events) for hardbounces, spambounces, and softbounces. ## Prerequisites --- - Create an account in Infobip. - In the Infobip documentation, check the message limits imposed by Infobip. While planning email campaigns and sending email batches, take these limits into consideration. ## Enabling integration --- 1. Go to Settings icon**Settings > Apps & Services**. 2. In the list of integrations, find **Infobip (Email)** and next to the integration name, click **Show**. - If there is a connection, you may proceed to [configuring a sender account](/docs/campaign/e-mail/configuring-email-account#configure-a-sender-account) - If there is no connection or you want to create a new one, proceed to the next step. 3. Click **Add connection**. **Result**: A pop-up appears. 4. In the **API Key** field, enter [the API key generated in Infobip platform](https://www.infobip.com/docs/essentials/api-authentication#api-key-header). The key must have the following access scopes assigned: `email:manage`, `email:message:send`, `message:send`. 5. In the **Base URL endpoint** field, enter the full base URL for API requests. To get your base URL, log in to the [Infobip API Resource](https://dev.infobip.com/) hub with your Infobip credentials. Once logged in, the URL is in the following format: `https://xxxxx.api.infobip.com`. Learn more about the base URL [in the Infobip documentation](https://www.infobip.com/docs/essentials/base-url). 6. In the **Application ID** field, enter the Application ID associated with the API key. This field is optional. Learn more about this property [in the provider's documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management). 7. In the **Entity ID** field, enter the Entity ID associated with the API key. This field is optional. Learn more about this property [in the provider's documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management). 8. Click **Apply**. 9. Proceed to [configuring a sender account](/docs/campaign/e-mail/configuring-email-account#configure-a-sender-account). ## Tracking bounce events --- The tables below illustrate the mapping between Infobip errors and Synerise events. The mapping depends on the **Group ID** and **Group Name** values that Infobip includes in its notification, as well as the specific error code.
The tables list only the error codes that affect event mapping. For a complete list of Infobip error codes, see the [Infobip documentation](https://www.infobip.com/docs/essentials/api-essentials/response-status-and-error-codes#email-error-codes).
The events will be generated in Synerise and will be available in the activity list on a profile card. You can [create a segmentation](/docs/analytics/segmentations/creating-segmentations) based on the events listed in the tables to obtain the list of profiles for whom the events were generated. **Group ID 1** | Error in Infobip | Group name | Event in Synerise | |------------------|------------|-------------------| | `EC_SPAM_DETECTED` | DROPPED | [`newsletter.spambounce`](/docs/assets/events/event-reference/email#newsletterspambounce) | | `EC_SUPPRESSED_SPAM_COMPLAINT` | DROPPED | [`newsletter.spambounce`](/docs/assets/events/event-reference/email#newsletterspambounce) | | `EC_SUPPRESSED_BOUNCE` | DROPPED | [`newsletter.spambounce`](/docs/assets/events/event-reference/email#newsletterspambounce) | | Any other error name | DROPPED | [`newsletter.dropped`](/docs/assets/events/event-reference/email#newsletterdropped) | | Any error name | HANDSET_ERRORS | [`newsletter.hardbounce`](/docs/assets/events/event-reference/email#newsletterhardbounce) | **Group ID 2** | Error in Infobip | Group name | Event in Synerise | |------------------|------------|-------------------| | `EC_SENDER_IP_BLACKLISTED` | BOUNCED | [`newsletter.spambounce`](/docs/assets/events/event-reference/email#newsletterspambounce) | | `EC_BLOCKED_AS_SPAM` | BOUNCED | [`newsletter.spambounce`](/docs/assets/events/event-reference/email#newsletterspambounce) | | `EC_SPAM_REVERTED` | BOUNCED | [`newsletter.spambounce`](/docs/assets/events/event-reference/email#newsletterspambounce) | | `EC_RECIPIENT_INBOX_FULL` | BOUNCED | [`newsletter.softbounce`](/docs/assets/events/event-reference/email#newslettersoftbounce) | | `EC_SOFT_BOUNCE` | BOUNCED | [`newsletter.softbounce`](/docs/assets/events/event-reference/email#newslettersoftbounce) | | Any other error name | BOUNCED | [`newsletter.hardbounce`](/docs/assets/events/event-reference/email#newsletterhardbounce) | | Any error name | USER_ERRORS | [`newsletter.hardbounce`](/docs/assets/events/event-reference/email#newsletterhardbounce) | **Group ID 3** | Error in Infobip | Group name | Event in Synerise | |------------------|------------|-------------------| | Any error name | OPERATOR_ERRORS | [`newsletter.hardbounce`](/docs/assets/events/event-reference/email#newsletterhardbounce) |