Send WebEngage email through SendMero

Deliver your WebEngage email campaigns with SendMero, and see delivered and bounced results in WebEngage.

WebEngage builds and schedules your campaigns; SendMero delivers the email and reports what happened to each message back to WebEngage.

Set up

Verify your sending domain. The From address of your WebEngage campaigns must be on a domain you have verified in SendMero. Add your domain →
Create an API key. WebEngage uses it to send through your SendMero workspace. Create an API key →
Add SendMero in WebEngage. In WebEngage, open your email channel settings, add a new email service provider, choose SendMero, and paste your API key when WebEngage asks for it. Save the configuration, then select it when you set up a campaign.
Send a test campaign to a few teammates and check the result in WebEngage and in Activity in the SendMero dashboard.

Messages sent this way count towards your sending limits and credits in the same way as messages sent through the API.

SendMero tells WebEngage about each recipient automatically. You do not set up a webhook for this.

What happened	What WebEngage shows
The recipient's mail server accepted the message	Delivered
The message could not be delivered (a bad address, a full mailbox, a rejection)	Bounced, with the kind of bounce
The recipient reported the message as spam	Bounced, marked as a spam report
SendMero could not send it (for example an attachment could not be downloaded)	Bounced

Opens, clicks and unsubscribes are tracked by WebEngage itself, through the links and images in your campaign. SendMero does not change your links.

Message size. An email's content (HTML, text and the other fields) can be up to about 120 KB. Larger campaigns are refused.
Attachments. Up to 10 attachments and 10 MB in total per message. Each one must be a public https link that can be downloaded directly, without redirects. If a file cannot be downloaded, that message is reported to WebEngage as bounced and is not sent.
Sending limits and credits are the ones that apply to your workspace. When you reach a limit, WebEngage is told the message could not be accepted.

WebEngage shows an error code when SendMero refuses a message. These are the ones you may see:

Code	Meaning	What to do
9003	The API key is not valid.	Check the key you entered in WebEngage. It must be an active key from the same workspace as your domain.
9011	The From domain is not verified or not ready to send.	Open Domains in SendMero and finish verifying the domain. Domain not verifying →
9002	A sending limit was reached, or you are out of credits.	Check Usage in the dashboard.
9001	Too many requests at once.	WebEngage retries automatically.
9024	New sending is paused because an invoice is overdue.	Pay the invoice in the dashboard.
9988	Something else was wrong with the message, such as a message that is too large or an attachment link that is not valid.	Check the size and the attachment links.

If a message was accepted but is not arriving, look it up in Activity. Find a message →