API Requests
Track every API call hitting SuprSend — success/failure counts, error breakdowns, and request volume over time.
Workflow Executions
Monitor workflow performance, catch execution errors early, and identify top failing workflows.
Messages
Follow the full message lifecycle — triggered, delivered, seen, clicked — with delivery errors by vendor and channel.
Enterprise plan feature. The SuprSend Datadog connector is only available on our Enterprise plan.
How it works
SuprSend exportssuprsend.* metrics to Datadog via OTLP over HTTP. You provide your Datadog OTLP endpoint and API key, choose which events to sync, and SuprSend streams them in near real-time — with latency under 1 minute.
Once connected you can build custom dashboards, set up monitors and alerts for delivery failures or API errors, slice by any dimension (workspace, tenant, workflow, channel, vendor, template), and correlate notification health with your infrastructure and APM data in Datadog.
All metrics are tagged by workspace, tenant, workflow, category, channel, vendor, template, node, and error details. See Reported metrics for the full list.
Installing the connector
Create a new connector
In your SuprSend dashboard, navigate to Connectors and click New Connector.

Configure connector settings
Fill in the following fields:

| Field | Description |
|---|---|
| Connector Name | A label to identify this connector (e.g. Datadog Production) |
| OTLP Endpoint | Select the site that matches your Datadog account’s region from the dropdown |
| API Key | A Datadog API key from the API Keys page. We recommend creating a dedicated key for SuprSend |
| Events to sync | One or more metric events to export (see Reported metrics) |
| Protocol | HTTP |

Dashboard starter kit
Get started quickly with our pre-built Datadog dashboard to visualize your SuprSend metrics in a few clicks.
Copy Dashboard Starter Kit JSON
Setting up alerts
Once your metrics are flowing into Datadog, you can set up monitors to get paged when something goes wrong in your notification pipeline. Here are two examples to get you started.Example 1 — Alert on delivery error rate spike
Alert when message delivery errors exceed a threshold — useful for catching vendor-side failures or misconfigurations before users notice.- In Datadog, go to Monitors → New Monitor and select Metric.
- Under Choose the detection method, select Threshold Alert.
-
Under Define the metric, enter:
Set Evaluate the bounds for the last to 5 minutes.
-
Under Set alert conditions:
- Trigger when the evaluated value is:
abovethe threshold - Alert threshold:
50— adjust based on your typical delivery volume. A good starting point is 1–2% of your average message volume per 5 minutes. - Warning threshold:
20— optional, but useful for early visibility before a full alert fires - If data is missing: set to Evaluate as zero

- Trigger when the evaluated value is:
-
Under Configure notifications & automations, give the monitor a name (e.g.
SuprSend — Delivery Error Spike) and add a message with context:Add your notification recipients (email, Slack, PagerDuty, etc.) using @ mentions in the message body. - Click Save.
Example 2 — Alert on anomalous message delivery drop
Alert when delivered message volume drops unexpectedly — useful for catching silent failures where messages stop flowing without a corresponding error spike.- In Datadog, go to Monitors → New Monitor and select Metric.
- Under Choose the detection method, select Anomaly Detection.
-
Under Define the metric, enter:
Set Evaluate the bounds for the last to 15 minutes.
-
Under Set alert conditions:
- Trigger when the evaluated values have been:
belowthe bounds — so you’re only alerted when delivery drops, not when it spikes - Alert threshold:
75— alert when 75% or more of the values in the window fall below the expected range - Under Advanced options → Anomaly detection algorithm options: set deviations to
2and keep the algorithm as basic

