{"componentChunkName":"component---src-templates-markdown-template-jsx","path":"/guides/settings/platform/notifications/","result":{"data":{"pageMetadata":{"title":"Notifications","path":"/guides/settings/platform/notifications/","sourceCode":null,"metadataParent":{"title":"Platform","path":"/guides/settings/platform/","sourceCode":null,"hasVersionPicker":null,"metadataChildren":[{"title":"Platform Configuration","path":"/guides/settings/platform/platform-configuration/","order":1,"label":null},{"title":"mParticle Users and Roles","path":"/guides/settings/platform/users/","order":2,"label":null},{"title":"Key Management","path":"/guides/settings/platform/key-management/","order":3,"label":null},{"title":"Notifications","path":"/guides/settings/platform/notifications/","order":4,"label":null},{"title":"Audit Logs","path":"/guides/settings/platform/audit-logs/","order":5,"label":null}],"metadataParent":{"title":"Settings","path":"/guides/settings/","metadataChildren":[{"title":"Platform","path":"/guides/settings/platform/","order":1,"label":null},{"title":"Billing","path":"/guides/settings/billing/","order":4,"label":null},{"title":"Usage metering for value-based pricing (VBP)","path":"/guides/settings/usage/","order":5,"label":null}],"metadataParent":{"title":"Guides","path":"/guides/","metadataChildren":[{"title":"Platform Overview","path":"/guides/platform-overview/","order":0.5,"label":null},{"title":"Getting Started","path":"/guides/getting-started/","order":1,"label":null},{"title":"mParticle Agent","path":"/guides/mparticle-agent/","order":1.5,"label":null},{"title":"Oversight","path":"/guides/oversight/","order":2,"label":null},{"title":"Data Platform","path":"/guides/data-platform/","order":3,"label":null},{"title":"Data Warehouse","path":"/guides/data-warehouse/","order":4,"label":null},{"title":"Customer 360","path":"/guides/customer-360/","order":5,"label":null},{"title":"Analytics","path":"/guides/analytics/","order":6,"label":null},{"title":"Audiences","path":"/guides/audiences/","order":7,"label":null},{"title":"Settings","path":"/guides/settings/","order":8,"label":null},{"title":"Troubleshooting mParticle","path":"/guides/troubleshooting/","order":10,"label":null},{"title":"Default Service Limits","path":"/guides/default-service-limits/","order":11,"label":null},{"title":"Glossary","path":"/guides/glossary/","order":12,"label":null}],"metadataParent":null}}}},"markdownRemark":{"html":"

When configured and enabled, Notifications delivers fault notifications when a supported feature, data input, or data output encounters a critical error.

\n

By surfacing these critical errors in real-time or near-real-time, fault notifications can lead to faster issue resolution and a more reliable and trustworthy customer data infrastructure.

\n

\n \n \n \n \n \n \n \n Notification types

\n

Notifications currently supports fault notifications, which are critical notifications delivered when a supported feature or integration fails to process data.

\n\n

Fault notifications can be delivered for the following features:

\n

\n \n \n \n \n \n \n \n Data inputs

\n

Fault notifications are triggered when mParticle fails to ingest data from a supported data input due to a pipeline configuration or connection issue.

\n\n

\n \n \n \n \n \n \n \n Warehouse Sync

\n

Following are the different Warehouse Sync integrations that support fault notifications:

\n\n

\n \n \n \n \n \n \n \n Data outputs

\n

Fault notifications are triggered when mParticle fails to forward data to a configured output destination. These faults may involve connectivity issues, misconfigurations, or errors returned by downstream systems.

\n

Output faults are supported for the following warehouse and audience output integrations:

\n

\n \n \n \n \n \n \n \n Audience outputs

\n

Fault notifications are sent when downstream partners return non-retryable errors to mParticle that require action from you to resolve. (For all other errors, mParticle continues retrying to forward data in the background.)

\n

Supported audience outputs:

\n\n\n

\n \n \n \n \n \n \n \n Data warehouse outputs

\n

Supported data warehouse outputs:

\n\n

\n \n \n \n \n \n \n \n Other fault notifications

\n

In addition to fault notifications for data inputs and outputs, you can also enable fault notifications for Composable Audiences and Rules.

\n

\n \n \n \n \n \n \n \n Composable Audiences

\n

Fault notifications are triggered when Composable Audiences fails to query data within your connected warehouse due to a broken connection, invalid SQL statement in a data model, or a data model configuration change.

\n

\n \n \n \n \n \n \n \n Rules

\n

Fault notifications are triggered when a rule (which can be used to cleanse, enrich, or transform batches of incoming or outgoing data) fails to execute as configured. These faults could be caused by a time-out, exception or mis-configuration.

\n\n

\n \n \n \n \n \n \n \n Notification destinations

\n

Notification destinations are the channels where mParticle sends fault notifications. Supported destinations include email lists, Slack channels, and custom webhooks. Once a destination is created, you can enable or disable specific notification types for that destination from the Notifications settings page.

\n\n

To create and manage notification destinations:

\n
    \n
  1. Log in to your mParticle account.
    2. \n
  2. Hover your cursor over the Settings gear icon in the left-hand navigation, select Platform, and go to the Notifications tab.
    3. \n
\n

\n

Here you can create notification destinations and configure which notification types are sent to each destination. Each row represents a notification type, and destinations (such as an email list or Slack webhook) are represented as columns.

\n

To enable or disable a specific notification type for a destination, simply check or uncheck the corresponding box in the grid.

\n

\n

\n \n \n \n \n \n \n \n Add a new destination

\n

To add a new destination, click the + button and select either Email List, Slack, or Webhook before following the specific instructions for your selection below.

\n

\n

\n \n \n \n \n \n \n \n Email List

\n

Email lists are shared notification channels that allow Admins to send fault notifications to a group of email recipients. Email lists ensure that critical alerts are delivered to multiple stakeholders (like data engineering teams or system admins) through a centralized distribution list.

\n

To add a new email list:

\n
    \n
  1. Click the + button and select Email List.
    2. \n
  2. Enter a descriptive name for your email list destination. For example, if you want these notifications to be delivered to the email addresses of your account administrators, use “Admins”.
    3. \n
  3. Enter each email address you want to receive notifications. Separate multiple addresses with a comma.
    4. \n
  4. Click Save.
    5. \n
\n

\n \n \n \n \n \n \n \n Slack

\n

Before you can add a Slack destination, you need to create an Incoming Webhook in your Slack workspace:

\n
\n \n \n \n \n \n \n \n 1. Create a Slack App
\n
    \n
  1. Visit the Slack App Directory.
    2. \n
  2. Click Create New App.
    3. \n
  3. \n

    In the modal that appears:

    \n\n
    4. \n
\n
\n \n \n \n \n \n \n \n 2. Enable Incoming Webhooks
\n
    \n
  1. In the left-hand sidebar, select Incoming Webhooks.
    2. \n
  2. Toggle the switch to Activate Incoming Webhooks.
    3. \n
  3. Scroll down and click Add New Webhook to Workspace.
    4. \n
  4. Select the Slack channel where you want to post notifications (e.g., #warehouse-input-notifications).
    5. \n
  5. Click Allow to authorize.
    6. \n
  6. After authorization, a Webhook URL will be generated for your selected channel.
    7. \n
  7. \n

    Copy the URL — it will look something like:

    \n
    https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
    \n
    8. \n
\n
\n \n \n \n \n \n \n \n 3. Create your Slack notification destination in mParticle
\n
    \n
  1. Click the + button and select Slack.
    2. \n
  2. Enter a name for your Slack destination (e.g., #data-alerts - Fault Notifications).
    3. \n
  3. Paste the Webhook URL from Slack in Slack Webhook URL.
    4. \n
  4. Click Save.
    5. \n
\n\n

\n \n \n \n \n \n \n \n Webhook

\n

For advanced use cases, mParticle supports custom webhook destinations that receive fault notifications as raw, JSON-formatted payloads. This allows you to integrate notifications directly into your internal systems, such as monitoring tools, incident response workflows, or observability pipelines. Each notification includes structured metadata about the faulted configuration, making it easy to programmatically parse, log, or trigger automated responses.

\n

To create a custom webhook destination:

\n
    \n
  1. Ensure you have a working webhook endpoint that can receive POST requests containing JSON payloads.
    2. \n
  2. From the Notifications settings page, click the + button and select Webhook.
    3. \n
  3. Enter a name for your webhook destination.
    4. \n
  4. Under Webhook URL, enter the URL for your custom webhook.
    5. \n
  5. If your webhook requires authorization to receive POST requests, enter the key under Authorization.
    6. \n
  6. Click Save.
    7. \n
\n
\n \n \n \n \n \n \n \n Example webhook notification payloads
\n

All raw, JSON-formatted notifications will include some common fields, such as your account ID, the timestamp when the fault was detected, and an error message. See the table below for a complete reference of these common fields included with each notification:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Field nameDescription
account_idYour mParticle account ID.
account_nameYour mParticle account name.
detected_atIndicates when the fault was detected, formatted as an ISO timestamp.
error_messageThe error message that was returned when the fault was detected.
org_idYour mParticle organization ID.
org_nameYour mParticle organization name.
\n

Each notification type will include additional descriptive fields that are specific to the particular entity (e.g. a Warehouse pipeline or an audience output) that faulted. Following are examples of JSON-formatted notifications for each notification type, along with a descriptive list of the entity-specific fields included.

\n
\n \n \n \n \n \n \n \n Example warehouse input notification payload
\n
{\n  \"account_id\": \"4732\",\n  \"account_name\": \"NimbusRetail_Main\",\n  \"detected_at\": \"2025-07-08T14:37:52.421Z\",\n  \"error_message\": \"An unhandled error has occurred.\",\n  \"org_id\": \"8921\",\n  \"org_name\": \"Nimbus Retail Inc.\",\n  \"pipeline_id\": \"redshift__k4lm9\",\n  \"pipeline_name\": \"Redshift Pipeline\",\n  \"pipeline_status\": \"faulted\",\n  \"pipeline_url\": \"direct URL to the pipeline configuration\",\n  \"workspace_id\": \"25\",\n  \"workspace_name\": \"US Marketing Prod\"\n}
\n

Specific Warehouse input notification fields

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Field nameDescription
pipeline_idThe ID of the warehouse pipeline that faulted.
pipeline_nameThe name of the warehouse pipeline that faulted.
pipeline_statusThe pipeline status.
pipeline_urlA direct URL to the warehouse pipeline configuration settings in mParticle.
\n
\n \n \n \n \n \n \n \n Example warehouse output fault notification JSON
\n

All warehouse output fault notifications sent to custom webhooks match the following format:

\n
{\n  \"account_id\": \"4732\",\n  \"account_name\": \"NimbusRetail_Main\",\n  \"detected_at\": \"2025-07-08T19:04:44.035Z\",\n  \"error_message\": \"The maximum number of attempts has been reached in ExternalSnowflake loader for [OutputConfigurationId 56164] [StreamPartition 0]\",\n  \"org_id\": \"8921\",\n  \"org_name\": \"Nimbus Retail Inc.\",\n  \"warehouse_output_id\": \"540\",\n  \"warehouse_output_name\": \"Snowflake Warehouse Output\",\n  \"warehouse_output_url\": \"direct URL to the output configuration\",\n  \"workspace_id\": \"25\",\n  \"workspace_name\": \"US Marketing Prod\"\n}
\n

Specific Warehouse output notification fields

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Field nameDescription
warehouse_output_idThe ID of the warehouse output that faulted.
warehouse_output_nameThe name of the warehouse output that faulted.
warehouse_output_urlA direct URL to the audience output’s configuration settings in mParticle.
\n
\n \n \n \n \n \n \n \n Example audience output fault notification JSON
\n

All audience output fault notifications sent to custom webhooks match the following format:

\n
{\n  \"account_id\": \"4732\",\n  \"account_name\": \"NimbusRetail_Main\",\n  \"audience_output_id\": \"1051\",\n  \"audience_output_name\": \"Audience Output\",\n  \"audience_output_url\": \"direct URL to the output configuration\",\n  \"detected_at\": \"2025-07-08T19:03:13.126Z\",\n  \"error_message\": \"Audience forwarding failed: Received HTTP 403 Forbidden - Invalid or expired OAuth token. Please re-authenticate the destination account to resume delivery.\",\n  \"org_id\": \"8921\",\n  \"org_name\": \"Nimbus Retail Inc.\",\n  \"workspace_id\": \"25\",\n  \"workspace_name\": \"US Marketing Prod\"\n}
\n

Specific Warehouse output notification fields

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Field nameDescription
audience_output_idThe ID of the audience output that faulted.
audience_output_nameThe name of the audience output that faulted.
audience_output_urlA direct URL to the audience output’s configuration settings in mParticle.
\n

\n \n \n \n \n \n \n \n Delete a destination

\n

To delete a destination:

\n
    \n
  1. Using the left-hand navigation, go to the Notification settings page by clicking Settings > Platform and selecting the Notifications tab.
    2. \n
  2. Hover your cursor over the destination name and click Edit.
    3. \n
  3. Click Delete. When the confirmation modal appears, click Delete.
    4. \n
\n

\n \n \n \n \n \n \n \n Testing notifications

\n

To validate your notification configuration, set up a working destination (e.g., a verified email), then intentionally trigger a fault. One way to do this is to:

\n\n

\n \n \n \n \n \n \n \n When notifications are triggered

\n

Notifications are triggered at the point mParticle detects a non-retryable fault in a configuration. When faults are detected varies depending on the specific input or output integration.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Integration TypeWhen notifications are triggered
Warehouse InputsNotifications are triggered when mParticle attempts to ingest data from the warehouse according to your sync schedule.
Warehouse OutputsNotifications are triggered when mParticle attempts to forward data to the warehouse.
Audience OutputsNotifications are triggered when mParticle attempts to forward an audience to an output. The upload frequency for the integration determines when faults are detected.
","frontmatter":{"title":"Notifications","order":4,"seoTitle":null,"seoDescription":null},"parent":{"__typename":"File","modifiedTime":"October 12, 2026"}}},"pageContext":{"slug":"/guides/settings/platform/notifications/"}},"staticQueryHashes":["2950460867"]}