- Trigger when the evaluated values have been:
-
Under Configure notifications & automations, give the monitor a name (e.g.
SuprSend — Delivery Drop Anomaly) and add a message:Add your notification recipients using @ mentions in the message body. - Click Save.
Reported metrics
SuprSend streams the followingsuprsend.* counter metrics to Datadog. All counters are monotonically increasing and represent cumulative counts from the time the connector is enabled.
API Requests
Track the volume and health of every API call made to SuprSend.| Metric | Description |
|---|---|
suprsend.api_request.total | Total number of API requests received by SuprSend. Use the status tag to break down by outcome — sent, in_progress, success, failed, or partial_failure. |
suprsend.api_request.errors | API requests that failed to process due to an error. Group by api_type to identify which endpoint is failing, and by error_severity to prioritize investigation. |
| Tag | Description | Example values |
|---|---|---|
api_type | The SuprSend API endpoint that was called | workflow_trigger, broadcast_trigger, user_edit, event |
method | HTTP method of the request | POST, GET, PUT, PATCH |
status | Outcome of the request | sent, in_progress, success, failed, partial_failure |
workspace_key | Identifier of the SuprSend workspace (environment) | your_workspace_key |
workspace_slug | Slug of the SuprSend workspace. Eg. staging | |
tenant_id | Tenant ID if the request is scoped to a tenant | tenant_abc |
error_severity | Severity level of the error (on error metrics only) | critical, warning, info |
Workflow Executions
Monitor how your workflows and broadcasts are performing and quickly spot execution failures.| Metric | Description |
|---|---|
suprsend.workflow_execution.total | Total number of workflow executions started. Workflow executions are counted per-recipient. Use workflow_slug and category tags to drill down into specific workflows. |
suprsend.workflow_execution.errors | Workflow executions that failed to process due to an error. |
suprsend.broadcast_execution.errors | Broadcast executions that failed to process due to an error. |
| Tag | Description | Example values |
|---|---|---|
workflow_slug | Slug of the workflow that was executed | welcome-flow, order-confirmation |
trigger_type | How the workflow was triggered | api, event |
category | Notification category of the workflow | transactional, promotional |
root_category | Top-level category when categories are nested | marketing |
workspace_slug | Slug of the SuprSend workspace | my-workspace |
workspace_key | Identifier of the SuprSend workspace (environment) | your_workspace_key |
tenant_id | Tenant ID if the workflow is scoped to a tenant | tenant_abc |
error_severity | Severity level of the error (on error metrics only) | critical, warning, info |
Messages
Follow the full lifecycle of every message — from trigger through delivery, open, and click — and monitor delivery failures by vendor and channel.| Metric | Description |
|---|---|
suprsend.messages.triggered | Total number of messages triggered. Slice by channel and vendor to see volume distribution. |
suprsend.messages.delivered | Total number of messages delivered to the recipient. |
suprsend.messages.delivery_errors | Messages that failed to deliver due to an error. Use vendor / channel tags to isolate the error source. |
suprsend.messages.seen | Total number of messages seen by the recipient. Requires vendor webhook callbacks to be configured (see note below). |
suprsend.messages.clicked | Total number of messages clicked by the recipient. Requires vendor webhook callbacks to be configured (see note below). |
| Tag | Description | Example values |
|---|---|---|
workspace_slug | Slug of the SuprSend workspace | my-workspace |
workspace_key | Identifier of the SuprSend workspace (environment) | your_workspace_key |
tenant_id | Tenant ID if the message is scoped to a tenant | tenant_abc |
category | Notification category of the parent workflow | transactional, promotional |
channel | Delivery channel used for the message | email, sms, push, whatsapp, inbox, slack, ms_teams |
vendor | Vendor used to deliver the message | mailgun, twilio, firebase, sendgrid, etc. |
workflow_slug | Slug of the workflow that generated the message | welcome-flow, order-confirmation |
- All metrics are scoped to the SuprSend environment (e.g.
production,staging) via theworkspace_keytag. - For delivery, seen, and click metrics to be populated for Email, SMS, and WhatsApp, configure
https://hub.suprsend.com/webhook/*as a callback URL in your vendor dashboard. See the vendor integration docs for per-vendor instructions. - For error details, the SuprSend dashboard provides more granular information via Logs and Analytics.
Disabling the connector
To pause metrics streaming, open the connector from the Connectors page and toggle Enable sync off. Re-enable it at any time to resume.